How I finished building the MVP just in two weeks
by YSTo validate my theory, I understood that interviews might not be the most effective means to grasp what's functioning and what isn't. I needed the simplest version of an app, one that could be equipped with analytics to analyze actual user behavior and observe their real reactions. Ultimately, what truly matters is how users interact with your app, rather than what they merely express about it.
I dedicated myself to working tirelessly, fully aware that this approach might lead to burnout. However, I felt compelled to give that final push to confirm whether I was heading in the right direction. I coded the entire application in Android Studio using Kotlin, as it was the programming language I was most comfortable with. During this process, I didn't pay much attention to syntax or code quality; my focus was purely on speed, akin to a Hackathon-style development. In just 14 days, I managed to create the initial, albeit somewhat buggy, app. This app allowed users to create lists, prioritize tasks, and employ a Pomodoro Timer to maintain focus.
Upon reflection, I realized that there were a few features I had built that probably could have been deferred to a later stage. Nevertheless, I believe we now possess a minimum viable product (MVP), and I am exceedingly eager to begin analyzing user behavior and gauging their thoughts about the product!
