NewFree MVP in 7 days

Mobile apps that feel nativeand keep the intelligenceon the phone.

We design and build iOS, Android and Flutter apps, with AI features that run on the device. They answer instantly, work offline, and don't send your users' data anywhere to do it.

Scroll
Example: an offline summary, on the phone
9:41Airplane mode

Meeting notes

Ship the onboarding redesign on Friday. Priya owns analytics events. Push notifications move to the next sprint because the copy isn't final. Test on older Android phones before release.

Summarized on this phone
  • Onboarding redesign ships Friday
  • Priya owns analytics events
  • Push notifications move to next sprint
Network requests0Time on device420 msData that left the phone0 bytes
SwiftSwiftUIKotlinJetpack ComposeFlutterDartStoreKit 2Play BillingApple Foundation ModelsGemini NanoCore MLTestFlight

What we build

Apps for phones and tablets, from the first prototype to the store listing. We pick the stack per product: fully native where the feel matters most, one shared codebase when it really saves time.

On-device AI

Summaries, search, transcription and smart replies that run on the phone, with a cloud fallback only when it's needed.

Apple Foundation ModelsGemini NanoCore ML

iOS

Native apps for iPhone and iPad that follow Apple's design and review guidelines from day one.

SwiftSwiftUIStoreKit 2

Android

Modern Android apps built for the whole range of devices, from flagships to older budget phones.

KotlinJetpack ComposePlay Billing

Flutter

One codebase for both platforms when the product suits it, with native modules where it doesn't.

DartPlatform channels

Store-ready

Listings, screenshots, privacy labels and review notes, prepared alongside the build.

App StoreGoogle Play
Free · 3 slots a month

Your app idea,on your phone,in 7 days.

Not a pitch deck. Not a Figma file. A real build of the one flow your app can't live without, running on your own phone by day 7. Free, and no contract.

One core flow on one platform. We read every request and take three a month, picking the ones we can do well in a week. How the week works →

  1. Day 1Pick the flow

    A 30-minute call. We choose the single flow that proves the idea and agree on what done looks like.

  2. Days 2–6Build in the open

    Short progress notes every day, and a test build on your phone by mid-week.

  3. Day 7Hand it over

    A TestFlight build or an APK, the source code, and a written plan with an estimate for version one.

  • A working iOS or Android build
  • One core flow, end to end
  • The source code, yours to keep
  • A plan and estimate for v1

Why free? A week of real work tells us both more than a month of calls. If you like it, we build the rest together. If you don't, you keep the code.

How we decide

Three numbers we design against. Each one is something your users feel, even if they never name it.

8.3ms

A frame on a 120 Hz screen

That's the time each frame gets on a modern display (16.7 ms at 60 Hz). We profile scrolling and animation on real devices, including older ones, before calling a screen done.

0bytes

Sent for an on-device feature

When a model can run on the phone, personal data stays there. Cloud AI is a deliberate choice for the jobs that need it, not the default.

1review

To get through the store

App Store and Google Play policies change every year. We plan for them early, so a launch isn't held up by a rejection over something avoidable.

How we work

Short loops, with something you can hold in your hand at each step.

  1. Step 1 of 4

    Scope

    We agree on the core flows, the platforms, and what "done" means for the first release.

    • Core user flows
    • Platforms and devices
    • What ships first
  2. Step 2 of 4

    Prototype

    A clickable build on your phone early, so decisions are made on the real thing.

    • Tap-through prototype
    • Real device, real data
    • Decisions on the thing itself
  3. Step 3 of 4

    Build

    Weekly builds through TestFlight and Google Play internal testing, with notes on what changed.

    • A build every week
    • Changelog with each one
    • Profiling on older phones
  4. Step 4 of 4

    Launch

    Store listings, review, release, and a handover of the code and accounts that are yours.

    • Listings and screenshots
    • Review and release
    • Code and accounts handed over

Notes fromthe field

We write about platform changes that affect the apps people ship: new store rules, OS releases, and what on-device AI can and can't do yet.

  • Oct 2026iOS 27 subscriptions: multiseat purchasing is on by default
  • Oct 2026The App Store's new product page and search assets
  • Oct 2026Google Play's target API 36 deadline
  • Oct 2026Android now checks who built your app
  • Oct 2026Apple's free on-device language model, and its limits

Have an appin mind?

Pick a time for a 30-minute call, or send a message if you'd rather write first. Either way, tell us what you're building and what has to work on day one.

30-minute intro callGoogle Meet, at a time that suits you. The link arrives by email.Book a 30-min call

Prefer LinkedIn? Message us there.

Send a message

What are you building? optional, pick any