Who
I wanted a thin auth starter that did email + social without dragging Clerk or a Convex migration into launch week.
For anyone spinning a Next App Router app that needs Firebase Auth + a users doc and can live with honest leftovers.
What
I built simple - public https://github.com/michaelmonetized/simple. HEAD da7e0b0. 10 commits. 0 stars. Default main. Version 0.1.0 (private: true). Claimed live URL https://simple-ivory.vercel.app is DEPLOYMENT_NOT_FOUND.
Shipped (~1k LOC app/firebase/components): Next 16 + React 19 + Firebase 12 Auth/Firestore. /, /login, /register. Email/password SignUpForm + LoginForm. Google / Facebook / Twitter Connect buttons (signInWithPopup / linkWithPopup). AuthProvider -> Firestore users. Generic CRUD in firebase/crud.js. Clamp spacing + Catppuccin color tokens. Security headers in next.config.mjs. Documented keep-Firebase decision.
Launch arc: four Sept 2024 init commits -> Dec 2025 / Feb 2026 CVE bumps -> console strip + HSTS/X-Frame headers -> architecture doc -> final console cleanup (#5).
Gaps: create-next-app README still; login/page.tsx exports RegisterPage; coerceeUserCredntial typo; console.warn left; hardcoded firebaseConfig; Hustle Launch branding; Tailwind pkg vs classic config; kitchen-sink env example; no middleware; Vercel deploy gone.
Where
Code: https://github.com/michaelmonetized/simple - public.
Run: install deps then next dev.
Live: simple-ivory host is down (404).
When
2024-09-05 - fec428f to 1c2d5f5 four init commits.
2025-12-29 - 7c5e849 cve vulnerabilities.
2026-02-21 to 2026-03-23 - 03addd3 CVE; e0b5dee+407450f headers; 9b33e46 keep-Firebase; da7e0b0 HEAD.
Why
Because launch week needed auth that already worked, with a written keep-Firebase decision.
Engagement Q: Redeploy simple-ivory and finish middleware, or keep as Firebase keep-decision reference until Convex revisit?