Generates a Baseline Profile for :androidApp — AOT-compiling the cold-start and first-frame code paths so ART doesn't pay the JIT cost on first launch. Targets the google flavor (the variant most users run).

Generate the profile (run on a device/emulator)

./gradlew :androidApp:generateBaselineProfile

Output is merged into androidApp/src/main/generated/baselineProfiles/baseline-prof.txt (mergeIntoMain in androidApp/build.gradle.kts). Commit that file: release builds of both flavors package it via androidx.profileinstaller.

Quantify the win

./gradlew :baselineprofile:connectedGoogleBenchmarkReleaseAndroidTest

Compare startupCompilationNone vs startupCompilationBaselineProfiles in the output.

Scope / TODO

The journey (BaselineProfileGenerator) is cold-start only, since CI has no paired radio. Extend it with post-connection screens (node list, map, message thread) once a fake transport or connected device is wired into the harness — a more representative journey yields a better profile.
For hermetic CI generation, swap useConnectedDevices = true in build.gradle.kts for a Gradle Managed Device.
Only google is produced, and f-droid ships that same profile from src/main. Add a second flavor here if the f-droid startup path ever diverges enough to matter.