Android UI (Compose & Views).

The Android view layer: Jetpack Compose, activities/fragments, ViewModel and navigation. Covers 6 topics.

• Android UI (Compose & Views) · 1 of 3

  ViewModel & LiveData

  In current Android architecture guidance, which observable type does the team recommend for new ViewModel-exposed UI state instead of LiveData?

  AStateFlow from kotlinx.coroutines, collected on the UIBMutableLiveData wrapped in a Transformations.map callCRxJava BehaviorSubject bridged through LiveDataReactiveStreamsDSharedFlow with replay = 0, emitting each change once

• Android UI (Compose & Views) · 2 of 3

  Activities & Fragments

  How do Fragments communicate with each other in modern Android?

  ABy calling methods directly on each other through the FragmentManagerBA shared ViewModel, the Fragment Result API, or Navigation SafeArgsCThrough static singleton objects that both fragments referenceDUsing BroadcastReceivers registered in each fragment's onCreate()

• Android UI (Compose & Views) · 3 of 3

  Navigation Component

  detail is a full-screen destination, not a dialog. Once the transition to it has finished, what does this code print for the previous back-stack entry?

  val prev = nav.currentBackStackEntrynav.navigate("detail")// after transition settles:val state = prev?.lifecycle?.currentStateprintln("prev=$state")

  Aprev=DESTROYEDBprev=CREATEDCprev=RESUMEDDprev=STARTED