Native iOS apps
Swift and SwiftUI apps for iPhone and iPad, with widgets, share extensions and the details that make them feel at home.
We design, build, release and maintain native apps, and we run nineteen of our own on the App Store and Google Play. That means we know what store review, subscriptions and real users do to an app after launch.
Swift and SwiftUI apps for iPhone and iPad, with widgets, share extensions and the details that make them feel at home.
Kotlin apps, or React Native when sharing one codebase across both platforms makes sense.
StoreKit, Play Billing and RevenueCat wired properly: entitlements, trials, restores and the edge cases nobody tests.
Screenshots, listings, privacy labels and review notes, through to approval on both stores.
iCloud and backend sync, offline-first storage and data that survives bad connections.
Push notifications, home-screen widgets and live updates that bring people back.
A few of the nineteen apps we build, release and keep current under our own name.
Live values for 1,000+ Murder Mystery 2 items, a free trade calculator and community feed.
Pass the California DMV written test first try — practice tests, flashcards and a mock exam simulator.
A lovely library for links, photos, videos and notes — with on-device search and offline saves.
A call and a written brief: the users, the core flows, the platforms and what success looks like.
Screens and interactions agreed in a clickable prototype before any code is written.
Short cycles with a TestFlight or internal-testing build you can install every week.
Store submission, crash monitoring and updates after launch, because that is when real problems show up.
Yes: 13 apps on the App Store and 6 on Google Play under our own name. We use Swift and SwiftUI, Kotlin, and React Native where sharing code makes sense.
Native when the app depends on platform features, polish or performance; React Native when one shared codebase saves real time. We recommend one in the scope, with the reasons.
Yes: listings, screenshots, privacy labels, review notes and any back-and-forth with review.
Yes. We start with a short code review, fix what is risky, then carry on with new features and releases.
Send a short brief — what you want to build, roughly when, and any constraints. We reply with honest next steps, scope and timing.