All work

Concept project: a sample build that shows how we approach this kind of product. The client, features and figures are illustrative.

Mobile · Flutter + Python (FastAPI) · Fintech · Consumer

fintrack

A Flutter budgeting app that makes logging spending take seconds and shows people where their money goes.

Client
Concept: personal finance startup
Year
2026
Services
Product design, Flutter app, Python backend, App store release
Live site
Concept build
FinTrack interface

Overview

The brief

Most budgeting apps lose their users in the first two weeks: entering a transaction takes too many taps, and the dashboards are dense charts that nobody reads. A personal finance startup wanted an app built around three simple jobs, track, understand and plan, that works on a train with no signal and keeps financial data secure.

Problems & fixes

What was in the way

Pick a problem to see what was wrong, what we built and what changed.

The problem

Competitor apps needed six or more taps and a keyboard to record a coffee, so people stopped logging after a few days.

What we built

A one-screen entry flow with a large amount pad, recent merchants and suggested categories, plus recurring transactions that log themselves.

What changed

A typical expense is logged in about five seconds.

1 / 4

Impact

What it changed

5 sTo log an expense
2Platforms, one codebase
100%Offline entries synced
38%Better 30-day retention
  • Users keep logging past the first month because it takes seconds.
  • One Flutter codebase halves the cost of building and maintaining two apps.
  • Budget alerts arrive before overspending, not after.

How it works

Under the hood

Click any part of the system, or play the flow from start to finish.

Step 1 · Flutter · Riverpod · GoRouter

App

One codebase for iOS and Android, with reusable widgets, charts and offline drafts.

01 —

Offline first

Every action works without a connection and syncs later.

02 —

One number

"Left to spend" answers the question users actually have.

03 —

Tested

Dart unit, widget and integration tests, plus API tests, run on every build.

Timeline

  1. Weeks 1–2Journeys, wireframes and the design system
  2. Weeks 3–5Flutter screens, offline drafts and charts
  3. Weeks 5–6FastAPI backend, auth and notifications
  4. Week 7Testing, TestFlight and Play internal release

Tech stack

FlutterDartRiverpodGoRouterFastAPIPostgreSQLFirebase AuthFirebase Cloud MessagingDockerAWS

got an idea?let's lift it.

Tell us what you're building. A senior engineer, not a salesperson, replies within one business day.

Start a project
Start a project