YaboiCdog-13

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.