Mobile app speed is not only a technical metric. For a food-ordering service, it directly affects whether users see the menu, complete an order, and return the next day.

What the Zomato team did

In an Android Developers case study, the team describes improving startup by removing legacy SDKs and unused libraries, lazy-loading dependencies, and refining layouts. Average cold startup improved by about 25%, and by up to 30% on low- and mid-range devices.

The most important result was business-related: the number of users reaching a fully loaded home screen increased by about 20%, while Day 1 retention improved by about 90%. The team also reported roughly 600,000 additional orders per month.

The lesson for other products

Performance work does not need to begin with a full rewrite. Measure the real journey first: tap the icon, reach the first useful screen, search, select, and complete an action. Then split the time between initialization, SDKs, network requests, UI construction, and data.

  • Remove what is not used.
  • Defer secondary libraries.
  • Test heavy screens on low-end devices.
  • Connect technical metrics to conversion and retention.

The Zomato case matters because it connects engineering work to user behavior. Speed has value not by itself, but because it removes friction on the way to an outcome.

Source: Android Developers: Increasing app speed by 30% at Zomato.