We take a product from the first sketch to a released, maintained application — and we are equally at home extending a system that already exists.
Native development in Swift and SwiftUI, targeting iOS 16.4 and above. Home screen widgets with WidgetKit, local notifications, camera and barcode capture, Keychain-backed sessions, Dynamic Island support, light and dark themes, and full App Store submission and review handling.
Android builds of the same products, distributed through the Play Store or as a direct APK where a client needs to sideload inside their own organisation. Shared backend, shared data model, platform-appropriate interface.
One TypeScript codebase for iOS and Android when the product calls for it, built with React Native and Expo — faster delivery and a single team, with native modules where the platform matters: camera, barcode scanning, notifications, secure storage. We choose React Native or fully native per project, based on what the app has to do rather than habit.
The backends behind the mobile apps, written in PHP, .NET or Python on MySQL or MSSQL — whichever fits the stack a client already runs. REST APIs, operator dashboards and admin panels in React, B2B portals, and the browser views that let an invited guest take part without installing anything.
Connecting applications to the systems that already run an operation: SCADA field data from pumping stations, sorter conveyor lines, warehouse management and ERP. Reading real status bits, real thresholds and real alarms, and presenting them so an operator can act on them.
Architectures where the device is the source of truth and the server is a synchronisation point. Entries survive a lost connection, reconcile on reconnect, and never block the person using the app.
Image processing that runs on the phone: locating objects in a photograph, reading the values printed on them, and handing the result back for confirmation. Nothing is uploaded, so it works offline and raises no privacy question.
Deciding what an application should not do is most of the work. We design the flows, the screens and the copy in both Turkish and English, and validate them on a device before a line of production code is written.
Operating systems change every year, and an app that is not maintained quietly stops working. We stay with the products we release — through OS releases, API changes and the process changes on the customer’s side.
Services
You describe the process or the product. We come back with what we think the first release should contain — and, more usefully, what it should leave out.
A written scope with the screens, the integrations and the deliverables, and an estimate against it.
Working builds on your device from early on, so decisions are made against something real rather than a document.
Store submission, review handling, staged rollout, and the supporting site or landing page if the product needs one.
Ongoing updates, OS compatibility, and development that follows how the product is actually used.
Tell us about the process you want to move onto a phone, the platform you want to launch, or the system that needs to talk to something else.
