[WarpLaunchApp] Improve transparency on usage limits

I'm primarily a mobile developer — I've shipped a bunch of iOS and Android apps over the years. And every single time, there's this moment near the end where I need to create the App Store listing assets: screenshots, icons, preview images. It's always weirdly confusing. Do I open Figma? Photoshop? Pay someone on Fiverr? Use one of those $30/month screenshot tools? I always end up wasting hours on something that should be straightforward. So I decided to build a tool that does it for me. You paste a link to your app or website, it pulls the info and generates a marketing-ready brief, then uses that to create store-ready screenshot layouts with headlines, AI-generated backgrounds, and icon concepts you can iterate on. But honestly, the product was only half the motivation. I also wanted to test whether I could build, deploy, and monetize a real web app using **Supabase + Cloudflare Workers** end-to-end. I'd used both in smaller projects but never for something with auth, payments, storage, and AI generation all wired together. **The stack:** - **Next.js 16** (App Router, React 19) — server components by default, server actions for mutations - **Supabase** — Postgres database, Google OAuth, Row Level Security, and Storage for all generated images - **Cloudflare Workers** — deployment via OpenNext adapter - **AI** — paste a link to your app and it generates a marketing brief, then uses that to create screenshot headlines, background art, and icon concepts - **Stripe** — auto-recharge credit system for monetization - **Tailwind CSS 4 + shadcn/ui** — styling **What went well:** - **Supabase Auth is the standout** — Google OAuth setup was the most seamless auth integration I've ever experienced. Seriously, good job Supabase - **Supabase RLS** is genuinely great once you get the cascading pattern down. Every table checks ownership through the parent chain — no auth middleware spaghetti - **Cloudflare Workers** deployment is fast. The OpenNext adapter works, though it has quirks - **Supabase Storage** solved a real problem — I initially stored generated images as base64 in Postgres and kept crashing my Nano instance (512MB RAM). Moving to Storage fixed it immediately - **Server actions + optimistic updates** make the workspace feel snappy **What was rough:** - I planned to run on **free tiers** for both Supabase and Cloudflare. Before a single user even signed up, I had to upgrade to paid plans on both — Worker CPU time limits, Supabase usage quotas, etc. "Free tier" is great for prototyping but don't count on it for anything real - **Supabase is not transparent about critical issues.** My Nano instance kept running out of memory and all I got was an "Unhealthy" status with no details. Took a lot of digging to figure out it was OOM from storing base64 in Postgres - **Supabase's auto-generated TypeScript types** don't play well with custom RPC functions. I ended up maintaining types manually and wrote a validation script to keep them in sync with the SQL - **Tailwind v4's** CSS `@layer` changes broke some inline style overrides in unexpected ways I call it [WarpLaunchApp](https://warplaunch.app) and started using it for my own apps and found it actually saved me real time, so I cleaned it up and opened it to everyone. There are free credits on signup so you can try it without paying anything. Happy to answer questions about the stack, the Supabase + Cloudflare experience, or anything else.