Own product · Taxi dispatch SaaS
TaxiDex
My own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
Service
One engineer responsible for the whole product: the schema, the API, the web portal, the mobile apps and the deployment. You get a single person who can follow a bug from a tap on a phone to a row in a table.
TypeScript back ends on Node.js with AdonisJS, NestJS or Express. React and Next.js front ends. Flutter apps. MariaDB, PostgreSQL and Redis underneath, and Socket.IO for anything that has to stay live. If your team already runs Laravel or Spring Boot, I work in those too.
Features usually stall at the hand-offs: the API team waits on the app team, and the app team waits on a spec. When one person holds the whole picture, a change to a fare rule can land in the database, the API and two apps in the same pull request.
TaxiDex is the clearest example. It has more than 1,000 API routes, over 200 portal pages and two Flutter apps on Google Play, and I own all of it.
Yes. I read the code first, get it building and deploying reliably, and then add features. Inherited and half-finished codebases are a normal part of my work.
The one that suits your problem and the people who will maintain it. For a new product I usually reach for TypeScript on the server, React on the web and Flutter on mobile.
Yes, on the parts that would hurt most if they broke, such as money, permissions and dispatch logic. TaxiDex has more than 3,000 automated back-end tests.
Own product · Taxi dispatch SaaS
My own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
Automotive super-app
Garage, courier, rides, parts, chauffeur, tow and fleet tools in one Flutter app on a large Express API.
Productivity
A task and project-management suite: React on the web, Flutter on mobile, TypeScript underneath.
A discovery call within 48 hours, and a kickoff typically inside two weeks.