Dollaride

About the project

Dollaride was a public transportation platform with Rider and Driver mobile apps, a backend API, and a web product. I worked across all of those pieces while leading a team of around three to five developers. I was also the main mobile developer, so my role covered both keeping the wider project together and staying very close to the React Native apps.

This is one of the clearest examples of the kind of work I enjoy: not staying inside one codebase, but understanding how the whole product fits together and helping a team move through it.

API and architecture

I was in charge of the development of the API using NestJS, Node.js, and WebSockets. I designed and architected features for the team, broke the work into pieces, and helped other developers understand how their part connected to the rest of the system.

I also worked on an integration of the OCPP standard. That work later became useful as the company moved toward electric van transportation. It is a good reminder that infrastructure work can outlive the first feature it was made for.

Mobile apps

The Rider and Driver apps were built with React Native. They needed to represent a real transportation system where location, timing, and changes from the backend had to reach the person using the app without making the experience confusing.

I was the main mobile developer for the Rider and Driver apps. I contributed directly to the features, reviewed the work around them, and made the technical decisions needed to keep both applications moving as one product.

I also taught junior and mid-level developers about React Native and helped them navigate the codebase. That meant explaining why something worked, helping debug the platform-specific parts, and making sure knowledge did not remain with only one person even when I was the person keeping most of the mobile work together.

Web product and team leadership

The web product used Next.js and WebSockets. I supervised and reviewed its development while contributing alongside a junior developer. My role was not to disappear into planning documents. I still wanted to work in the code with the team and be available when the implementation exposed a problem in the plan.

Leading this project meant architecture, reviews, client communication, teaching, debugging, and helping a small team keep moving. My work on Dollaride was broad and strong. I was involved wherever the project needed someone to connect the pieces, while still being responsible for a large part of the implementation itself.

It also meant accepting that decisions need to be revisited when the product teaches you something new. Keeping everything together was not one task. It was the combination of many small technical and human decisions across mobile, backend, and web.

Archive note

The mobile links are third-party archives because the original listings are no longer available. The images may represent versions released at a different point in the product’s history.