History, Principles and Concepts of the Decompose Navigation Library
summary
A talk about the Decompose navigation library for Android and Kotlin Multiplatform that covers its history, design principles, and key architectural decisions. It explains how Decompose provides flexible, scalable, and compile-time type-safe navigation, describes the main library APIs, and shows how and why to build custom navigation models to improve testability and fit different project sizes.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:09What is Decompose
- 3:54Architecture and components
- 13:30Library history
- 29:15Navigation API and boilerplate
- 36:22Framework or library
- 40:15Q&A
related talks
45mThe Final Word in Android Navigation
22mDecompose your Kotlin Multiplatform project into feature modules
37mHow to Avoid Chaos: Navigation as a Separate Logical Layer
22mDecompose your Kotlin Multiplatform project into feature modules
27mManaging In-App Navigation with the Navigation Architecture Component
30mBreaking the Rules: Dynamic Navigation in Modularized Apps
41mNav2, Nav3… Or Roll Your Own? — Building to Understand Nav3’s Design Intent
06mType safe, multi-module best practices with Navigation Compose
