With FitnessTracker in beta (again), it was time to start reusing the code. One of my goals going in was to build an entire application with components so loosely coupled that I could pull some out and create a totally different application. Well, it turns out that I can. And StorePhotos is proof.
I caught the publishing bug a long time ago and struggled under the weight of photos, credits and permissions. And through the GT Surveillance years, I developed a keen understanding of just how much storage photos can eat up. So I repackaged a large part of FitnessTracker to fill that need. So far, it's worked really well - despite my better judgment, 78solutions is turning itself into a publication and StorePhotos has been excellent so far. Heck, I just took a bunch of pictures off a memory card older than my child, renamed them and transferred them over to an external hard drive in three clicks. Then went through, tagged some as publishable for two stories that I'm working on about tech in the 2000s and it all felt seamless.
Pricing is up in the air, but I want to make it really really cheap. Indie publishing is really expensive and during the End Magazine days, I talked to lots of publishers who had cobbled together solutions based on free tech. Not because they liked to tinker but because they couldn't afford more. I honeslty can't afford to support a free product right now, but I will keep it as cheap as possible and once again, it's not subscription software, has no ads or in app purchases and I can only access application data if you choose to send it to me.