# Thoughts about Event Handling on Android

DevFeed: [Thoughts about Event Handling on Android](<https://devfeed.tech/articles/thoughts-about-event-handling-on-android-27087.md>)

Original publisher: [Read original article](<https://zsmb.co/thoughts-about-event-handling-on-android/>)

Author: Márton Braun

Published: 2020-06-09T18:00:00Z

Content type: tutorial

Language: en

Sources: [zsmb.co](<https://devfeed.tech/sources/zsmb-co.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [ui](<https://devfeed.tech/topics/ui.md>), [navigation](<https://devfeed.tech/topics/navigation.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [event](<https://devfeed.tech/tags/event.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [marton-braun](<https://devfeed.tech/tags/marton-braun.md>), [mvvm](<https://devfeed.tech/tags/mvvm.md>), [navigation](<https://devfeed.tech/tags/navigation.md>), [ui](<https://devfeed.tech/tags/ui.md>), [zsmb](<https://devfeed.tech/tags/zsmb.md>), [zsmb-co](<https://devfeed.tech/tags/zsmb-co.md>), [zsmb13](<https://devfeed.tech/tags/zsmb13.md>), [zsmbco](<https://devfeed.tech/tags/zsmbco.md>)

## AI overview

This theoretical introduction explains why ViewState alone cannot represent one-time communication from an Android ViewModel to a View. It presents events, also called view effects, for messages and navigation triggers that should be processed only once, and discusses lifecycle awareness and sticky state as related challenges.

## Source excerpt

In MVVM-like view architectures, view state isn't enough to communicate from the ViewModel to the View. They have to be supplemented by some kind of events, which come with several challenges you should be aware of.