---
title: "Comment by Veeresh Charantimath on \"Tracking Android App Launch in production\" | Hashnode"
description: "is there a way to improve app hot-launch time with the Papa lib or in general? Our app is doing well in the cold and warm department but not able to figure what"
url: "https://hashnode.com/posts/tracking-android-app-launch-in-production/64af4c0009b8aa2957c3b3ae/comment/64b154980470cd817f0dc689"
---

[Discussion](https://hashnode.com/posts/tracking-android-app-launch-in-production/64af4c0009b8aa2957c3b3ae)

Comment [Tracking Android App Launch in production](https://hashnode.com/posts/tracking-android-app-launch-in-production/64af4c0009b8aa2957c3b3ae)

[Veeresh Charantimath](https://hashnode.com/@veeresh8)

[Jul 14, 2023](https://hashnode.com/posts/tracking-android-app-launch-in-production/64af4c0009b8aa2957c3b3ae/comment/64b154980470cd817f0dc689)

is there a way to improve app hot-launch time with the Papa lib or in general?

Our app is doing well in the cold and warm department but not able to figure what might be causing hot-launches to be bad.

any ideas?

[Pierre-Yves Ricau](https://hashnode.com/@py)

[Jul 14, 2023](https://hashnode.com/posts/tracking-android-app-launch-in-production/64af4c0009b8aa2957c3b3ae/comment/64b154980470cd817f0dc689#reply-64b178a70470cd817f0dcad4)

You could add stack sampling in production with `Debug.startMethodTracingSampling()` (works in releases) with a low sampling rate, then upload the file from the device. Alternatively, you could track attributes (account, device type, entry point, etc) and then try to repro locally and once you repro a slow hot launch you can profile locally.