Case studies

Work

Each project carries a status label and evidence chips. A chip appears only where a record with a real artifact stands behind it, so the shortest card is the honest one.

FieldProof

PORTFOLIO PROJECT

FieldProof: Field work that survives bad connectivity.

Inspectors record findings on sites with no signal. The work syncs once a connection returns, freezes when it is handed in, and the office reviews it — photographs and all — from a hosted console.

Who owns a record, what the office may read, and the freeze on submitted work are all enforced by row-level policy in Postgres — not by the app, so they hold even when the app is bypassed.

Offline drafts
279 mobile tests
183 database assertions
Live review console

Role: Solo engineer — mobile, database, admin, CI

FlutterSupabase / PostgresNext.jsGitHub Actions

CI
TESTS
SOURCE
LIVE DEMO
RELEASE
DEVICE QA
DATABASE
SECURITY
DESIGN

Case study →

One Frame

NOT PUBLISHED

One Frame: A journal that never leaves the phone.

One photograph and one sentence a day, for someone who wants the habit without handing their life to a server. There is no account and no upload — and uninstalling loses it, which the app says on the first screen.

Private by manifest, not by promise — the release build declares no INTERNET permission, so the app has no route off the device at all.

220 tests
Release refuses an unsigned build
Run on Android hardware
Repository private

Role: Solo engineer — mobile, product, release

FlutterSQLiteGitHub Actions

CI
TESTS
RELEASE
DEVICE QA
REPORT

Case study →

First Week

PORTFOLIO PROJECT

First Week: A checklist that will not invent a deadline.

Vietnamese first-years piece their enrolment week together from school notices, group chats and the year above. First Week puts one cohort's steps in a single list and shows what stands behind each one — including the steps nobody has answered yet.

A step marked official cannot be constructed without the school's own page attached — the model throws, so a guess can never reach the screen wearing the school's authority.

Public repository
79 of 80 tests at HEAD
14 screens on a real device
No CI

Role: Solo engineer — contract, data, application

FlutterOpenAPIFrozen fixtures

TESTS
SOURCE
DEVICE QA
DESIGN
REPORT

Case study →

Skillr

UNVERIFIED

Listed for inclusion in this portfolio. No repository, deployment, build or written artifact could be reached, so no scope, stack or contribution is described here.

Role: Not established

No evidence availableCase study →