Apps calling multiple APIs often take over 4-5 seconds to load. Even with splash and skeleton screens, many users exit during this wait.

Self-service apps, which many global telcos promote for user adoption, display usage, billing, metering, and personalized offers. They gather data from various systems like billing, CRM, SAS, and promotional systems, each with its own request handling and response time constraints. This complexity often leads to slow load times, causing about a third of new users to abandon the app.

In contrast, the MyJio app, a standout in the telco self-service category, seems to use cache-on-load and asynchronous loading to improve the experience while managing these complexities. These techniques disconnect the UI from numerous API calls, speeding up the loading process.

This success prompts a rethink for telcos and similar apps. Essential considerations include:

✅ Only vital information should display on the launch screen, with the rest loading asynchronously based on user interaction.
✅ Although usage data changes at each app launch, displaying cached values during the API call for updates is acceptable.
✅ Items updated less frequently, like personalized offers, should be cached and asynchronously invoked based on user interaction, not at launch.