\n
![](\"https:\/\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEizVuum2Jg1s5Y5EQmfuXrjm8QqcqxdAUDveRe-CSS4ZGVeNG9VFEizeayzpolJ5oCPSfoNmkT3RdS3Z-g1-aXzDBWwJtjOzflCgt657KFitWQby_GcYa5PO4PBN_7IUmG4CC9BvOw8mFFIMPai_R9EoPIcWZkPDV0aAAs20amwT6Lr2oXi5Yfe-e7b1t0\/s1600\/announcing-jetpack-navigation-3-compose-google-io-2025.png\")
<\/p>\nPosted by Don Turner – Developer Relations Engineer<\/em><\/p>\n Navigating between screens in your app should be simple, shouldn’t it? However, building a robust, scalable, and delightful navigation experience can be a challenge. For years, the Jetpack Navigation library has been a key tool for developers, but as the Android UI landscape has evolved, particularly with the rise of Jetpack Compose, we recognized the need for a new approach.<\/p>\n Today, we’re excited to introduce Jetpack Navigation 3<\/b>, a new navigation library built from the ground up specifically for Compose. For brevity, we’ll just call it Nav3 from now on. This library embraces the declarative programming model<\/a> and Compose state<\/a> as fundamental building blocks.<\/p>\n The original Jetpack Navigation library (sometimes referred to as Nav2 as it’s on major version 2) was initially announced back in 2018, before AndroidX and before Compose. While it served its original goals well, we heard from you that it had several limitations when working with modern Compose patterns.<\/p>\n One key limitation was that the back stack state could only be observed indirectly. This meant there could be two sources of truth, potentially leading to an inconsistent application state. Also, Nav2’s NavHost<\/span> was designed to display only a single destination \u2013 the topmost one on the back stack \u2013 filling the available space. This made it difficult to implement adaptive layouts that display multiple panes of content simultaneously, such as a list-detail layout on large screens.<\/p>\n Nav3 is built upon principles designed to provide greater flexibility and developer control:<\/p>\n <\/p>\n To give you an idea of how Nav3 works, here’s a short code sample.<\/p>\n <\/p>\n To get started, check out the developer documentation<\/a>, plus the recipes repository<\/a> which provides examples for:<\/p>\n We plan to provide code recipes, documentation and blogs for more complex use cases in future.<\/p>\n Nav3 is currently in alpha, which means that the API is liable to change based on feedback. If you have any issues, or would like to provide feedback, please file an issue<\/a>.<\/p>\n Nav3 offers a flexible and powerful foundation for building modern navigation in your Compose applications. We’re really excited to see what you build with it.<\/p>\n Explore this announcement and all Google I\/O 2025 updates on io.google<\/a> starting May 22.<\/p>\n<\/ul>\n<\/ul>\n<\/div>\n![](\"https:\/\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEiAaXdjIziCSWC6AxDELcBes5wYDD03GByPFm8jipBg5cilU9-3w_50B5RhF1BXzHUY0HTmp-WEAeshuqLmBpdK9onZAys4S3Pv2izciuQxqlTL23YaOCpaGMoazKbXUCHr5TZcDadxWbDdUDAX_1GS_iN133wFnxH-Qal7icpfcZhKZ2aNy3FaJ0zIDds\/s1600\/new-in-jetpack-compose.png\")
<\/a><\/p>\nWhy a new navigation library?<\/span><\/h2>\n
<\/div>\nFounding principles<\/span><\/h2>\n
\n
\n
\n
\n
<\/div>\nKey features<\/span><\/h2>\n
\n
\n
\n
<\/div>\nBasic code example<\/span><\/h2>\n
\/\/ Define the routes in your app and any arguments.<\/span>\ndata object Home\ndata class<\/span> Product<\/span>(val<\/span> id: String)\n\n\/\/ Create a back stack, specifying the route the app should start with.<\/span>\nval<\/span> backStack = remember { mutableStateListOfGet started and provide feedback<\/span><\/h2>\n
\n
\n