› should we build native or cross-platform
Application Engineering
One product, every screen, no compromise on the native feel.
Cross-platform apps that respect each platform’s idioms instead of flattening them. Built for the App Store, Play Store and the browser from a shared core, with gesture, haptics and offline behaviour handled properly. This is a new practice for us — see the note below.
What we hold ourselves to
60fps
Interaction budget
44pt
Minimum touch target
<100ms
Tap-to-feedback
These are the budgets we build against and measure on handover — not a warranty. Where a target can’t be met we tell you which one and why, before you sign.
New practice. We have no shipped client work in this discipline yet. The engineering standards above are real and we hold to them, but if you need someone with a delivered track record here, we will tell you that on the first call rather than the last.
What this actually includes.
Cross-platform
iOS and Android from one codebase, without the uncanny valley.
- Platform-adaptive navigation — tab bar on iOS, top app bar on Android
- Native gesture handling and haptic feedback
- Shared design tokens across mobile and web
- Over-the-air update pipeline
Native
When the hardware is the product.
- Swift / Kotlin where the platform API demands it
- Camera, BLE, background tasks and secure enclave work
- Deep-link and widget surfaces
- App Store review preparation and release management
PWAs
Installable, offline-first, zero app-store friction.
- Service worker caching with a real offline state
- Install prompts and standalone display handling
- Push notifications and background sync
- Works down to 3G with graceful degradation
Delivery surfaces
- iOS
- Android
- Web App
- Desktop
- Watch
Typical stack
- React Native
- Expo
- Swift
- Kotlin
- Workbox