In 2011 I released an app which was an education in MVP for me. I knew there was an free open source Java library that parsed Microsoft Access Library, so one

In 2011 I released an app which was an education in MVP for me. I knew there was an free open source Java library that parsed Microsoft Access Library, so one day I had the idea to write an Android app for it. As there was no competition at all to parse Microsoft Access databases on the Android device(1) at that time, I figured I could release it without much features, so four days after having the idea I release the app - you can load one database and then one table from the disk and page forward (not backwards) through it. I had an immediate user base despite so few features as there was no alternative at the time. The education was in what the users wanted. I had ideas about what users might want next, like column sorting, and was thinking of what big O sorting method to use for doing that. My other ideas for features people might want were more technically complex than that. No one asked about column sorting in the first few months. First they asked if you could page backwards through the table. Then they wanted search. Then they wanted case insensitive search. Then they wanted wildcard search. Then someone said they always loaded the same database, and had to go through the filesystem to find it each new session, and could I have a recent files tab. I had no idea what features users thought were important. Some were probably important to more than one person, as I got multiple comments and e-mails asking for search. Pretty much everything I implemented was something asked by multiple users. The only exception to that is if one user asked for a feature, but it was simple and obviously a good idea. Some features multiple users asked for, but I put on the backlog because I knew it would take a lot of time to implement correctly. It was an unusual scenario in that I had a sizable user base who loved that they could look at their Microsoft Access databases on their phones, even though it initially was written in four days. The main lesson was all these ideas I had about the challenges of which big-O algorithm to use were for features users never asked for, and a lot of what they wanted was pretty simple. I knew users would probably want to read Microsoft Access databases on their phones, but I had no idea at all which features of doing that were most important to them until they told me.