I built and run SugarWOD (https://www.sugarwod.com). SugarWOD is a workout solution for CrossFit gyms including apps (iOS/Android), website, plug-ins, and TV support. Was a solo, free service for the first 3 years. Converted to a paid model 1.5 yrs ago, and as of a few months ago have part-time contractors helping with tech/ops, mktg, and support.
I agree with novaleaf that a very broad skill set is needed, though I'd add that it might be enough to at least be interested in all the areas mentioned. You can learn a lot along the way, which is a big part of the fun. If you're focussed on making a great Product (capitalized product = the entire customer experience including everything from web copy, onboarding, support, performance, features, etc.) all of it is important.
As an aside, I think it is this breadth that allows someone to be a "10x problem solver", which to me is 10x more interesting than being a "10x developer". Code is a means to an end.
"Success" is a malleable and personal term, but by typical SaaS metrics SugarWOD is a success. Millions of workouts logged, paying customers, profitable, growing quickly.
More importantly, I get huge satisfaction working on something I feel passionate about, and I really love running the entire business from a laptop anywhere in the world (though I'm usually not far from Colorado :)
I use SugarWOD every day, it powers the crossfit gym I go to. Gotta say you did a great job, I can't imagine such a community built around the gym without it.The fistbumps are a really great feature!
Untrue, at least in the case of my 9 year old. He loves writing Javascript "apps" from bitsbox (bitsbox.com). I learned by poke'ing on an Apple ][ because that was the tech of the day. Apps are the tech of the day for kids and he loves seeing the things he can create.
> I would need a great incentive to switch how I take notes. I'm thinking a bunch of other developers thought the same thing.
Just like the OP, you've generalized your personal experience to other developers. It is an easy trap to fall into. I agree with the takeaway called out in another comment: validate the idea as objectively as possible and as early as possible.
I agree with novaleaf that a very broad skill set is needed, though I'd add that it might be enough to at least be interested in all the areas mentioned. You can learn a lot along the way, which is a big part of the fun. If you're focussed on making a great Product (capitalized product = the entire customer experience including everything from web copy, onboarding, support, performance, features, etc.) all of it is important.
As an aside, I think it is this breadth that allows someone to be a "10x problem solver", which to me is 10x more interesting than being a "10x developer". Code is a means to an end.
"Success" is a malleable and personal term, but by typical SaaS metrics SugarWOD is a success. Millions of workouts logged, paying customers, profitable, growing quickly.
More importantly, I get huge satisfaction working on something I feel passionate about, and I really love running the entire business from a laptop anywhere in the world (though I'm usually not far from Colorado :)