# Presenters don't need lifecycle events

DevFeed: [Presenters don't need lifecycle events](<https://devfeed.tech/articles/presenters-don-t-need-lifecycle-events-25465.md>)

Original publisher: [Read original article](<https://hannesdorfmann.com/android/presenters-dont-need-lifecycle/>)

Author: Hannes Dorfmann

Published: 2016-03-24T09:00:00Z

Content type: opinion

Language: en

Sources: [Hannes Dorfmann](<https://devfeed.tech/sources/hannes-dorfmann.md>)

Topics: [mvc](<https://devfeed.tech/topics/mvc.md>), [Library](<https://devfeed.tech/topics/library.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [code](<https://devfeed.tech/tags/code.md>), [components](<https://devfeed.tech/tags/components.md>), [library](<https://devfeed.tech/tags/library.md>)

## AI overview

The article argues that MVP Presenters in Mosby do not need Android lifecycle callback methods. It says Presenters should coordinate the view, transform model data for presentation, and bridge to business logic, while only tracking whether a view is attached. It discusses LightCycle as a way to delegate lifecycle logic into smaller components, but cautions that adding lifecycle methods to Presenters can merely relocate complex code.

## Source excerpt

I have been asked several times why Presenters in Mosby (MVP library) don't have lifecycle callback methods like onCreate(Bundle), onResume() etc. Also the awesome guys over at SoundCloud have published a library called LightCycle that helps break logic out of Activity or Fragments into smaller containers bound to the parents Activity's or Fragment's lifecycle.