# Reactive Apps with Model-View-Intent - Part 4: Independent UI Components

DevFeed: [Reactive Apps with Model-View-Intent - Part 4: Independent UI Components](<https://devfeed.tech/articles/reactive-apps-with-model-view-intent-part-4-independent-ui-components-25457.md>)

Original publisher: [Read original article](<https://hannesdorfmann.com/android/mosby3-mvi-4/>)

Author: Hannes Dorfmann

Published: 2017-02-25T09:00:00Z

Content type: tutorial

Language: en

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

Topics: [reactive](<https://devfeed.tech/topics/reactive.md>), [ui](<https://devfeed.tech/topics/ui.md>), [App](<https://devfeed.tech/topics/app.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [design-patterns](<https://devfeed.tech/tags/design-patterns.md>), [flow](<https://devfeed.tech/tags/flow.md>), [recyclerview](<https://devfeed.tech/tags/recyclerview.md>), [shopping](<https://devfeed.tech/tags/shopping.md>), [toolbar](<https://devfeed.tech/tags/toolbar.md>), [ui-components](<https://devfeed.tech/tags/ui-components.md>), [viewmodel](<https://devfeed.tech/tags/viewmodel.md>)

## AI overview

This blog post discusses building independent, reusable UI components in reactive application architectures such as Model-View-Intent, Model-View-Presenter, and Model-View-ViewModel. It argues that presenters should communicate indirectly by observing shared business logic and describes this approach using a shopping-basket example.

## Source excerpt

In this blog post we will discuss how to build independent UI components and clarify why Parent-Child relations are a code smell in my opinion. Furthermore, we will discuss why I think such relations are needless. One question that arises from time to time with architectural design patterns such as Model-View-Intent, Model-View-Presenter or Model-View-ViewModel is how do Presenters (or ViewModels) communicate with each other?