Working with API performance on the frontend

[rakhirani458]

“As a developer, you have to be very careful about latency when you first use an API because it’s very hard to turn off,” Nassimi says. “It’s also out of your control once you decide to use it in a company. The big problem is that there’s a threshold of latency that users are okay with, and once you cross that threshold, you start seeing very strange behavior from them.”

According to him, this behavior is especially slovenia mobile database on the front end, where users start doing unpredictable things like hitting refresh, hitting the back button, closing tabs, spamming, typing, or leaving the site altogether. The only solution that can be tried after implementing the API is to implement something in the UI that helps the user understand what is happening, such as a visual indicator of loading progress. Even a synthetic indicator, where the developer simply guesses how long the loading will take and creates a visualization accordingly, is better than simply leaving the user in limbo.

Ultimately, of course, it's better if the API works as intended, which is what prompted Nylas to address latency issues in its updated API in the first place. Typically, developers at client companies experience latency when connecting email and calendar, as the API waits to sync with the user's CRM and email.