Open
Description
We'd like to start managing the bundle size of the SDK more actively.
For that, we'd like to start taking some numbers during PRs, and with the end goal of posting as a PR comment the bundle size and a diff to main
.
Approaches considered and characteristics of them:
Measuring the aar
- Either we do a naive measurement solely of our package without considering dependencies. Or we need to recursively find all dependencies and measure their sizes.
- There are multiple slices on each aar, for each abi.
- We'd need to compile for a specific one, or peek into the aar to calculate specific architectures.
Measuring the final app
- We can run proguard on the sample app which has heavy use of our features and measure more realistically the "overhead" in bundle size.
Suggested Phases:
- Measure size of sample app
- Post size as a comment to PR
- Add flavor without Sentry and measure size
- Post both to PR the metrics
- Sizes (like JS bundle on getsentry/sentry) to PR
- Method count
- Diff (using JakeWharton/diffuse or Tencent/matrix@master/matrix/matrix-android/matrix-apk-canary)
- Proguard the sample app (both withSentryAndNdk and withoutSentryOrNdk flavors)
- Document size
- For example: https://pspdfkit.com/guides/android/current/faq/framework-size/
- Not having Kotlin so kotlin std doesn't affect size
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Backlog