When do you stop pouring milk?
I prefer just as the cereal starts to show its buoyancy.
I prefer just as the cereal starts to show its buoyancy.
Only thing missing is a gerwalk mode. What other wall scrolls do you like?
I ♥️ both.
I wanted to figure out how much of my online gaming performance issues were my home network, my isp, or the actual game servers. This is the tool i made for the off network stuff. The other part is not hostable on a webpage, but the screen shot of that tool is in the coming soon section.
I would love to hear what I'm missing from this or things that you think are wrong.
https://gramsapps.com/connection-quality/
I don't have trackers or cookies on this page. I respect privacy over usage stats.
Still prefer no spoon cereal eating. Part of this complete breakfast.
I have a pretty hefty startup but I didn't want to have side projects that didn't have real world application since the real world part is where things get tested. So i started making useful web apps for things that mattered to me. Instead of one big thing, I build small single-purpose browser apps like: a swim log, a to-do app that lets you snooze tasks with an honest excuse, a line-of-sight checker for figuring out if you'll actually see the fireworks from your yard, plus a handful of arcade games.
The unlock wasn't any one app. It was building the account layer once.
One auth + profile system that every app plugs into. New app = new front end, zero new backend work. Sign-in, saved progress, leaderboards, and the subscription tier all come for free the moment I point a new project at it. Ship time for app #10 was a fraction of app #2.
Second-order benefit I didn't expect: cross-promotion is free. Someone who came for a game already has an account when they hit a utility. No second signup wall. (don't even need an account but it does make resuming play or scenarios easier)
What I'd tell past me: build the boring shared layer before app #3, not after app #6. I rebuilt auth 2 times because I treated each project as standalone.
For transparency — I'm not strictly no-code, I write the code with heavy AI assistance. But the strategic point is the same either way: your leverage is the infrastructure you reuse, not the app you're currently excited about.
Curious how others here handle multi-product auth. Do you keep products fully separate, or share an account across them?
Mine's at gramsapps.com if you want to see what this looks like in practice — all free, no signup required to try anything.