Currently working on the iPhone release of the app . There are things I’m not happy about presently and the previous version of me would have straightened all those things out. I like things to be perfect and just-so. Having studied in Agile and particularly achieving a Scrum Master certification, I’m learning to work with the MVP and prioritise. In the app itself, that sometimes means text mis-alignment, imperfections and things that don’t look …clean. But I know if I focus on these things I won’t move forward with the next updates. Once the iPhone platform is released, I’ll be working on job flow and statuses. At it’s core, the app does it’s job. Someone can log a job, someone can accept it, but it’s nowhere near where the workflow use to be. I know though, if I keep trying to clean up the bits that are not perfect, I won’t get around to building all the features. At some point in the future there will be a round of spring cleaning, but for now, it’s all about getting to the goal. I hate it, but it works.
All of the most common mistakes with MVPs are caused by the same thing. When you are developing your MVP and expose it to a test audience, it’s easy to become distracted. It’s easy to lose sight of what will make you business successful and neglect those advantages to pursue a bigger market segment or create a flashy new feature. This will lead to expensive rework, lack of focus, and a failed product.
https://www.cobbleweb.co.uk/building-mvp-top-mistakes/
It’s natural for people to pick out the flaws in the presentation, but we’re not onto the brand design yet. We’re in the dirty stages of functionality. I want the app to do something impressive and unique to itself, not just be a clone of other ideas. The app was designed to help me learn new things, so copying other ideas and obsessing about presentation is not the one!
Leave a Reply