Tech Stack Audit: Solo Founder | Next.js + [Flutter vs RN] + Supabase + Stripe | Solving "AI Context Drift"Hi all,
I'm a solo founder launching a location-based utility SaaS. Architecting for a lean start, but ensuring the codebase is "due-diligence ready" for a future exit or team expansion.
The Proposed Stack:
\- Web: Next.js (SEO Landing Page, blog + Admin/B2B Portal).
\- Mobile: Consumer-facing iOS/Android app (Alerts & Schedules).
\- Backend: Supabase (Postgres + PostGIS for geospatial lookups).
\- Payments: Stripe (via RevenueCat for cross-platform entitlement).
\- Infrastructure: Cloudflare (DNS/WAF) + OneSignal for Push Notifications.
\- The Engine: Python-based scrapers (Playwright/BeautifulSoup) standardizing data.
The Mobile Dilemma:
\- Torn between Flutter (Premium feel/Performance) vs. React Native/Expo (CodePush OTA updates and shared logic with Next.js). For a solo dev building a utility-first app, which provides the best ROI on development time vs. exit valuation?
The Dual-AI Workflow & "Memory" Issues:
\- I use Cursor (Claude 3.5 Sonnet) for coding and Gemini 1.5 Pro for architectural strategy. Even with a "split brain" approach, I'm hitting "Context Drift"—the AI loses the thread of previous architectural decisions or gives contradicting logic once the repo grows.
Questions for the Community:
Monorepo vs. Polyrepo: Does a Monorepo make it easier for the "AI Coder" to see the full context, or does it lead to "Context Poisoning" where it confuses Mobile vs. Web logic?
Project Memory: How are you using .cursorrules or PROJECT\_STATE.md to keep the AI "locked in" to your tech stack over a 6-month build?
The Scraper Pipeline: Best way to trigger Push Notifications from a Python scraper outcome? Should the scraper hit a Supabase Edge Function or talk directly to the DB?
The "Exit" Standard: If you were buying a solo SaaS, would you prefer a clean Next.js/Supabase/Flutter stack, or is the framework secondary to the data moat?
Appreciate any insights!
A solo founder is seeking advice on their tech stack for a location-based SaaS, focusing on Next.js, Supabase, and Stripe. They are debating between Flutter and React Native for mobile development and are experiencing 'AI Context Drift' with their dual-AI workflow. They seek community input on monorepo vs. polyrepo, project memory strategies, and best practices for triggering push notifications from a Python scraper.
This is a really thoughtful breakdown, honestly feels like you’re already thinking in the right direction, most people in similar situations end up leaning toward Next.js for web because Flutter Web still has rough edges like heavier loads and performance quirks, while Firebase is great for speed early on but something you might outgrow or rethink later , so it kind of comes down to whether you want faster iteration now or more control long term !!!
Solid stack overall, especially Supabase + PostGIS for your use case.
On the mobile side, for a solo founder I’d lean Flutter unless you specifically need tight web/mobile code sharing. RN/Expo can look faster early on, but Flutter tends to give you more consistency and fewer platform-specific issues over time.
On the “context drift” problem, this is very real once the codebase grows. What’s worked best for me is:
- keeping a single source of truth (like a PROJECT_STATE.md)
- documenting decisions as constraints, not just notes (e.g. “we always use X for Y”)
- breaking tasks into smaller, self-contained chunks so the AI doesn’t need full repo context every time
For the scraper → notifications flow, I’d avoid writing directly to the DB. Hitting an edge function or API layer is usually safer so you can control logic, validation, and triggering side effects like notifications in one place.
For exit value, I’d say the data + execution matters more than the exact framework —> a clean, understandable codebase is more important than whether it’s Flutter or RN.