@robj3d3 i saw both of his interview on starter story but with yours i really connected because you actually go into the details and i absolutely loved it!
wish to meet you someday and thank in person for bringing him on and getting a bit more in depth than the upper layers.
> make b2c mobile app
> find format that gets 100k+ views on tikt0k
> recreate with app mascot and plug app in organic way
> once you crack it and working, scale using post bridge
> relax and enjoy $0 cost marketing
10 years to build the body
10 years to build the skills
10 years to build the audience
I don't want it to look like it was easy money.
Years of hard work compounded.
Social media algorithms only surface successful stories, but I spent 7 years of my entrepreneurial life in a void state where almost no one bought my products. 90% of my 36 startups failed.
You can read about my failures in my free mini-book: https://t.co/AXPh8ekCx2
Tech advice for mobile apps.
• From a sénior swe & ~$13k/m indie dev.
1. Never use Firebase.
Countless catastrophic data breaches on thousand of android apps, as well as KFC, Subway etc. The architecture makes huge mistakes too easy.
2. Just use Cloudflare.
Broadly the best infra right now. R2 is FREE egress. You pay nothing to serve assets in your app. At scale you'll pay for storage & read/writes. R2 scales in price way better than Superbase, Convex, even S3!
Cloudflare D1 is dramatically cheaper than Supabase or Convex databases for realistically the same amount of management. Convex is magic for heavy realtime features, but you're gonna pay for it.
Pair D1 with Cloudflare workers & R2, and you've got a backend that will scale insanely cheaply to hundreds of thousands of users. At colossal scale, I'd look into something like Google Spanner or Planetscale.
3. Give 1% to Superwall or RC.
The amount of value you get from a managed subscription platform is worth 1% of your revenue. You also only pay once you hit a milestone (i.e 5k/m). Remote paywalls, AB testing, refund handling, etc.
4. You probably don't need Apple Sign In.
Unless you have heavy social features. Even then, rolling your own basic auth is simpler and is less friction. Tie device ID to an anon ID. Only downside is device sharing & if user deletes app, data is inaccessible.
5. Be very careful with what MMP you use.
Some may not be compliant with Apple's ToS in regards to fingerprinting. Also, be careful about the pricing models: they say it's x per conversion, but it's actually per install. Hopefully RC and Superwall will make their own robust in house offerings soon.
6. Stay compliant with Apple ToS.
Proactively comply. This means taking your review out of onboarding before they ask. Have discussions with reviewers about anything slightly spicy. You'll be surprised by the outcome. Regardless of how we feel or think about the Apple ToS, your dev account is just not worth 3% extra conversion. Never mislead the user.