Case studies
Otomiks
A service marketplace connecting vehicle owners with garages and mechanics.
01
Problem
When a vehicle needs servicing or repair, the owner has to ask around, call garages one by one and explain the job over the phone. On the garage side, demand arrives scattered: a flow split between calls, messages and a notebook, leaving no record of either the request or the answer given. Both sides run the same job independently of each other, and neither keeps a record.
02
Solution
The whole flow, from the moment a request is created to the garage's response, was built on a single Laravel 12 core as 28 backend modules. On top of it sit a Next.js 15 web interface and iOS and Android applications built with React Native (Expo). All three clients use the same API and the same business rules: a feature is written once and works on three surfaces. MySQL sits underneath as the data layer.
03
Result
The web version and the iOS and Android applications are live. Because there is one codebase, behaviour does not diverge between platforms and a new module lands on all three surfaces at once. The server, web and mobile sides were all built and are all operated by Erbe Bilişim.
## Engineering scope
- **28** — backend modules on a single Laravel 12 core
- **3** — live platforms: web, iOS and Android
- **1** — shared codebase and a single API contract
The server side runs on Laravel 12 and MySQL; the web interface was built with Next.js 15 and the mobile applications with React Native (Expo). Mobile and web are not separate products but two faces of the same core: the business rules live in one place and the clients simply present them.