Remove obsolete launcher integration and reduce navigation jank

This commit is contained in:
Elijah Kuntz 2026-10-19 14:48:08 -07:00
parent ac0a892c5f
commit 2739b278cd
21 changed files with 394 additions and 129 deletions

View file

@ -8,7 +8,7 @@ Follow Android and Android TV best practices. Keep Luma portable across current
- Use documented platform APIs, API-level availability checks, measured capabilities, and resource limits when behavior needs to adapt. Provide a safe portable fallback. Make performance/quality tradeoffs explicit user settings when capability checks cannot reliably predict performance.
- Use the same defaults across devices unless a documented capability requires otherwise. Verify optimizations on both available test devices; record comparable workloads and distinguish measurements from assumptions. Never assume that an optimization on one GPU improves another.
- Keep deployment addresses, repository endpoints, and environment-specific values configurable or in deployment/test configuration. Do not embed a particular household's device addresses in production logic.
- Preserve existing launcher fallbacks, user preferences, and accessibility configuration during development and testing. Restore temporary test changes.
- Preserve installed launchers unless the user explicitly authorizes their removal. Preserve user preferences and accessibility configuration during development and testing. Restore temporary test changes.
## Keys and security