TrimugoSmart Solutions

Lumo Rentals

A travel platform for booking bikes, cars, and tempo vehicles — with web and mobile apps live on Android and iOS.

Category

Full-Stack · Mobile

Year

2025

Status

Delivered

Built by

Trimugo — Malisetti Obulamurthy

Stack

• React.js
• React Native
• Postgres
• Payments

See it

Open the live site  ·  Google Play  ·  App Store

The problem

Renting vehicles is a coordination problem before it is a software problem: what is available, for which dates, at what price, paid for by whom. Handling that across separate channels means availability is only ever correct in one person’s head.

What was built

A booking platform with one API behind three clients. Vehicle catalogue, availability, reservations, customer accounts and payment all live in one system, so a booking made on a phone and a booking made on the web are the same record.

Engineering

• A single backend service and PostgreSQL data model serving three clients
• React Native application shipped through both App Store and Google Play review
• Payment provider integration
• Availability modelling across vehicle classes and date ranges

What the system now handles by itself

• Availability and reservation state maintained by the system rather than reconciled by hand
• Payment capture and booking confirmation handled in-flow instead of chased afterwards
• One booking record shared across web and both mobile apps

On AI in this build

No AI in this build. The value here was in removing manual coordination, and adding a model would have added risk without adding capability — the same judgement we apply to every project.

Where it stands

• Live in production on the web, the App Store and Google Play
• Bookings run through one system rather than across separate channels
• Customers self-serve on the surface they already use

The flow, end to end

• Customer
• Availability
• Reservation
• Payment
• Confirmation
• Operations

How it was built

Designed, built and delivered by one engineer — discovery, architecture, implementation and release were the same person, with no handoff between roles and no subcontracting. The link above goes to the running product rather than to a mockup or a case-study screenshot.

Work with the same engineer

Freelance engagement · Contract engagement · AI solutions