CAPABILITY / 07
Backends for Flutter apps
In production
Backends and contracts for Flutter apps: the mobile developer writes the UI; I own the API, data and release behind it.
Updated
01 / PROOF
The measured part
02 / WHAT I DO
In practice
- Design the API contract before the mobile UI is built.
- Lint the contract in CI and test every reply against it.
- Handle migrations and the release path for the backend.
- Work with the mobile developer without pretending I wrote their UI.
03 / WHERE I'VE DONE IT
The systems behind it
04 / STACK
What it runs on
- Flutter backends
KP builds the API contract and backend; the Flutter UI is built by the mobile developer
See the system - OpenAPI
OpenAPI 3.1 contract, 163 operations
See the system - Node.js
Self-service API service
See the system - PostgreSQL
Shared relational store
See the system
05 / LIMITS
What this does not claim
The Flutter UI on Team RVM and most of the BadaBhai worker app are colleagues’ work.
07 / QUESTIONS
Short answers
Does KP write Flutter?
No. He builds the backend and the API contract the Flutter app runs on; colleagues write the Flutter UI.
How is the mobile contract kept honest?
Team RVM has one OpenAPI 3.1 file with 137 paths and 163 operations, linted in CI, and 1,321 contract tests that check every reply against it.
Need this on a real system?
Hiring for a role, or scoping a short engagement? The Hire page has the role families and contact; Consulting has the scoped offers.