Simplified Single-Activity Apps using Simple-Stack
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.
Guide to destroying codebases: the demise of clever code
We try to write the best code possible, simplify future maintenance, optimize for code reuse, and apply best practices and principles to help us achieve this.
However, what if this can serve as a double-edged sword?
In this talk, we'll analyze different ways and look at various examples on how through either under-use or over-use (or mis-use) of certain principles, we can inadvertantly introduce enough error surfaces, unintended complexity, or accidental coupling - that the only hope for a fix is a rewrite.
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top