Hey HN!<p>TLDR: I wrote a project to show to potential employers. In the end, I liked the architecture I wrote from scratch so much that I think it deserves to become an open source library on its own. Find the link at the end.<p>I found myself out of a job during lockdown (by my initiative at first, but now it's taking longer than I planned) and decided to start preparing for job interviews by having a sample project to demo to companies in lieu of making a different test or take-home exercise for each potential employer.<p>Being an Android developer, my project should be a simple app that fetches some content and displays it on list. Additionally, you can select one of the rows to see details about the item you clicked.<p>I remembered from my previous time job hunting I had created a few of those apps. I took them as a starting point and wrote a new project that took the best parts of different projects.<p>I started with a MVP project and rewrote it with a MVI architecture - I had grown a big fan of MVI over the last few years. Because I had time (not so great companies were hiring) I did several rounds of tweaking the MVI architecture I was using. After each iteration I liked it more, and could see how this was very generic and powerful that could be used by a lot of people...<p>Eventually I got to a point where that sample project is finished but now I felt like I had something bigger to do: this architecture deserved to see more than my private git repo. I had to turn it to a library!<p>So I wrote a library based on that architecture (there were yet a few more changes). It finally reached 1.0. So far I've heard encouraging feedback from close friends but I think it's time to show it to the world!<p>Please tell me what you think!<p><a href="https://pedroql.github.io/mvflow/" rel="nofollow">https://pedroql.github.io/mvflow/</a>
<a href="https://github.com/pedroql/mvflow" rel="nofollow">https://github.com/pedroql/mvflow</a>