Patrice M.

I rebuild no-code and AI-built apps into custom code that scales: Flutter for iOS and Android, Next.js for web, with Supabase, PostgreSQL or Firebase behind them. 𝗢𝘂𝘁𝗴𝗿𝗼𝘄𝗻 𝗕𝘂𝗯𝗯𝗹𝗲, 𝗙𝗹𝘂𝘁𝘁𝗲𝗿𝗙𝗹𝗼𝘄, 𝗟𝗼𝘃𝗮𝗯𝗹𝗲 𝗼𝗿 𝗮 𝗰𝗼𝗱𝗲𝗯𝗮𝘀𝗲 𝗻𝗼𝗯𝗼𝗱𝘆 𝘄𝗮𝗻𝘁𝘀 𝘁𝗼 𝘁𝗼𝘂𝗰𝗵? 𝗧𝗵𝗮𝘁'𝘀 𝘁𝗵𝗲 𝘄𝗼𝗿𝗸 𝗜 𝗱𝗼. Most rebuilds stall on the same things: a database that was never modelled, roles enforced only in the UI, no tenant isolation, and nobody who understands the whole system. I fix those first, then ship. 𝗪𝗵𝗮𝘁 𝗜 𝗱𝗼 1. 𝗥𝗲𝗯𝘂𝗶𝗹𝗱𝘀 & 𝘁𝗮𝗸𝗲𝗼𝘃𝗲𝗿𝘀: move no-code or AI-generated apps to maintainable code, with data migration 2. 𝗠𝘂𝗹𝘁𝗶-𝘁𝗲𝗻𝗮𝗻𝘁 𝗦𝗮𝗮𝗦: org-level isolation, role-based access enforced at the database, audit trails 3. 𝗠𝗼𝗯𝗶𝗹𝗲 𝗮𝗽𝗽𝘀: Flutter for iOS and Android, shipped to the App Store and Google Play 4. 𝗪𝗲𝗯 𝗽𝗹𝗮𝘁𝗳𝗼𝗿𝗺𝘀: Next.js, React, TypeScript and Node, with admin dashboards 5. 𝗣𝗮𝘆𝗺𝗲𝗻𝘁𝘀 & 𝗔𝗜: Stripe, RevenueCat, M-Pesa, and Claude API features where they earn their place 𝗥𝗲𝗰𝗲𝗻𝘁 𝗽𝗿𝗼𝗼𝗳 - 𝗡𝗼-𝗰𝗼𝗱𝗲 → 𝗰𝗼𝗱𝗲: inherited a FlutterFlow nonprofit platform, rebuilt it in Flutter, redesigned the UI and normalized the database. It now serves multiple organisations on one multi-tenant system with automated reporting, and I'm rebuilding its web app in React/TypeScript. - 𝗦𝗰𝗮𝗹𝗲: built the iOS and Android apps for a US travel platform that peaked at ~29K monthly active users, plus backend work on its PostgreSQL stack. - 𝗦𝗵𝗶𝗽𝗽𝗲𝗱 𝗔𝗜: a Claude-powered property assistant that matches tenants with listings. 𝗛𝗼𝘄 𝗜 𝘄𝗼𝗿𝗸 Claude Code is part of my daily workflow, under strict review and test gates. I read every diff, and nothing merges without passing CI. You own every repo and account from day one, and the codebase is handed over documented so your team can keep building safely. ✅ Top Rated Plus · 100% Job Success · $200K+ earned · 70+ contracts 𝗣𝗹𝗮𝗻𝗻𝗶𝗻𝗴 𝗮 𝗿𝗲𝗯𝘂𝗶𝗹𝗱? Send me your current app or specs here on Upwork and I'll reply with a short risk review: what to keep, what to rebuild, and a rough estimate.