<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>architecture on Dan Lowe</title>
    <link>https://danlowe.me/tags/architecture/</link>
    <description>Recent content in architecture on Dan Lowe</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <managingEditor>dan@danlowe.me (Dan Lowe)</managingEditor>
    <webMaster>dan@danlowe.me (Dan Lowe)</webMaster>
    <lastBuildDate>Wed, 14 Aug 2019 10:59:50 -0400</lastBuildDate>
    
	<atom:link href="https://danlowe.me/tags/architecture/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Android MVI Simplified</title>
      <link>https://danlowe.me/post/2019-08-15-mvi/</link>
      <pubDate>Wed, 14 Aug 2019 10:59:50 -0400</pubDate>
      <author>dan@danlowe.me (Dan Lowe)</author>
      <guid>https://danlowe.me/post/2019-08-15-mvi/</guid>
      <description>Why am I here? When I first started jumping into MVI and learning about it, there were few if any sources that I remember being complete enough for me to implement the pattern on my own. I don&#39;t like that. I could understand the benefits of it, but couldn&#39;t picture how it would look in production without a basic understanding. I want to solve that problem for the next person, so let&#39;s build an MVI app with only the libraries available in a new Android Studio project.</description>
    </item>
    
  </channel>
</rss>