Preview · an iOS builder with a review desk
Describe the app in a sentence. Dirl’s agents build it in Swift, then keep working Apple’s review notes with you after upload.
Free tier runs on your own API key. Plans are a preview.
01
Swift and Apple’s own UI frameworks. A real app, not a website in a wrapper.
02
Apple’s notes become a thread with an owner, a fix, and a drafted reply.
03
Start from a Shopify store or a site made with Lovable, Bolt, or v0.
04
Build on hosted Macs or on your own. Same project, same agents.
The review desk
When Apple sends notes, they land here as a thread with an owner, a fix, and a drafted reply. You read it, you approve it, and it goes back with the new build.
Guideline 2.1 — Performance: App Completeness
The app crashed when we declined camera access while adding a plant. Please fix the crash and resubmit.
Guideline 2.3.3 — Accurate Metadata
Screenshot 3 shows a home screen widget we couldn’t find in the app.
Two items. Swift takes the crash, Interface takes screenshot 3. I’ll write the reply.
Fixed in build 13. Declining the camera now opens the photo library instead.
AddPlantView.swift
let photo = try! await camera.capture()
guard let photo = try? await camera.capture() else {
showLibraryPicker = true; return
}
Screenshot 3 now shows the plant list. The widget shot waits for 1.1.
Thanks for the notes.
2.1 — Build 13 fixes the crash. If camera access is declined, the app offers the photo library instead.
2.3.3 — Screenshot 3 now shows the plant list. The widget will arrive in a later version.
Apple’s notes arrive as a thread with the guideline attached, not an email you find three days later.
The Clerk drafts the reply. You read it and approve it. Nothing goes back to Apple without your OK.
The fix travels with the reply. Build 13 is uploaded and retested before you are asked.
The agent room
Each agent owns a piece of the app. When work moves, it moves on the board, and the log says who handed what to whom, and why.
Thirstiest-plant widget
InterfacePlant list and empty state
InterfaceOffline watering reminders
SwiftCamera purpose string
SwiftListing, privacy labels, review notes
ClerkHandoff log
Plant care app. One photo per plant, a nudge when it’s thirsty. Works offline.
Plant list first. Big names, one tap to water.
Reminders have to work offline. No sign-up.
List and empty state are on the simulator.
Reminders fire in airplane mode. Try to break them.
Both pass. The camera prompt only says “Camera access”.
Review will flag that. Say what the photos are for.
Start the widget. It ships in 1.1, not this build.
Purpose string rewritten. It’s in build 12.
You approved. Build 12 is submitted; I’ll watch for Apple’s reply.
Turns the brief into a plan and decides what ships first.
Screens, motion, icons, and the store screenshots.
Data, logic, and device features, written in Swift.
Runs each build the way a person would, offline too.
Listing, privacy labels, review notes, and replies to Apple.
Sample project. Agent roles are illustrative.
Bring a site
Bring a Shopify store or a site built with Lovable, Bolt, or v0. Dirl reads what’s there, and the agents use it as the brief for a native app.
How bringing a site worksPlans · preview
Monthly, in US dollars. Tell us which plan you’d start on when you join the waitlist.
$0/ month*
Build on your own model key.
Model usage is billed by your provider.
Join the waitlist for FreeReview desk included
$20/ month*
The full review desk.
Everything in Free, plus
One builder, one app at a time.
Join the waitlist for Pro$200/ month*
More room. More apps.
Everything in Pro, plus
For people running more than one app.
Join the waitlist for Max* Preview figures, may change before launch. Full plan details
Questions
Something missing? Ask support.
Yes. Dirl writes Swift with Apple’s own UI frameworks, so what you get is an iOS app, not a website in a wrapper. That matters at review time too: Apple tends to push back on apps that are only a web view.
Most builders stop at the upload. In Dirl, the Clerk agent keeps the submission open. When Apple sends notes, it opens a thread, hands each fix to the agent that owns that part of the app, and drafts the reply. You approve the reply and the new build before anything goes back.
To publish, yes. Apps go out under your own developer account, so the listing is yours. You can start building before you have one.
No. Builds can run on hosted Macs in the cloud. If you have a Mac, you can build locally instead and switch whenever you like. The project and the agents come with you.
Yes, that’s what Bring is for. Point Dirl at a Shopify store, a site made with Lovable, Bolt, or v0, or anything with a URL. The agents treat it as the starting brief.
How bringing a site worksThe agents run on a language model. On Free, you connect a key from your model provider, and the provider bills you for usage. Paid plans include a model allowance.
Dirl is in preview. Join the waitlist and we’ll send an invite when there’s room. We’d rather not promise dates we might miss.