Skip to content

Galen Myburgh

I build production mobile & web systems that handle money, scale and mess.

Five years shipping Flutter and React — a buy-now-pay-later app used by hundreds of thousands of people, a cashless wallet that settles on an NFC card with no signal, and the AI products I work on now. Mostly the kind of system where being approximately right is the same as being wrong.

  • Flutter & React
  • Payments & NFC
  • AI products
Downloads on apps I've shipped to
400k+Downloads on apps I've shipped to
Years shipping Flutter in production
5Years shipping Flutter in production
Products delivered for clients
10Products delivered for clients
MobileWebData & backendHardware & IoTCloud & toolingAI & automation

Every node is something I've shipped with. Pick one to filter the work.

Filter by technology

Full write-ups: the problem, the constraints, what was hard, what changed.

All work →
Payflex app screens showing the spend limit view and the store directory

Payflex · 2024

Stabilising a buy-now-pay-later app used by 400,000+ people

Migrated a legacy consumer payments app to Clean Architecture and cut its crash rate by more than 40% without pausing feature delivery.

40%+ reduction in crash rate (firebase crashlytics)

  • Flutter
  • Dart
  • Clean Architecture
  • Firebase
  • +5
Tripleblue web platform and mobile app screens

Tripleblue · 2024 – 2025

Taking a product off low-code without losing a feature

Rebuilt a FlutterFlow web and mobile product as a custom Next.js and Flutter stack on Supabase, at full feature parity, while the original stayed live.

100% feature parity at cutover

  • Flutter
  • React
  • Next.js
  • TypeScript
  • +6
Camera analytics dashboard showing detected events and camera health

Internal / SME security · 2024

Turning dumb security cameras into something that reports

A Python and OpenCV analytics layer that adds motion detection, object recognition and health monitoring to existing camera hardware.

Edge runs on-device, no continuous upload

  • Python
  • OpenCV
  • Computer Vision
  • Automation
  • +2

How I work

Most of what goes wrong on a project goes wrong before anyone writes code, so this is the part I take seriously.

  1. 01

    Understand

    Whose problem is this, how bad is it, and what happens if we do nothing? A brief that can't answer those isn't ready to build against.

  2. 02

    Build

    Ship something real early, against real data. Boring code a stranger can change in six months beats clever code only I can.

  3. 03

    Watch

    Crash reporting and analytics from day one. At Payflex, Crashlytics decided what got refactored — without that signal you are guessing.

Where I've worked

Full history →