Clarify Application class code and system splash screen vs. Android TTID

Open Beginner friendly
#18,700 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
85/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Tech stack
android
Domain
documentation

Research direction

Start in docs/platforms/android/tracing/instrumentation/automatic-instrumentation.mdx and review the Cold Start and Time to Initial Display sections. Use the described SentryPerformanceProvider timing and Android system splash-screen behavior as context. Done means both behaviors are clearly explained in a short note so readers can determine what contributes to TTID.

Written by the indexing model from the issue text.

Description

Docs

The Android app-start docs (docs/platforms/android/tracing/instrumentation/automatic-instrumentation.mdx, Cold Start / Time to Initial Display sections) don't clarify two behaviors that came up in a customer question:

  • Code in the Application class (e.g. onCreate, attachBaseContext) runs before TTID ends and is counted as part of cold start, not after it. This follows from SentryPerformanceProvider's ContentProvider.onCreate() starting the app-start clock, which itself runs before Application.onCreate().
  • The Android system splash screen (the default SplashScreen API window on Android 12+, shown as an OS-rendered Window rather than an Activity) has no effect on TTID measurement. The SDK has no splash-screen-specific instrumentation (verified: no splash/SplashScreen references anywhere in sentry-java); TTID is purely Activity-lifecycle- and first-frame-drawn-based.

Adding a short note covering both points to the Cold Start / TTID docs would help customers reason about what does and doesn't count toward the measurement.

Requested by kpujji via Junior.

--

View Junior Session in Sentry

Dominant language
MDX
Stars
446
Forks
1.7k
Avg merge
1d 21h
Merged PRs (30d)
312

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/sentry-docs

All issues in getsentry/sentry-docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.