Migrating App to Navigation 3: Pain, Overtimes, and Hotfixes

This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).

A first-hand account of migrating a 170+ screen Android app from Navigation 2 to Navigation 3 in early 2026. The author details the two-week solo migration effort, key motivations (adaptive layouts, MVI alignment, Google's large-screen push), and unexpected challenges including the lack of incremental migration support, missing Bottom Sheet support in Nav3, deeplink restructuring, and a post-release serialization crash requiring a hotfix. The post also reflects on how Claude Code's later Nav3 migration support would have halved the effort, and closes with practical advice on when not to migrate and lessons learned around serialization, Bottom Sheet stack management, and stabilization time.

12m read timeFrom proandroiddev.com
Post cover image
Table of contents
Life with Navigation 2Why We Decided to MigrateWhat Convinced UsHow the Migration Happened and Is There Life After It?Overtimes. Why?The UnexpectedDeeplinksGet Tetiana Synytsyna’s stories in your inboxStabilizationThe ReleaseProactivity Is Good, But Not AlwaysConclusions and Lessons LearnedWhen I Would NOT Recommend MigratingThe AdvantagesSummary
852 Impressions