A Google Android performance engineer shares how the team improved app startup and search latency by reordering initialization steps in the Android Google app. The key insight was that initializing the web fragment (which renders search results) too late caused high search latency, but moving it earlier caused startup latency to spike 5x. The solution was 'intentional initialization': deleting unused code, reordering initialization blocks to match when they're actually needed, and leveraging gaps in the startup timeline. Specific wins included prioritizing keyboard display before secondary UI (the biggest growth driver for the team in Q2), moving Chrome Custom Tabs pre-warming later, and pre-warming WebView profile and instance earlier. The strategy reduced startup interactive latency, cut cancellation rates, and improved search latency simultaneously.
Sort: