Shipped, and still running today.
Three mobile products in production, each solving a different distribution problem.
- eLaundry →
Native iOS and Android apps for both customers and operators, with the routing, dispatch and billing dashboard behind them.
- Caterday →
Swift and Java mobile companions to a marketplace web app, sharing one Node.js backend and GPS lookup for nearby suppliers.
- MealDaay →
One app serving customers and kitchen owners through role-specific experiences, with GPS routing through to delivery.
What we build it with.
Chosen per project, and for what your team can maintain afterwards.
Questions we get asked.
Should we build native or cross-platform?
It depends how much of the product is genuinely platform-specific. Heavy camera, Bluetooth, background location or platform-native UI work usually pays for native. A form-and-list product that has to reach both stores quickly usually does not. We make the call with your roadmap in front of us and write down the trade-off, because reversing it later is expensive. Our post on native versus cross-platform apps goes through the reasoning in more depth.
Do you publish the app to the App Store and Google Play?
Yes — submission, listing copy, screenshots, privacy declarations and responses to reviewers are part of delivery. We work inside your developer accounts rather than ours, which means the app, its signing identity and its reviews stay yours if you ever change vendor.
Who owns the code?
You do. Source, repositories, build pipelines and infrastructure accounts are yours and are handed over at the end of the engagement. We do not keep client products parked in our own accounts.
Can you take over an app somebody else built?
Often, and we will say plainly when the answer is no. It starts with an assessment of the codebase, the build pipeline and the store accounts, after which you get a written view of what is worth keeping and what is cheaper to replace.
How much does a mobile app cost?
Too much rides on scope for a number here to be honest. Roles, integrations, offline behaviour and how much design already exists move the figure far more than the choice of platform does. Our consultation page sets out the six factors that drive it, and a call turns them into a range for your requirements.
What happens after launch?
OS releases, dependency updates, crash triage and store policy changes carry on regardless. Either we keep a maintenance engagement running, or you take over an app documented well enough for your own team to maintain. Budgeting nothing is the one option that reliably fails.
Other services.
- Web Application Development →
Custom platforms, portals and SaaS — including replacing a legacy system while the business running on it stays up.
- Agentic Software Development →
Senior engineers directing autonomous agents that plan, write and test in parallel — with a named human accountable for every release.
- Salesforce Implementation →
Sales Cloud, Service Cloud and marketing automation configured around how your business really sells — with adoption as the deliverable.