<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Mvi on codeskraps</title>
    <link>https://codeskraps.com/tags/mvi/</link>
    <description>Recent content in Mvi on codeskraps</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <managingEditor>me@codeskraps.com (codeskraps)</managingEditor>
    <webMaster>me@codeskraps.com (codeskraps)</webMaster>
    <lastBuildDate>Fri, 27 Sep 2024 13:45:09 +0200</lastBuildDate>
    <atom:link href="https://codeskraps.com/tags/mvi/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Simplifying MVI Architecture</title>
      <link>https://codeskraps.com/posts/2024/mvi_architecture/</link>
      <pubDate>Fri, 27 Sep 2024 13:45:09 +0200</pubDate><author>me@codeskraps.com (codeskraps)</author>
      <guid>https://codeskraps.com/posts/2024/mvi_architecture/</guid>
      <description>&lt;p&gt;Model-View-Intent (MVI) is a powerful architectural pattern for building user interfaces, especially in Android development. In this post, we&amp;rsquo;ll explore a helper class that simplifies the implementation of MVI, making it easier to manage state, handle user intents, and emit actions in your application.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
