Problem
Currently, app start data is captured directly within the standaloneui.load transaction.
The future should be to separate it for a cleaner separation and possibly allow capturing app starts that don't necessarily have a UI e.g background services.
Proposal
Instead of attaching app start spans and measurements to the ui.load transaction, the SDK should send a standalone app start transaction as soon as app start data is available. App start timing is taken from the native layer, so the span structure matches Android.
This transaction carries all the same spans, measurements, and metadata — but is independent of any screen transaction.
- Transaction op:
app.start
- Opt-in via
enableStandaloneAppStartTracing (experimental)
Reference
Mirror of JAVA-283
Problem
Currently, app start data is captured directly within the standalone
ui.loadtransaction.The future should be to separate it for a cleaner separation and possibly allow capturing app starts that don't necessarily have a UI e.g background services.
Proposal
Instead of attaching app start spans and measurements to the
ui.loadtransaction, the SDK should send a standalone app start transaction as soon as app start data is available. App start timing is taken from the native layer, so the span structure matches Android.This transaction carries all the same spans, measurements, and metadata — but is independent of any screen transaction.
app.startenableStandaloneAppStartTracing(experimental)Reference
Mirror of JAVA-283