The first version of this app didn’t die from a bug or from losing interest. It died because Reddit changed its API pricing in 2023 and the math stopped working overnight. That’s the honest origin story for everything about how the current version is built, so it’s worth actually writing down: what happens when Reddit changes the rules again, and what I’ve done about it.
What Actually Happened in 2023
Reddit announced API pricing that made sense for large companies training models on Reddit data and made no sense at all for a solo dev running a scroller app for a few thousand users. There wasn’t a grace period that mattered — the pricing made continuing to run v1 a losing proposition, full stop. I shut it down rather than either eating a cost that didn’t pencil out or trying to pass it on to users of a free tool. That’s not a dramatic story. It’s just what happens when your entire product sits directly on top of someone else’s API and they decide to change the terms.
The Actual Risk Hasn’t Gone Away
I want to be straight about this: rebuilding Redinfinite didn’t remove the dependency. It’s still built on Reddit’s API, because there isn’t another way to build something that reads Reddit. Anyone who tells you they’ve “solved” third-party API risk is usually just describing a different flavor of the same exposure. What I actually did was build the current version to be less fragile to that risk, not immune to it.
What’s Different This Time
No assumption that pricing stays flat. The whole point of watching what happened to v1 is that I don’t get to assume the current terms are permanent. The app’s cost structure is built with margin, not run at the exact edge of what current API pricing allows — so a moderate pricing change is absorbable instead of immediately fatal.
Caching that actually reduces call volume. V1 hit the API more than it needed to, because it was built before I had to think hard about call efficiency. The rebuild caches aggressively where content doesn’t need to be live-fresh, which lowers both cost exposure and the blast radius of any future rate-limit tightening.
A monitoring habit, not a monitoring system. I don’t have some sophisticated early-warning dashboard. What I do have is a habit of actually reading Reddit’s developer communications instead of finding out about a change from a user’s bug report, which is exactly how v1’s death played out in real time — I found out from the fallout, not from paying attention.
What Still Worries Me
Honestly? The same thing that killed v1 could still kill this version. A sufficiently aggressive pricing or access change from Reddit doesn’t care how well-architected the caching layer is — if the terms make the product uneconomical, the product stops. I’ve built in margin and efficiency, not immunity, and I think pretending otherwise would be dishonest.
What I’ve actually gained isn’t safety. It’s a longer runway and a faster reaction time — the ability to absorb a moderate change instead of getting killed by it outright, and to notice a change coming instead of finding out after the fact. That’s a meaningfully better position than 2023. It’s not a guarantee.
Why I’m Building This Way Anyway
Some people would read all of this and ask why build on a foundation you don’t control. The honest answer: there isn’t a version of “an app that shows you Reddit” that doesn’t depend on Reddit’s API. The choice isn’t between dependency and no dependency — it’s between building on that dependency carelessly, the way v1 did by accident, or building on it with the 2023 lesson actually incorporated. I’ve done the second one. I don’t know if it’s enough. I know it’s better than not doing it.
