Single-Activity apps have been the officially recommended way to structure Android applications since 2018. However, whether they're simpler to write and maintain compared to multi-Activity apps (or even "Activity per screen" approaches) is still sometimes up for debate.

This talk focuses on the single-activity-focused navigation framework Simple-Stack, which has been in development since 2017.

- Why was Simple-Stack written?
- What does it do, how does it work?
- How to use it?

Overall, the talk will show how Simple-Stack can be used to simplify defining navigation destinations, type-safe argument passing, preserving data across configuration changes and sharing data between screens, and state persistence across process death, using either Fragments or even Jetpack Compose.