Track a more customizable way to measure app launch for Android, similar to COCOA-1018.
The current launch measurement should allow a more explicit and customizable end point so background launches and delayed UI work are handled more predictably.
A possible direction is to expose an API that lets developers extend app launch and then explicitly mark launch as finished when the app has reached the desired point. If needed, this could also support a separate "fully displayed" marker.
This issue is to track the Android equivalent of the customizable app launch work being discussed for Cocoa.
Should be tackled after JAVA-283
// This must be called before the onFirstFrameDrawn
val launchSpan: TimeSpan? = Sentry.extendAppLaunch()
...
// Call this when you want to mark the app as launched (defaults to firstFrameDrawn as it is now)
launchSpan?.finish()
// If we want to have a special "full display" span we can support this
launchSpan?.fullyDisplayed()
This should also help with implementing JAVA-359
Track a more customizable way to measure app launch for Android, similar to COCOA-1018.
The current launch measurement should allow a more explicit and customizable end point so background launches and delayed UI work are handled more predictably.
A possible direction is to expose an API that lets developers extend app launch and then explicitly mark launch as finished when the app has reached the desired point. If needed, this could also support a separate "fully displayed" marker.
This issue is to track the Android equivalent of the customizable app launch work being discussed for Cocoa.
Should be tackled after JAVA-283
This should also help with implementing JAVA-359