App development — iOS · Android · Wear

Apps people keep.

Native and cross-platform apps engineered for week six, not day one. 120 Hz interfaces, offline-first data and a release pipeline that ships on a Tuesday afternoon — no war room required.

Frame budget
8.3ms
Cold start
<2s
Crash-free
99.9%
Swift ✦ SwiftUI ✦ Kotlin ✦ Jetpack Compose ✦ React Native ✦ Expo ✦ Flutter ✦ watchOS ✦ Wear OS ✦ Core ML ✦ Room ✦ SQLite ✦ GraphQL ✦ Fastlane ✦ TestFlight ✦ Play Console ✦
01 — Platforms

Pick the stack after the problem.

We're fluent in all four, so we have no reason to sell you the wrong one. Tap a platform — the device morphs to show how each one actually feels.

Native iOS

Swift and SwiftUI, straight onto Apple's frameworks. The fastest route to platform-perfect motion, day-one OS features and the deepest hardware access.

Choose it when

  • Your customers skew iPhone (finance, premium retail, health)
  • You need Live Activities, widgets, App Intents or Apple Pay on day one
  • Motion and haptics are part of the brand

Trade-off

A second codebase when Android follows. We share the API, design tokens and test fixtures to keep that cost near 0.6×, not 2×.

Swift 6SwiftUICombineSwiftDataXCTest
02 — Under the glass

The hard parts, handled.

Six things that separate an app people keep from one they delete. Scroll — the phone runs each one live.

01

Biometric auth that feels like nothing.

Face ID, Touch ID and Android BiometricPrompt, backed by keys that never leave the Secure Enclave or StrongBox. Step-up auth on risky actions only — so a transfer asks twice, and checking a balance asks once.

LocalAuthenticationBiometricPromptPasskeys
02

Offline-first, not offline-tolerant.

Every write lands in a local database first and syncs when it can. Lifts, basements, rural highways — the app keeps working, queues changes, and merges them conflict-free when signal returns.

SQLite / RoomCRDT mergeBackground sync
03

Push and real-time, politely.

Notifications people don't mute: grouped, actionable, timed to the user's day. Live Activities and the Dynamic Island for things that are actually live, with socket-backed state that survives a dropped connection.

APNsFCMLive ActivitiesWebSockets
04

Machine learning, on the device.

Pose tracking, OCR, classification and transcription run on the Neural Engine or NNAPI — fast, private, free per inference and still working in airplane mode. Cloud models only where they earn their latency.

Core MLTensorFlow LiteML KitVision
05

Accessible at every size.

Layouts that reflow at 310% Dynamic Type, VoiceOver and TalkBack labels written by humans, and contrast checked in CI. Try it — drag the slider and watch the screen adapt.

100%
Dynamic TypeVoiceOverTalkBackWCAG 2.2 AA
06

Payments in two taps.

Apple Pay and Google Pay sheets, StoreKit 2 and Play Billing subscriptions, server-verified receipts and graceful retries. The checkout is the one screen we refuse to make interesting.

Apple PayGoogle PayStoreKit 2Stripe
03 — Feel

Go on, throw one.

Great apps are physical. Every gesture we ship runs on real spring physics with velocity hand-off — so a flick feels like a flick. Triage this roadmap: swipe right to ship, left for later.

spring.configidle
320
18
x 0pxv 0px/sζ 0.50
Roadmap triaged. 0 shipped · 0 later
0 shipped · 0 later

Drag, flick, or use ← → when focused

04 — The quality bar

Standards, not vibes.

The numbers every build is held to before it reaches a single customer. Targets, measured in CI — not adjectives in a pitch deck.

Render120fps

ProMotion-ready lists and transitions. 8.3ms frame budget, profiled in Instruments and Perfetto.

Cold start<2s

p95 target on a three-year-old mid-range Android. Measured on real devices, every release.

Stability99.9%

Crash-free sessions target, with staged rollouts that halt automatically if it dips.

Coverage80%+

Unit coverage on domain logic, plus UI and snapshot tests across light, dark and large text.

ci — release/2.4.0 — illustrative pipeline
// example output — your pipeline, your stores, same discipline
05 — Engagements

Start small. Scale honestly.

Fixed-scope phases with indicative pricing. Every engagement ends with code you own, a working CI pipeline and a team that can carry it.

Validate

Prototype Sprint

from $15k AUD
3–4 weeks
  • Clickable native prototype on real devices
  • Five moderated user tests
  • Technical spike on the riskiest feature
  • Platform recommendation & build estimate
Book a sprint →
Most chosen Launch

MVP

from $40k AUD
8–12 weeks
  • iOS + Android from one codebase, or one native platform
  • Auth, payments, push, analytics
  • API / backend, offline cache
  • CI/CD to TestFlight & Play, store submission
Scope an MVP →
Scale

Flagship

from $120k AUD
4–9 months
  • Fully native iOS & Android, shared design system
  • Offline-first sync, on-device ML, wearables & widgets
  • Security review & pen-test readiness
  • Performance budgets enforced in CI
Plan a flagship →
Keep

Care Plan

from $3.5k / month
Ongoing
  • Annual iOS / Android OS readiness
  • Crash & performance monitoring
  • Fortnightly releases, dependency hygiene
Talk care →

Indicative pricing in AUD, excluding GST. Final quotes follow a free scoping call.

07 — FAQ

Asked often.

Something else? Send us a brief →

Native or cross-platform — which should we choose?

It depends on your users, your feature list and who maintains it after launch. Cross-platform (React Native or Flutter) wins for content, commerce and most B2B apps on a budget. Native wins when the app is the product: heavy animation, hardware, wearables, or day-one OS features. We'll recommend one in the scoping call and tell you why.

How long does an app take to build?

A validated prototype in 3–4 weeks, a store-ready MVP in 8–12 weeks, and a flagship native build in 4–9 months. You'll have a TestFlight / Play internal build to hold from week two onward.

Do you handle design, or just engineering?

Both. Product design, motion and the component library are built alongside the code by the same team — which is how the details survive into production.

Who owns the code and the store accounts?

You do — from the first commit. Repos, App Store Connect, Google Play Console, signing certificates and CI all live in your organisation. We're invited in, not the other way around.

Can you rescue or take over an existing app?

Yes. We start with a two-week audit — crash analytics, architecture, build pipeline, dependencies — and hand you a prioritised plan before touching a line of code.

What about App Store and Play review?

We prepare listings, privacy labels, data-safety forms and review notes, and design features around the guidelines from the start. Rejections are rare and usually turned around within a day.