Full-stack + mobile engineer / Kampala, UG

I build for the network you assume actually have.

Offline-first apps, distributed systems and resilient infrastructure for environments where connectivity, power and devices cannot be treated as guaranteed.

Explore selected work Read flagship case study

Focus: Offline-first systems
backend + mobile
Experience: 3 years production
engineering + leadership
Availability: Open to remote roles

FIELD CONSOLE / NETWORK SIMULATION

CONNECTED

Interactive system demo

The portfolio behaves like the systems I build.

Switch the network offline. Portfolio events begin queuing locally instead of failing. Bring the connection back and the queue reconciles automatically. It is a small browser simulation of the local-first pattern behind the flagship project below.

// Client-side simulation only. No fake backend calls and no data leaves this page.
// The interaction exists to demonstrate the engineering model, not to imitate production telemetry.

Latency

42ms

Signal

▂▄▆█

Queue depth

0

Last sync

just now

Local write queue 0 pending

SYNCED portfolio.session.start

01 / SELECTED WORK

Evidence before ambition.

SHIPPED + ACTIVE BUILDS

Building Offline-first Sync engine Cached locally PROJECT / 01

Mobile Money Ledger for Offline Vendors

A local-first Flutter app and Go synchronization service for small vendors who need to record sales, update stock and reconcile transactions even when connectivity disappears for an entire market day.

Constraint: Intermittent or zero connectivity
Architecture: Flutter + Drift + Go + PostgreSQL
Decision: Local writes first, opportunistic sync

Read the engineering case study

Flutter client Drift / SQLite
local writes

Sync queue retry + backoff
on device

Go sync API conflict check
reconciliation

PostgreSQL server source
of truth

WRITE LOCALLY → SYNC WHEN POSSIBLE → RECONCILE

Production work 02

Inventory Platform

Worked from the early stages of a multi-warehouse inventory system across database design, Go APIs, React web interfaces and an offline-first Flutter mobile client.

Operational 03

HR Management System

An independent full-stack HR platform with role-based access, leave workflows, JWT authentication, analytics dashboards and containerised local infrastructure.

02 / ENGINEERING LAB

Experiments have a different job.

LEARNING IN PUBLIC

L/01

Raft-Lite

A simplified distributed key-value store for working through leader election, replicated writes and the Raft paper in code.

GO / GRPC / CONSENSUS

L/02

Collaborative Editor

A CRDT-based editing experiment focused on concurrent changes, WebSocket presence and reconnect behaviour.

REACT / GO / YJS / WEBSOCKETS

L/03

USSD / SMS Service

A constrained interface experiment for users without smartphones or reliable data plans, with session-based state and telecom APIs.

GO / USSD / AFRICA'S TALKING

L/04

Flutter Package

A planned extraction of a reusable offline-first building block from the ledger project, with tests and a production-grade README.

DART / FLUTTER / PACKAGE DESIGN

Current profile Full-stack + mobile engineer

Leadership Former CTO & Head of Software Engineering

International work Client-facing QA + cross-border delivery

Base Kampala, Uganda
Open to remote roles

03 / SIGNAL LOG

Notes from the build.

View all entries

MAR / 2026

Why offline-first is harder than it sounds: conflict resolution for a mobile money ledger

OFFLINE-FIRST
6 MIN READ

FEB / 2026

Six months as a first-time CTO: what actually changed day to day

LEADERSHIP
8 MIN READ

JAN / 2026

What I'm learning building Raft-lite in Go

DISTRIBUTED SYSTEMS
7 MIN READ

Available for the next serious build

Need an engineer who thinks about the failure case before the happy path?

I am currently open to remote full-stack, backend, mobile and technical leadership opportunities. If the problem involves unreliable networks, constrained devices or systems that need to keep working when assumptions break, I would especially like to hear about it.

Start a conversation More about me