TheSquatRack.com - workout tracking, analysis, as well as ( macros, body measurements, workout-journals, data-export options, import options, etc.). Current features being deployed include workout routines that span weeks and months, with progressions and deloads of weights, macronutrients adjust up or down (you can have customizable targets like <=10g carbs or >= 1.5g/lb bw protein, etc), adding/removing sets or reps, etc. Also allowing you to schedule workout repetition patterns or meta routines, where you're routine responds to the data logged (use case: your FitBit logged less than 5 hrs of sleep, today's workout should be pushed back a day), and you automatically see that in your dashboard. Of course, all the routines are in a database anyone can review and rate. And since the workout schedule is known, it can log it for you, or just keep it scheduled. more info - https://thesquatrack.com/soon . I've taken it from idea to approaching-sustainable living income on my own. Started in August 2012 as a shits-n-giggles side project, got a bit more serious in October, did a lot from Jan-May, took a couple months off, started back up, decided to go all in, and quit my job at Intel doing preboot storage drivers. Now I'm getting a decent subscription rate considering private-beta (I'm sure that'll change once it's public), but I have no true idea how it's going to scale ... so that'll be fun.

The hard part has been managing burnout, stress, backlog stuff, and generally just everything ... there's so much non-programming stuff that goes into a business. Once I can get someone to manage all that stuff, it'll be interesting to see what I can do with all that extra time, haha. That and revenue/funding. I'm completely bootstrapped and solo on this, no cofounder, nothing ... what a pain in the ass, why can't someone just manage the business stuff and marketing stuff.

As far as revenue, I've gone with a subscription model. I tried to split the features so that as a free user, you have no ads and you can manually everything. Subscribers get power-user-esq tools like slice-n-dice analytics, soon the routines and auto-logging, etc. As far as managing the users, I just try to be honest and transparent with them, and actually take their feature requests into consideration. A lot of times it's userA wants feature ABC and userB wants XYZ, clearly not the same, but if you step back you realize the just want special-use cases of '123', see if there's a couple other cases for it, and build it if it fits with the direction of the site. Sometimes features take a long long time to get implemented, but I get to them because I have several more pre-reqs to do first, I just try to weave them into the pipeline as logically as I can because it'll be a different problem to solve and help the users so why not.

How's that for a response? Any questions or anything? I try to be open and honest about myself and TSR because I want to be proud of what I made, it's like digital legos.