Bitrig
A macOS app that turns plain-English descriptions into real Swift code and complete Xcode projects, tests them in built-in simulators, and handles code signing, TestFlight and App Store publishing for every Apple platform.
What is Bitrig?
Bitrig is a macOS application that turns a written description of an app into working Swift code and a complete Xcode project. It is published by Bitrig, Inc., a company founded by co-creators and longtime members of Apple's SwiftUI team, and it runs only on Apple silicon Macs under macOS 15 or later.
The workflow starts as a conversation. You describe what you want to build, Bitrig writes the code, and the result launches inside a built-in simulator framed in a photorealistic 3D device that can be rotated and lit dynamically. It does not stop at rendering: through a capability the vendor calls Simulator Use, Bitrig interacts with the app the way a person would — tapping, scrolling and typing — spots interface problems and fixes what it finds.
The coding itself is delegated to frontier agents. Bitrig ships with Claude Code and Codex, running the latest Anthropic and OpenAI models, and it accepts any agent that speaks the Agent Client Protocol, including Cursor, Grok Build and OpenCode. Rather than metering tokens, it lets you connect a Claude or ChatGPT subscription you already pay for.
What comes out is a real Xcode project, built with the full toolchain and current SDKs, openable in Xcode at any time and exportable even on the free plan. Coverage extends well past a single screen: widgets, Live Activities, Controls, App Intents, Shortcuts, Siri, Spotlight, Watch complications, Liquid Glass, Apple Intelligence, Metal, PencilKit and SF Symbols, with targets for iPhone, iPad, Mac, Apple Watch, Apple TV and Vision Pro. Backends can be wired to CloudKit or Supabase, push notifications included, and monetisation to StoreKit in-app purchases, subscriptions, native paywalls and RevenueCat.
Publishing happens in the same window. Bitrig creates the App Store record, archives and signs builds, handles provisioning, uploads to TestFlight and the App Store, keeps the store listing inside the project and captures the screenshots each required device and localisation demands. Changes can be pushed back through an existing GitHub workflow. A companion app, Bitrig Remote, distributed through TestFlight, streams simulators to an iPhone or iPad so the same work continues away from the Mac.
What it does
- Turn a written description into working Swift code and a complete Xcode project.
- Run the app in a built-in photorealistic 3D simulator, then test it by tapping, scrolling and typing like a user, and fix the bugs it finds.
- Archive, sign and upload builds to TestFlight and the App Store, provisioning included.
- Manage the App Store listing from inside the project and capture screenshots for every required device and localisation.
- Wire a CloudKit or Supabase backend, with user accounts, server-side code and push notifications.
- Add StoreKit in-app purchases, subscriptions, native paywalls and RevenueCat.
- Review diffs, edit source files and push changes back through an existing GitHub workflow.
When to use Bitrig / When not to
A quick filter to help you decide if Bitrig is the right fit.
When to use Bitrig
- Swift and iOS developers who want to move from prototype to App Store submission faster, while keeping a normal Xcode project.
- Designers and product managers who can specify an app precisely but do not want to hand-write SwiftUI.
- Indie developers and startup founders shipping Apple apps on their own, without a dedicated release engineer.
- Small teams already working through GitHub, who need generated changes to land in their existing review workflow.
- Builders targeting the wider Apple surface — widgets, Live Activities, Apple Watch, Apple TV or Vision Pro — rather than a single iPhone screen.
When not to use Bitrig
- Anyone building for Android or the web: Bitrig produces native Apple code and nothing else.
- Owners of Intel Macs or machines below macOS 15, since Apple silicon and macOS 15 are hard requirements.
- Teams that need a public API or a headless build server: no API or developer documentation is published.
- Organisations whose procurement requires a signed DPA, a named subprocessor list or an EU Article 27 representative, none of which the vendor publishes.
- People under 13, and users located in countries under United States embargoes, both excluded by the terms of service.
How to use Bitrig
A typical end-to-end flow, from setup to results.
- Download the Mac app from the site; the download page redirects to app.bitrig.com/download/latest.
- Check the hardware requirement first: an Apple silicon Mac running macOS 15 or later.
- Create an account, which the terms of service make mandatory.
- Optionally connect the Claude or ChatGPT subscription you already hold, to avoid paying per token.
- Describe the app you want in the conversation; each exchange consumes credits according to how complex the task is.
- Let Bitrig run the build in the integrated 3D simulator, test it by interacting with it, and fix what it breaks.
- Review the diffs and edit source files inside Bitrig, or open the same project in Xcode.
- Connect GitHub, and add a CloudKit or Supabase backend, push notifications, in-app purchases or RevenueCat as needed.
- Obtain a paid Apple Developer account, at 99 USD per year, before distributing anything.
- Publish to TestFlight and then the App Store from Bitrig, or from an iPhone or iPad using Bitrig Remote.
Pros & Cons
Pros
- Founding team drawn from Apple's SwiftUI group, with four named co-founders and public profiles.
- Output is a standard Xcode project, exportable at any time and on any plan, which limits lock-in.
- An existing Claude or ChatGPT subscription can be reused instead of paying token-metered API prices.
- The tool tests its own work in the simulator, interacting with the app rather than only rendering it.
- Publishing is genuinely end to end, including code signing, provisioning and localised App Store screenshots.
- Coverage of the whole Apple surface, from widgets and Live Activities to tvOS and visionOS targets.
- A permanent free plan with daily credits, and a weekly release cadence documented in a public changelog.
Cons
- Runs only on Apple silicon Macs under macOS 15 or later, with no Intel or older-macOS path.
- Builds Apple apps exclusively: no Android, no web output.
- Bitrig Remote is still distributed through TestFlight, with no public App Store listing.
- No public API and no developer documentation are offered.
- Credit limits shape everyday use: 15 daily credits capped at 60 a month on the free plan, 200 a month on Pro, with rollover limited to one month and conditional on an active subscription.
- Distribution to TestFlight or the App Store requires a separate paid Apple Developer account at 99 USD per year.
- Compliance documentation is thin: no DPA, no named subprocessor list, no Article 27 representative, no documented training opt-out and no postal address on the site.
Pricing & Plans
A permanent free plan is available at 0 USD per month, with 15 daily credits capped at 60 per month and 10 daily requests through a connected Claude or ChatGPT subscription. The lowest paid entry point is the Pro plan at 25.00 USD per month. A Teams & Enterprise tier is offered on quote only, with no published price. Distributing an app to TestFlight or the App Store additionally requires a paid Apple Developer account, which the vendor states costs 99 USD per year and is billed by Apple, not by Bitrig.
- 10 daily requests using your own Claude or ChatGPT subscription
- 15 daily credits capped at 60 per month
- native Swift apps for every Apple platform
- access to Bitrig Remote
- and code export at any time.
- everything in Free
- plus unlimited daily requests through your Claude or ChatGPT subscription
- 200 monthly credits
- rollover of unused credits for one month while the subscription stays active
- distribution to TestFlight and the App Store
- installation to your own device from Bitrig Remote
- and priority support and feature requests.
- Teams & Enterprise — price on request
- presented as building and shipping with a whole team
- quotes are requested by email to contact@bitrig.com.
Data, GDPR & hosting
A consolidated view of how Bitrig handles your data.
GDPR overview
The site never uses the word GDPR, but the privacy policy dated 27 June 2025 implements much of its machinery under the heading European Privacy Rights. Bitrig, Inc. names itself as data controller and lists its legal bases: contract performance, legitimate interests, legal obligation and consent where required. Users are told they may lodge a complaint with their local supervisory authority. Section 10 grants access, correction, account deletion, data portability and an email opt-out, exercised through support@bitrig.com with a ten-business-day response target. Section 7 states that data is stored and processed in the United States and that Standard Contractual Clauses or equivalent safeguards apply where required. No data protection officer, no Article 27 representative and no data processing agreement are mentioned anywhere.
Who owns the data?
Under section 4 of the terms of service, you own the code, projects and messages you create. Bitrig, Inc. receives a limited licence to store, process, back up and — in anonymised form — analyse that content in order to improve the service and its AI models. Bitrig, Inc. separately owns its own trademarks, logos and non-user content. Projects are private by default, but tapping Share publishes a link that anyone can open without an account, and signed-in users may remix it; sharing grants Bitrig and every link holder a perpetual, worldwide, royalty-free licence. Support can disable a link, yet copies made beforehand survive.
Reuse rights
Users may reuse what they create without asking permission: the terms grant a personal, non-exclusive, non-transferable and revocable licence to use the service and any code it generates, and the pricing page states that code can be exported at any time, including on the free plan. Output is delivered as-is, so the vendor expects you to review and test it before production. On the vendor's side, the privacy policy limits use of your data to authentication, storage and synchronisation, AI features routed through third-party model providers, aggregated usage analysis and investigation of bugs, security events or misuse. Behaviour-based advertising and cross-site tracking are excluded, and contact information is never sold or rented. Sharing a project, however, hands a perpetual licence to Bitrig and to everyone holding the link.
Data retention & training
Hosting summary
The privacy policy states plainly that Bitrig stores and processes information in the United States, and that where required it relies on Standard Contractual Clauses or equivalent safeguards for international transfers. On security, it commits to TLS 1.3 in transit, encryption at rest where supported, and access restricted to the founders, while declining to guarantee absolute security. The terms add that the service is operated from the United States. No hosting provider, data centre region or availability zone is named: third parties appear only as categories, namely cloud hosting and infrastructure vendors, an analytics provider and an AI model provider. No certification such as SOC 2, ISO 27001 or HIPAA is claimed anywhere on the site, and no data processing agreement is offered. The Netherlands IP address returned by DNS belongs to an anycast content-delivery node and does not indicate where user data lives.
Where Bitrig works
Country-level availability.
Not available in
Things to keep in mind
Risks and trade-offs to weigh before adopting Bitrig.
- Generated code is supplied as-is: the terms explicitly place review and testing before production use on you, and an app that looks right in a simulator has not been audited.
- Sharing a project publishes it. The link works without an account, signed-in users can remix it, and copies made before a link is disabled keep the licence they were granted — so anything confidential should never enter a project you intend to share.
- User content may be analysed in anonymised form to improve the service and its AI models, and no opt-out from that analysis is documented.
- Fluency can outrun understanding: shipping Swift you did not write, to real users, makes it easy to lose the ability to diagnose the app when something eventually breaks.
- Credit mechanics reward haste. Daily and monthly caps, and rollover limited to a single month under an active subscription, push toward using the allowance rather than thinking the problem through.
- Compliance gaps matter for anyone handling third-party personal data: no DPA, no named subprocessor list, no Article 27 EU representative and no published postal address.
- Commercial and jurisdictional terms are one-sided: billing through the App Store is non-refundable except where law requires, EU and UK users waive the fourteen-day withdrawal right, disputes go to San Francisco County courts and class actions are waived.
Setup & Integrations
Technical difficulty
Low for a development tool. There is no server to configure: you download a Mac application, create an account and start describing the app you want. The two real prerequisites are hardware and paperwork — an Apple silicon Mac on macOS 15 or later, and, only when you want to distribute, a paid Apple Developer account at 99 USD per year. Connecting an existing Claude or ChatGPT subscription is optional. No Xcode expertise is needed to begin, although what you end up with is a standard Xcode project. Bitrig Remote requires going through TestFlight.
Deployment
Integrations
Behind Bitrig
Fundraising
Social
Resources
All the official URLs gathered for verification and reference.
Frequently asked questions
What exactly does Bitrig produce?
What do I need to run it?
What are credits, and how many do I get?
Do I have to pay per-token AI prices?
Do I need an Apple Developer account?
Is there a mobile version?
Where is my data stored?
Are my projects private?
Is my code used to train AI models?
How do I cancel?
Should you pick Bitrig?
Bitrig occupies a narrow and unusually well-defended position: it is an AI app builder that targets nothing but native Apple platforms, and that hands back an ordinary Xcode project rather than a proprietary artefact. That single design choice does most of the work, because it means the output survives the tool. A project started in Bitrig can be finished in Xcode, handed to a contractor, or pushed through an existing GitHub review process, and code export is promised on every plan.
The credibility argument is equally concrete. The company is founded by co-creators of Apple's SwiftUI team, four of whom are named on the about page, and the changelog shows a genuine weekly release rhythm across roughly a year. The feature surface is unusually complete for a young product: simulators that test the app by using it, code signing and provisioning, App Store listing management, localised screenshots, CloudKit and Supabase backends, StoreKit purchases and RevenueCat.
The reservations are mostly about maturity rather than capability. Hardware requirements are strict — Apple silicon and macOS 15. The iPhone companion is still a TestFlight build. There is no API. Compliance documentation is thin for anything beyond an individual developer: no data processing agreement, no named subprocessor list, no EU representative, no documented way to exclude your code from the anonymised analysis the terms permit, and no postal address published anywhere on the site. Publishing also carries an unavoidable outside cost, the 99 USD annual Apple Developer account.
For an indie developer, a designer with a shippable idea or a founder who needs an app in the store, the free plan makes the evaluation nearly costless and the 25 USD monthly tier is modest. Procurement-driven organisations should wait for the paperwork to catch up with the product.
- Choosing a selection results in a full page refresh.
- Opens in a new window.