log 127: next

process

With my app coming back into the world of active testing, I’m not sure of how to move forward. I haven’t put much thought into what I’m going to do while the app is testing. This is the start of the next big step so I have to plan carefully. From one of my previous meetings I was able to talk to a big software tycoon in Singapore. For his products, he has a team working on the current release and another team working on the next release. After a new version is made public, the team works on quick bug fixes for two weeks while the other moves onto the next. After that, they start work on the release that comes after next. I thought it was a clever system. However, as a solo coder with no help. I have to play it even slower. Release the first version, bug fix asap, then work on the new features. One of my thoughts was to work on getting more stuff out quickly but more isn’t necessarily better. Another piece of advice I was kindly given was to see what my users actually use. There isn’t a point developing an idea if the statistics show people won't use that type of function. I need to implement trackers to see what buttons are being pressed. Playing it slow will definitely help narrow down what I need to focus on moving forward, especially with school coming soon.