I take products from idea to app store.

Short-term-rental cleaning companies coordinate turnovers through texts and spreadsheets, and the incumbent software takes a percentage of every clean — while being built for property owners, not the crews doing the work. Worse for software: cleaners work in basements and coverage dead zones, so the app can't assume a connection. Ever.

I built a Flutter app with true offline-first sync — PowerSync over Postgres — on a Supabase backend with row-level security multi-tenancy. Photo-proof checklists, automatic Airbnb calendar ingestion, crew scheduling. Every feature works with zero bars and reconciles when the signal comes back.

• Flutter
• Supabase
• PowerSync
• Postgres
• Cloudflare

Consumer apps built on metered third-party APIs have a nasty failure mode: every user costs money, growth costs more of it, and one loose query pattern turns a good week into a bill. GobbleGo runs on Google Places for restaurant data, so the unit economics had to be a design constraint rather than an end-of-month surprise.

I built the app and the company around it — Flutter client, Supabase backend, and per-SKU cost controls on every Places call so spend stays bounded and attributable per feature. Shipping it meant the unglamorous half too: Twilio toll-free verification so the app can legally send texts, transactional email through Resend, and the LLC and Apple Developer org to put it all under.

• Flutter
• Supabase
• Google Places API
• Twilio
• Resend

Adding save/load to a Unity game after the fact is miserable, so I built a node-based scripting system where serializing the entire game state — mid-execution, at any point — is built into the runtime rather than bolted on. Pause a running graph, save, quit, reload, resume exactly where it was.

Published on the Unity Asset Store with full source on GitHub. Used for everything from menu flow to NPC behavior to branching dialogue.

• Unity
• C#
• Graph runtime
• Serialization