The Complete Guide to Android Value Passing: Control Your Architecture, Control Your “Passing”!

In Android app development, the thought “I need to pass this value to another class!” pops up all the time. Yet the best way to do so changes with context and goals. The more approaches you know, the better you can choose the one that fits your situation and product. And when it comes to passing values, architecture is inseparable from the discussion. This session starts with the fundamental principles of Android app architecture, then surveys the many techniques for passing values and weighs their architectural pros and cons. Strengthen your design skills and build apps that pass data “just right”! Agenda - First things first: core architectural principles!! - UDF (Unidirectional Data Flow) - SSOT (Single Source of Truth) - Many ways to pass values - Just stick it in the parameter!!!! - The most basic method—yet not always enough… - Concrete examples of when and why it falls short - “GO-TO” style (notify multiple components) - Broadcast - Event Bus - Passing values during navigation - Intent / Bundle Standard between Activity and Fragment. - SavedStateHandle Works with ViewModel to restore state after process death. - Navigation Compose Easy to pass values as destination arguments in Compose navigation. - Passing values via DI - Field injection - Constructor injection - Stream and receive state - StateFlow - LiveData - For each method, does it preserve UDF? Does it honor SSOT? - Wrap-up (Translated by the DroidKaigi Committee)

• 

  みっちゃん STORES inc. , Android developer