Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sentry SDK timestamp from NativeLaunch-to-Android-to-Flutter for User Perceived App Start #2806

Open
thinkocapo opened this issue Mar 19, 2025 · 2 comments

Comments

@thinkocapo
Copy link

Problem Statement

Customer wants to track the user perceived app start.

They don't custom instrument a span because the app start begins in the native layer, then goes to the android layer, then finally the flutter layer.

This feature request might also be needed in

Solution Brainstorm

  1. Sentry Native SDK records a startTimestamp as soon as Sentry Native SDK is initialized, as app is starting.
  2. Sentry Native SDK propagates this startTimestamp to the Sentry Android SDK and Sentry Flutter SDK's
  3. Customer can decide the exact moment in their Flutter code that the user's perceived app start has completed, and customer is willing to generate a currentTimestamp and subtract the startTimestamp to figure the total time elapsed
  4. Customer to set this time elapsed as a Span Metric for tracking.

Customer could look into generating a startTimestamp themself in the native layer, and maybe track it via environmental variables and some kind of inter-layer communication, but was wondering if Sentry could assist in this.

Have other customers run into this sort of problem before?

Are you willing to submit a PR?

None

@kahest
Copy link
Member

kahest commented Mar 20, 2025

Hey @thinkocapo thanks for reporting - ignoring the proposed solution here for a minute, the actual use case

Customer wants to track the user perceived app start.

is exactly what the App Start integration is supposed to do. Please let us know if we're missing something.

@getsantry getsantry bot moved this to Waiting for: Community in GitHub Issues with 👀 3 Mar 20, 2025
@kahest kahest moved this from Needs Discussion to Needs More Information in Mobile SDKs Mar 20, 2025
@buenaflor
Copy link
Contributor

buenaflor commented Mar 20, 2025

@kahest I already replied in slack as well, they are essentially describing TTFD

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Waiting for: Community
Status: Needs More Information
Development

No branches or pull requests

3 participants