Mobile app development
Android and iOS from one codebase, for ordering, bookings, field staff and delivery drivers. Built in Flutter and published under your own developer account.
Discuss your appMobile apps, web applications and online stores for small and medium businesses. We write the app, build the API behind it and run the server it sits on, so nothing falls between suppliers.
Most projects get split between a designer, a developer and whoever ends up with the hosting login. We take all three, so there is one number to call when something stops working.
Android and iOS from one codebase, for ordering, bookings, field staff and delivery drivers. Built in Flutter and published under your own developer account.
Discuss your appCustomer portals, booking systems, internal tools and dashboards on Laravel and Next.js, designed around how your staff actually work.
Discuss your projectShopify and WooCommerce builds, speed and checkout fixes, and migrations onto your own platform when plugin licences cost more than they return.
Discuss your storeSetting cloud infrastructure up properly, migrating onto it, and working out why the bill went up. You hold the account and pay Amazon directly.
Discuss your cloudProvisioning, deployments, backups, SSL and monitoring on AWS or bare metal. The layer most development companies hand back and refuse to own.
Discuss supportMoving a business off accounting software, an old store platform or a stack of spreadsheets, running old and new side by side until the new one has proved itself.
Discuss a migration
Rides were quoted over the phone and written into a diary, so fares varied and no-shows were only found out on the day. The booking platform gives a fixed price before the customer commits, and the office sees every job in one place.

Customers ordered by phone and WhatsApp and staff typed every order in again. We replaced the WooCommerce site and the Sage 50 back office with one Laravel and PostgreSQL platform, a Next.js storefront and apps for the counter and the warehouse.

Counter staff worked from a till that did not know the menu, so prices were keyed by hand and the kitchen got a handwritten docket. The POS now runs dine-in, pickup and delivery off the same catalogue, and sends each order straight to the kitchen and the printer.

Drivers carried printed run sheets and wrote delivery notes out by hand, so proof of delivery came back to the office days later, if at all. Now the run sheet is on the phone and every drop is closed off at the door.
Your repository, your servers, your store and cloud accounts, in your company name. Nothing is held hostage if you work with someone else later.
One document before anything starts: what is included, what is not, what it costs and when it lands. Changes are quoted before they are built.
The same people write the app, the API and the server configuration. When the site goes down at 6am there is no argument about whose job it is.
We explain what we are building in words you can repeat to your staff. If what you need is smaller than you think, we tell you on the first call.
We are in India and answer emails the same working day, not the next week. You get one person who knows the project, not a ticket queue.
Documented, deployed and explained, so another developer could pick it up. We want you to stay because the work is good.
Half an hour on what the business does and where it goes wrong. No charge and no obligation to go further.
One document covering what is included, what is not, the cost and the delivery date. You approve it before work starts.
You get something you can use early, and regularly after that. Changes are cheap while we are still in the code.
Deployed to a server we set up, accounts and documentation handed over, and a monthly support agreement if you want one.
It depends on scope, so we quote a fixed price after the first call rather than publishing a rate. Smaller web applications and store migrations are the cheapest starting point. A multi-app system with its own API and server is the largest. You have the number in writing before anything is built.
A migration or a focused web application is usually a few weeks. A full system with customer, staff and driver apps takes a few months, and you will be using working parts of it long before the end.
Yes. The repository, the servers and the store and cloud accounts are all in your company name and handed over at launch, along with documentation.
Often, yes. We review what exists first and tell you honestly whether it is better to continue it or replace it. We will say so if continuing is the cheaper answer.
Monthly support covers hosting, backups, monitoring, security updates and a set amount of change work. It is a written agreement listing exactly what is covered, not an open-ended retainer.
We are based in India and work with businesses anywhere. Everything is handled over email, calls and video, and we reply the same working day.
A half-hour call, free, with no sales pitch. You will leave it knowing what the work involves and roughly what it costs.
Tell us what the business does, where it goes wrong, and what you are paying for software that is not earning its keep.
support@onezera.com
Monday to Friday, 9am to 7pm IST. Replies the same working day.
Based in India, working with businesses anywhere in the world.