-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Android Project Creation Enhancements #51792
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
Comments
11 tasks
Assigning to @getsentry/support for routing ⏲️ |
Still wanna do two improvements to the onboarding docs:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Uh oh!
There was an error while loading. Please reload this page.
Background
The onboarding during project creation today is not a dynamic experience which is easy for a user to best understand what options they have to integrate Sentry into their Android application. Considering which major product features they may want to turn on (Performance and/or Profiling) and which tools associated with their development lifecycle they can use to best integrate Sentry. (Gradle, Kotlin, ProGuard & DexGuard). To in the end have their Android application setup to be able to send errors, performance, profiles, and other contextual data around their application with each new build and release (source context) to provide readable stack traces which can be linked to their source code.
Proposal
There is an initiative to continue work in moving onbaording which re-uses our sentry-docs to the sentry repo in React code. There we can provide customer with a more custom experience, with toggles and other UI features to reduce clutter and make the experience adapt to the users needs.
Related:
getsentry/sentry-docs#7258
#48144
The text was updated successfully, but these errors were encountered: