A stalled or broken Flutter build, diagnosed and fixed on a fixed fee.
- 01Scoped from a paid code review, not a guess
- 02Fixed fee agreed before any work starts
- 03Ships before the bigger conversation begins
Mobile apps, GPS and fleet platforms, field-service systems and AI agents for operators in the US and Europe. Small studio, senior engineers, and prices published on this site rather than quoted after a discovery call.
Working 8am – 12pm US Eastern · replies typically within ~2 hours
The work clusters around one thing: software for businesses whose people, vehicles or assets are out in the world rather than sitting at a desk.
Live tracking, route replay and telematics built on Traccar — the open platform independent tracking businesses run on. Two apps from this stack are live in the App Store.
Fleet & GPS software →Technician and admin apps that get job data out of the field accurately the first time: scheduling, materials, hours, photos and signatures captured before the tech leaves site.
Field service software →iOS and Android from a single Flutter or React Native codebase. More than twenty apps I have built are live in the App Store, most under clients’ own developer accounts.
See shipped apps →Agents that take real actions — resolving load issues, creating invoices by voice — with a permission model and an audit trail around them, not a chat box that paraphrases a help page.
How the agents work →Customers, roles, invoicing, scheduling, dashboards and reporting, written rather than configured. Two of these were delivered under white-label agreements, so they cannot be shown — ask on the call and I will talk through the architecture.
Talk through an ERP build →A stalled or abandoned build, diagnosed in a paid code review and then fixed on a fixed fee. Sometimes the review concludes it is not worth saving, and you are told that plainly.
Rescue from $1,500 →If your trucks exist so your technicians can reach the job, off-the-shelf software was designed around someone else's workflow. That mismatch is usually why part of your operation still runs on a spreadsheet.
Best fit is 5–50 field workers. Below that the owner is usually still the system; above it you likely need an enterprise platform. Either way I'll say so on the first call.
Where a build is live you get the link. Where it is built but not yet published, the card says so.
Live vehicle tracking, in the App Store
Flutter · Firebase · Traccar
Read the build →GPS tracking with dashcam video, in the App Store
Flutter · Traccar
Read the build →Marketplace app, App Store and web
Flutter · Firebase
Read the build →Broker portal with an AI agent that takes actions
Flutter · Node.js · PostgreSQL · AI agents
Read the build →Hamza Kaleem founded Animmza and writes the code on most builds. The figures below are his freelance record, and every one of them is public on a platform he does not control.
Open the profiles and check — Fiverr and Upwork. Attributed by platform, never blended into one number. More about Hamza →
Twenty minutes to understand the operation. You get a written scope with a fixed price — not a proposal deck, and not an hourly estimate that drifts.
Working software at the end of each phase, not at the end of the project. If something is wrong, you find out in week three rather than month four.
Source code, accounts and deployment handed over on delivery. No retainer required to keep it running, and no dependency on me afterwards.
Most developers dodge this until the third call. These hold unless the scope moves.
A stalled or broken Flutter build, diagnosed and fixed on a fixed fee.
A focused app for one workflow — techs in the field, or a single ops surface.
Admin, technician and customer surfaces with the back end behind them.
I work 8am – 12pm US Eastern and replies typically land within ~2 hours. Bring the problem, not a spec — the first call is scoping, and it is free.