Native iOS and Android.
Designed native, not wrapped.
Reference builds from the studio — demo apps designed end to end so the craft can be examined directly. Each one is designed natively for both platforms, the iOS idiom and Material 3 rather than one layout skinned twice, around a device capability the browser cannot reach, and specced against the Swift and Kotlin stack it would ship on. These are demo builds, not client engagements. Paid client work sits on the portfolio.
8 builds, front to back
Construction, freight, property, remote patient monitoring, field service, corporate cards, on-call paging and plant-floor safety. Each one is taken far enough to be judged: a fully worked home screen, a deep detail screen, and the same feature redesigned in Material 3 rather than skinned.
Why these are native, and not a web app
Each build in the set was picked because it lands on something a browser cannot do. That is the whole argument for going native, and these are the 6 places it shows up across the 8.
The signal is optional
A day sheet, a delivery, a work order or a safety walk has to complete in a basement dock or a steel bay and reconcile cleanly hours later. Every build in the set is designed around an encrypted on-device store behind a durable, append-only outbox that replays in causal order on the first uplink. Browser storage is evictable and its critical path is the wire.
Peripherals that bond and reconnect
Blood-pressure cuffs, glucometers and scales on the Bluetooth SIG GATT profiles; refrigerant manifold gauges and clamp meters; ring scanners and cab-mounted label printers. Web Bluetooth cannot bond, cannot run in the background, and is not available on iOS at all.
Location that works with the screen off
Geofenced arrival and departure stamped from an Android foreground service or an iOS background-location mode, travel time separated from on-site time, and region monitoring that wakes the app when someone reaches the door. These are OS entitlements, not permissions a tab can ask for.
Vision that runs on the handset
Hazard and PPE detection scored against the camera preview buffer at around 30 fps on the Apple Neural Engine or an NNAPI/GPU delegate, plus photo tagging, nameplate OCR and receipt parsing. Frames are scored and dropped in memory, so sensitive imagery never leaves the device.
Capture and identity backed by hardware
EXIF stamped with GPS, compass heading and a barometric floor estimate at the moment of the shutter; pressure-sensitive signature capture; LiDAR room measurement; and approvals signed by a Secure Enclave or StrongBox key rather than returning a boolean.
Alerts that break through silence
The iOS critical-alert entitlement and an Android bypassDnd full-screen intent are the only ways a page rings at forced volume with the ringer switch off — and a page that does not wake you is not a page.
Building something that lives on a phone?
Tell us what the app has to do and who has to use it — offline, on a peripheral, in the background, or through Do Not Disturb — and we will tell you plainly what building it natively involves, and whether we are the right team for it.
Start the conversation