The FitnessTracker project is going extremely well, but thanks to some superior help from alpha/beta testers and other friends, I found another area that the software touches where with some slight changes, it would open up an entirely new market. In this particular case it started with some feedback from a beta user that the photo/timelapse part of FitnessTracker was the killer feature that made it different from other applications that help track exercise, nutrition and overall fitness. So I started using it to keep track of my own photo problem and the whole 78 solutions methodology kicked into high gear when I started to remember all the problems I had with photos when I published the Regina Streets Magazine and later, End Magazine.
One of my principles is that I reuse software as often as possible. In this case, I have been able to lift a photo module directly out of the FitnessTracker code, drop it into my starter scaffolding, write another two modules and create a totally different application with a different use case. And so StorePhotos was born with a minimal of heavy lifting, such a small amount that it will actually release before FitnessTracker despite there being a several month difference in time put into the project.
Economically, taking reusable modules to this level has given me the freedom to deliver some of the most common wishes I hear from users. I can provide actual tech support on software that is highly private and that people own instead of subscribing to. Moreover, I can make it extremely easy to install via the Microsoft App Store and give them the freedom to use most features without an internet connection. Finally, I can build support software and context driven help right into the application, keep that updated and not have to force users into subscriptions and a life of drip marketing.
The technical benefits are more difficult to manage but more lucrative if they are managed well. Having the same major module at the heart of two projects that solve different problems gives me the opportunity to get more feedback on that module. If I manage this process properly, I have the opportunity to deliver a better experience to everyone. If I manage it poorly, each project will deviate from its target according to feedback received on the other so I will end up with two really crappy applications. So there are pitfalls but I have been doing this for a long time and am confident in my ability to manage the process.
Both FitnessTracker and StorePhotos will be released later on this quarter and I am excited to get them out - they’re both major parts of my life and I am excited for them to see the light of day.