4 ms·
I've lived for 10 years solely from the revenue of an indie web app I wrote, so I guess my experience is applicable in so far as you're also doing bootstrapped/
by semicolonandson 6y ago
I've lived for 10 years solely from the revenue of an indie web app I wrote, so I guess my experience is applicable in so far as you're also doing bootstrapped/shoestring investment web applications.
I just started a YouTube channel where I give behind-the-scenes looks at how the technical and the business sides connect.
Specifically, I'm covering things like
- Experiments in SEO (from outsourced freelance content to microdata, to preserving SEO juice when user-generated content changes)
- Basic Google Analytics game
- The surprising hidden costs with payment providers like PayPal/Stripe
- AB testing
- The hell that is sales tax accounting
- Using data to decide what features to build (minimal viable features), so you don't over-invest limited resources in uncertain rewards.
- Technical cost-cutting (e.g. having a shitty looking admin area, knowing what not to test)
- Handling customers gracefully (e.g. setting expectations about response times, letting them yell at you and still feel zen, why you should always give refunds)
So, for a frank look at one particular programmer's/solopreneur's take on the above, you might get value from my channel: https://www.youtube.com/watch?v=aCzT-LQI6x0 https://www.youtube.com/watch?v=aCzT-LQI6x0
- bradleykingz 6y agoI'd like to know more about the last point. Why should I always give refunds? "letting them yell at you and still feel zen". I don't know how to phrase the question, but is there something you came to understand in order to get there?