# Handling Transient Events

DevFeed: [Handling Transient Events](<https://devfeed.tech/articles/handling-transient-events-30594.md>)

Original publisher: [Read original article](<https://ryanharter.com/blog/2019/07/handling-transient-events/>)

Published: 2019-07-26T15:00:00Z

Content type: tutorial

Language: en

Sources: [Blogs on Ryan Harter](<https://devfeed.tech/sources/blogs-on-ryan-harter.md>)

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

Tags: [android](<https://devfeed.tech/tags/android.md>), [events](<https://devfeed.tech/tags/events.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [livedata](<https://devfeed.tech/tags/livedata.md>), [navigation](<https://devfeed.tech/tags/navigation.md>), [notifications](<https://devfeed.tech/tags/notifications.md>), [view](<https://devfeed.tech/tags/view.md>)

## AI overview

This article explains why LiveData is well suited to persistent view state but less suited to transient view events. It distinguishes state that should be saved and restored from one-time events such as notifications, navigation, dialogs, and errors, using an Android app example.

## Source excerpt

LiveData has become an important part of many Android apps. With it's elegant handling of the complex lifecycle inherent in many Android components, its understandable that we would try to use them everywhere we can. LiveData, however, was designed with a very specific use case in mind. Its intended to hold data for use by views in an application, and make that data available in a lifecycle-safe fashion, while helping us reduce the need to reload data unnecessarily.