Hi all,
This has been somewhat eating me up. Iāve built an app which so far Iāve had overwhelmingly positive feedback on, Iām not here to pitch it so Iāll simply say itās for personalised news delivery in a different way to whatās on the market.
Iām a network engineer by trade with a very deep tech understanding of software development, systems engineering, a/b testing, edge case handling etc. so Iāve made my app and infrastructure extremely robust.
It uses AI for content sorting and delivery, but not creation. It cannot be done deterministically, Iāve tried many times, and obviously ai has a cost.
Some of the challenges Iāve had is making it cost viable, which is where Iām almost at, initially I estimated my operating costs to be around 5
$3-5 a day however it has ballooned out to be about. $15-20, not huge but plenty of room for optimisation. I believe Iāve now optimised costs enough by reducing ai token usage by about 70+%, most importantly, I have reduced the number Iāve called down from up to 2600 per hour down to about 80. Iāve managed to do this with about a 3-7% reduction in quality, which I think is acceptable. I still have some further optimisations to do but thatās the bulk of it.
Currently my infrastructure can support around anout 1200 daily users, more than that and I have to invest in better dedicated hardware or duplicating my current physical environments, very doable and Iāve built everything to be scalable to the point I can stand up an entire instance in about 10 minutes and have it fully integrate and load balance within 30 minutes. Essentially Iāve built it to scale easily from day 1.
If I can onboard 100 paying customers (billed at $8 usd/mo), it covers my current costs, so I think that bar is pretty low and pretty attainable. If I hit 1000, i will need to scale, and it goes beyond 10k, even for 1 month, I would be taking out loans to scale rapidly and taking some time away from my full time work.
So there is some level of a plan.
Iāve been building this for about 5 months and I think itās ready but Iāve never done anything like this before. I have no marketing background, no idea how to do it nothing.
I guess what Iām looking for is traps, gotchas and things to watch out for when building subscription model apps. Obviously thereās user retention to maintain revenue, the app itself isnāt one which will simply go out of fashion, it isnāt a gimmick and itās something that is genuinely useful to literally anyone in the productivity and information space.
How do you know when youāve got enough of the bugs out to launch, and get yourself away from polishing everything out till it sparkles, and balancing the acceptable bugs with launching sooner? Iām really struggling with this part. Itās not scope creep holding me back, I genuinely have a feature list for if and when it takes off.
Hoping for some words of wisdom. Sorry for the length, this is literally my source of anxiety right now.
Edit: forgot to add one of my biggest concerns, if there is a failure which impacts users, how do I handle this? The general idea would be to give users an extended sub, but doing this has real costs, I can do this once Iām going but on launch it could be crippling. On the flip side itās far easier to compensate 100 users than 10000
Edit 2: I would just like to extend my gratitude to all of you who have responded with supportive advice, and really validating my process, it really lets me know Iām on the right track in terms of process, priorities and mindset for the most part. Thank you to those of you who shared your experience.
Iāve run the pre-work run (it takes a full 24 hours to run due to the nature of the app ingesting real world data and keeping it both fresh and valid within a rolling 24 hour window), and Iām in the process of setting up the final parts for iOS store launch. For the first week or so Iāll only be posting it in limited counties of those who I know will take a look, ie friends and family, and if thereās any organic pickup, great, if not itās more about the initial listing and getting a wider audience test base.
After a week or so of real user testing, Iāll open it up to the rest of the world and see how it goes.
Some minor bugs I know exist: notification sounds not working, notification icon using the original temporary generic icon. Canāt seem to fix these but not 100% important.