Understanding Android App performance

Start-up time:

Implementation: Ideally, to calculate cold start we must track the starting point from the time when the app intent is launched. But since we cannot track from the process creation stage from a developer’s point of view, we start tracking as soon as the content provider from the manifest is initialized. This becomes the earliest point of detection for an app start.

  • Cold start can be defined as the time taken for the app to start from scratch and does not reside in memory. This is even before the initial process is created.
  • Warm start is when the user exits the app and re-launches it. In this case, the app does not reside in memory.
  • Cold start takes 5 seconds or longer.
  • Warm start takes 2 seconds or longer.

API calls:

Implementation: API calls can be monitored for two cases being Retrofit calls and OkHttp calls only. For both, we would require to call some methods from the Perfachhi SDK.

App details:

The app that is under test is a news application that uses Retrofit to make queries to an online news API. This fetches a bunch of articles that are laid down in a recycler view using architectural components.

Report details:

The SDK was integrated with a weather application for android but we did not have Retrofit support for that. We were able to generate reports which comprised of all the other parameters.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store


A pre-prod performance monitoring tool for Android developers. We will talk more about app performance and how can you optimize the app performance. Follow us!