InvoiceMe

Case studyInvoicing productProject 13

The problem

Freelancers and small businesses need fast, secure invoicing that works on mobile.

What I built

A Flutter app over a NestJS API with PostgreSQL, Stripe payment intents with signed webhooks, TOTP two-factor auth with backup codes, DB-backed refresh-token rotation, audit logging and GDPR export/delete. A protocol-2 sync client with server revisions and a conflict-review screen is built and tested, but the screens save directly to the server, so offline editing is not implemented.

The result

Development is complete; the production release is deferred by the owner. On the last code change, CI passes backend unit, real-PostgreSQL end-to-end, Flutter and Android-emulator suites, each reported separately below. Offline editing through the app’s screens is not implemented. Repository improvements verified independently; the owner-managed installation was outside this review, which does not establish which version that installation runs.

Evidence

Repository: github.com/seifosmaan53/invoiceme (public, 55 commits; main ec3bf04)
CI: GitHub Actions run 41108401365 on ed065aa (2026-10-30), the last change to application code, green with a postgres:15 service; later commits on main change documentation and phone-test scripts only
Backend tests: 658 unit tests (30 suites); 385 end-to-end API tests against a real PostgreSQL database passed, 1 skipped; the restore-verification file rerun with its Unix-socket test enabled, 13 passed. Each suite is reported on its own and not added together: the restore file is also part of the end-to-end run
App tests: 151 Flutter tests in the same run; on an Android emulator, 4 of 4 integration tests against a real backend passed (run 41108435367)
Physical devices: Owner-reported testing on an earlier build only; no physical-device check is recorded for the current build
Not finished: Offline editing through the app’s screens: they save directly to the server and sync runs only from Settings, so offline-first is not working yet
Release: Development complete; the production release is deferred by the owner, so no production signing key, production build or distribution exists yet
Review scope: Repository improvements verified independently; the owner-managed installation was outside this review, which does not establish which version that installation runs.
Comparison: Invoicing, built three ways: the same invoicing core on three stacks, with each build’s evidence

Stack

FlutterNestJSPostgreSQLStripe2FA

View on GitHub