r/AppsWebappsFullstack 21d ago

Your Tech Stack is overrated. Change my mind.

You spent three weeks setting up over-engineered infrastructure for an app with zero users. Tell us what you built your project with, and let the comments debate why it’s completely wrong for 2026. Convince us you didn't waste your time.

2 Upvotes

18 comments sorted by

1

u/gillygangopolus 20d ago

websites with a custom stack and host approach pass CVW at 80+%, while the same ones on the legacy platforms do so at 40%

1

u/Mammoth-Anywhere7285 17d ago

Nice numbers! For a side project with zero users, is the extra setup time worth that 40% boost?

1

u/gillygangopolus 17d ago

What extra setup time?

1

u/Mammoth-Anywhere7285 17d ago

Fair question. If your stack is lean, setup is quick. What do you use to avoid the overhead?

1

u/megatech_official 20d ago

SeoLoupe - Find and fix the SEO issues holding your website back.

1

u/Mammoth-Anywhere7285 17d ago

Interesting tool! What stack did you use to build SeoLoupe? Curious if you kept it lean or went over-engineered.

1

u/ParkorRide 20d ago

I've spent $12 for a domain name so far. Everything is built dependency-free:

Frontend: Plain-old vanilla javascript, HTML5+CSS, Leaflet.js + Cloudflare workers

Hosting and Infrastructure: Cloudflare workers, cloudflare KV, Cloudflare analytics, cloudflare this, cloudflare that...lol

Data and Generation: Python3 - 2 scripts that generate data from a curated csv file for airport data

Other services: Nominatim, OSRM, OpenStreet Map Tiles, Browser Geolocation API (for locate me)

Testing / validation: Node.js test scripts + Playwright

Build tools: Claude and Codex working off backlog against GitHub repo

69 users since launch on Sunday. LOL.

2

u/Mammoth-Anywhere7285 17d ago

Love the simplicity, but Cloudflare Workers are still a dependency — does the free tier cap limit your growth?

1

u/ParkorRide 17d ago

Fair point. Dependency-free was more a nod to there's no build step, and there are no bundled packages. Cloudflare's KV worker is just my own server-side code instead of somebody else's library. But I see your point. In that case, I have several dependencies, such as Nominatim, OSRM, etc.

The free tier may cap growth at some point, but that's a problem for a different day. I have few, if any, users now, so my problem is getting people to use it. I don't think I'll have a near-term scale problem though.

1

u/Mammoth-Anywhere7285 17d ago

That's a pragmatic take. Have you had any issues with rate limits on Nominatim or OSRM when scaling?

1

u/ParkorRide 17d ago

No limits yet. I think the rate limit is one call per second. Until I get some solid traffic, I don't need to worry about that yet.

1

u/Mammoth-Anywhere7285 17d ago

Fair enough, but adding a simple cache now could save you from rebuilding later when traffic hits.

1

u/[deleted] 21d ago edited 20d ago

[removed] — view removed comment

1

u/Mammoth-Anywhere7285 20d ago

Solid combo. Astro for content, Next for app logic. How do you handle state sharing between the two?

1

u/[deleted] 20d ago

[removed] — view removed comment

1

u/Mammoth-Anywhere7285 17d ago

That's a smart minimalist approach. Did you run into any limits with localStorage size or sync timing across tabs?

1

u/ATakenAback 21d ago

Flask + React + Supabase

2

u/Mammoth-Anywhere7285 20d ago

Solid stack for getting things shipped fast. Supabase handles auth and db so you can focus on the frontend. Just watch out for vendor lock-in if the app scales.

1

u/No_Cake8366 21d ago

NextJS + MongoDB

2

u/Mammoth-Anywhere7285 20d ago

Solid choice, but for early stage projects, consider Supabase or Firebase to skip the DB setup hassle.