Skip to content

Built it somewhere else.
It runs in a browser.
Bring it anyway.

Projects come to AirBuild from more than 1,000 tools.

Early access, by invitation from the waitlist.

orders.example.com

Your backend orders, payments

Keep it where it is. AirBuild builds the app beside it.

And it remembers the regulars’ usual order.

An example: pre-orders for a bakery.

The whole form.
One link, one sentence.

This is the first question on the waitlist, filled in the way we hope to see it. The link tells us where the app runs; the sentence tells us what the iPhone version should do first. That is enough to start reading.

Waitlist, question 1

Bring your app to iOS.

Project link (optional)

https://orders.example.com/

What should the iOS app do?

A pre-order page for a bakery: pick a pastry, choose a pickup time, pay. The iOS app should do the same for the regulars, and remember their usual order.

An example. Yours can be shorter. If the app talks to a backend or has pages behind sign-in, say so in the sentence, and leave the repository instead of the address.

What counts.
Anything a browser can open.

A published address on any domain. A repository we can read, when the app is not public or some pages are behind sign-in. A site from a builder, a Next.js app on a host of your own, an internal tool your team already uses. If a browser can open it, an AI team can read what it does.

What we build from it is a native SwiftUI app, not a wrapper and not an import. Your project is not changed and not moved; you keep working on it where it is, and the iOS app is built beside it. Tell us what it talks to, and we plan the app around that.

Real artists ship.

Steve Jobs, to the Macintosh team, 1983

What to bring.
Just the link.

  1. Where your app runs, or its repository if some pages are behind sign-in.

Built it in Lovable, Bolt.new or v0, or run a Shopify store? Those have their own pages.