AndroidScreen

Interface implemented by a Screen rendering class to minimize the boilerplate required for it to drive an Android UI via an appropriate ScreenViewFactory implementation.

Note that it is generally an error for a Workflow to declare AndroidScreen as its RenderingT type -- prefer Screen for that. AndroidScreen is strictly a possible implementation detail of Screen.

You will rarely, if ever, write a ScreenViewFactory yourself. Use one of its companion methods like ScreenViewFactory.fromViewBinding instead.

data class HelloScreen(
  val message: String,
  val onClick: () -> Unit
) : AndroidScreen {
  override val viewFactory : ScreenViewFactory =
    forViewBinding(HelloGoodbyeLayoutBinding::inflate) { screen, _ ->
      helloMessage.text = screen.message
      helloMessage.setOnClickListener { screen.onClick() }
    }
}

This is the simplest way to bridge the gap between your workflows and the UI, but using it requires your workflows code to reside in Android modules, instead of pure Kotlin. If this is a problem, or you need more flexibility for any other reason, you can use ViewRegistry to bind your renderings to ScreenViewFactory implementations at runtime.

Also note that a ViewRegistry entry will override the viewFactory returned by an AndroidScreen. This means that an AndroidScreen implementation can provide a default UI that can be completely customized at runtime via ViewRegistry configuration.

See also ScreenViewFactoryFinder to customize built in rendering types like BackStackScreen.

See also

Inheritors