Devin does build mobile apps, and its own documentation says where it stops.
Most pages in this series exist because a tool cannot make a mobile app. This one is the opposite. Cognition documents Devin running on macOS virtual machines with Xcode and the iOS Simulator preinstalled, building and testing iOS apps, uploading builds to TestFlight, and driving a full Android emulator with React Native named in the blueprint examples. There is a tutorial in the docs where the whole prompt is one sentence asking for an iPhone game. So the useful question is not whether Devin can do mobile work. It is where the documented path ends, which is at the Simulator for devices, at TestFlight for iOS distribution, and nowhere at all for Google Play. If you have not written any of the app yet, start from build mobile app without coding.
One thing to settle first, because two products share the name. This page is about Devin the cloud agent, the one you hand a task to at app.devin.ai. Cognition also sells Devin Desktop, which is the editor that used to be called Windsurf: on 22 October 2026 windsurf.com answered with a 308 redirect to devin.ai/desktop, and codeium.com before it redirects to windsurf.com. Same company, two products, and the editor answers a different question from the agent. If the editor is what you actually use, read windsurf to mobile app instead.
Every claim about Devin below comes from docs.devin.ai or devin.ai/pricing, read on 22 October 2026, and that includes the prices, which have moved before. Where the documentation says no, the page says no.
Start hereThe short version
Devin is an engineer with a Mac, and it bills by the work.
Cognition describes Devin as an autonomous AI software engineer that can write, run and test code, and sets the expectation like this: as a rule of thumb, if you can do it in three hours, Devin can most likely do it. The strengths listed in its introduction are Linear and Jira tickets, features built from scratch, bug repro and fixes, migrations and refactors, PR review, unit tests and internal tools. Mobile is one of the environments it can work in, not the product it sells.
That shapes the whole decision. You point Devin at a repository, configure a blueprint so sessions boot with the right toolchain, and ask for work. If there is no repository and no project yet, you are paying an engineer by the task to produce a first commit, and the usage meter does not know or care that this is day one. Decide which of those two situations you are in before you read any further.
What does Cognition document Devin as doing?
Writing, running and testing code in a session that has a shell, an embedded IDE and a browser you can take over. The docs put the session on Linux by default, and a blueprint field called runs-on picks the platform: default or linux, macos, or windows. Each platform gets its own snapshot, and an admin can make macOS the default for new sessions. You can also start a macOS session from Slack with a bang command, or by setting the platform field when you create a session through the API.
The macOS image is the part that matters for an app. It carries the latest Xcode 26 release as the default at /Applications/Xcode.app plus the Xcode 27 prerelease alongside it, one iOS Simulator runtime per installed Xcode, and xcodebuild, xcrun, simctl, Swift and the Metal toolchain. Homebrew sits at /opt/homebrew, repos clone to /Users/devin/repos, and the shell is zsh. Devin can boot a named simulator with xcrun simctl boot, install an app on it and launch it, and the iOS Simulator tab in the workspace streams the booted device so you can watch the taps happen.
Four limitations are published rather than discovered. There is no USB passthrough, so testing happens on simulators and not on physical iPhones or iPads. There is no nested hardware virtualisation, so containers fall back to software emulation and run roughly 15 to 25 times slower on CPU than native. Fetching another Xcode or simulator runtime needs Apple ID credentials and a long download. And profiling inside a VM is not representative of real device performance. Those are the sentences to read twice if your plan involves performance work.
Devin Docs, macOS support, read 22 October 2026
Check yours
Tick the job you actually need done
The Devin column is what Cognition's own documentation says, read on 22 October 2026, and it includes the two places where the answer is no. The Newly column is what Newly does. Tick a job to see both.
Nothing ticked yet. If the honest answer is that you want an engineer to pick up tickets on an app that already exists, Devin is the tool on this page built for that, and you can stop reading here.
Is mobile and React Native work in scope?
Yes on both platforms, and React Native is named in the documentation rather than implied. Devin's Android emulator support page asks whether you are building with React Native, Flutter or Kotlin Multiplatform and says Devin can test the Android side alongside your web or desktop builds in the same session. One of the blueprint examples is headed React Native. It installs Node 20, downloads the Android command line tools, installs platform tools, build tools 34.0.0, the android-34 platform and an x86_64 system image, creates an AVD on a pixel_6 profile, runs npm install and gradlew assembleDebug as maintenance, and stores npx react-native run-android as the command for running on the emulator.
The Android loop is a test loop. Devin installs the APK with adb, taps through flows with Computer Use, captures logcat for a crash or an ANR, runs Espresso or UI Automator suites, and sends you a video recording of the run. The docs recommend x86_64 system images because ARM images are significantly slower under emulation, and suggest running with no window and no audio when nobody needs to watch. What the docs do not contain is a path out of the emulator. Devin publishes three documentation indexes, 268 cloud pages, 104 Devin Desktop pages and 304 API pages, and on 22 October 2026 not one entry in any of them is about Play Console, Play app signing or publishing to Google Play.
One wrinkle about accounts, because it catches people. Cognition bills Devin cloud sessions, the Devin CLI and Devin Desktop against the same quota, and the link behind Devin Desktop in those billing docs goes to windsurf.com. So a Pro subscription is one allowance spread across all three surfaces rather than one allowance each, and a Teams flex seat gets no Devin Desktop access at all and draws only on the shared credit pool. Worth knowing before you count what a seat buys.
What does Devin cost, and in what unit?
On 22 October 2026, devin.ai/pricing listed five tiers: Free at $0, Pro at $20 a month, Max at $200 a month, Teams at $80 a month for the team plan plus $40 a month per full developer seat, and Enterprise on request. Devin's own billing docs add the mechanics behind those numbers. Teams pays at least $80 a month whatever the seat count, a full seat carries a Pro-equivalent allowance, and a flex seat costs nothing but draws entirely from the team's shared pool of prepaid on-demand credits. Both seat types count against a 200 user cap. These figures have changed more than once, so read the page rather than this sentence if the budget is real.
The unit is the thing to understand, because it is not a build and not a seat-hour. Each paid plan carries a usage allowance that refreshes on a daily and weekly basis, and usage accrues from the number and complexity of the actions Devin takes, plus a small fraction for virtual machine time. The pricing page says cost per message varies based on the model used, the task size and complexity, and the reasoning required. Past the allowance you buy extra usage, consumed at API pricing. Enterprise contracts are metered in Agent Compute Units at the rate written into the order form, and no dollar figure for an ACU appears in the public docs.
Two numbers are worth writing on the plan. A macOS session currently consumes the same usage as an equivalent Linux session with no surcharge, and the docs mark that as promotional launch pricing, subject to change. A Windows session consumes approximately 9 percent more. Also note the entry price for Apple work: the iOS tutorial opens by telling you to make sure you have a Pro or Teams account, because macOS sessions are available by default there, so the cheapest documented route to an iPhone build is $20 a month and not the free tier. Idle time is cheap by comparison, since a session sleeps after 30 minutes of inactivity and consumes nothing while asleep.
Devin Docs, macOS support, usage and cost, read 22 October 2026
Two different tools, read against the same list
The left column is what Cognition documents on 22 October 2026. The right column is Newly, which costs $25 a month and has no free tier. This is not a scoreboard, because the two products answer different questions. Read it as a list of jobs and find the row you care about.
| The job | Devin, per its own docs | Newly |
|---|---|---|
| Uploads an iOS build to TestFlight | Yes, with an App Store Connect API key you create and store as secrets | Yes |
| Publishes to Google Play internal testing | No | Yes |
| Produces an installable Android file | A debug APK for the emulator | A standalone APK |
| Opens pull requests in your repository | Yes | Two-way GitHub sync |
| Writes React Native | Yes, and anything else your repo is written in | React Native and Expo, and nothing else |
| Tests on a physical phone | No | Through TestFlight and Play testers |
| Submits to the App Store for you | No | No |
| Has a free tier | Yes, with limited usage, but macOS sessions need Pro or Teams | No |
Apple, App Review Guidelines, last updated 16 October 2026, read 22 October 2026
Who has to do the App Store paperwork?
A person, and both sides of this page agree on it. Devin's TestFlight page lists what you have to do before any upload can work, and says plainly that Devin cannot do those steps for you, because most require an Account Holder or Admin and some need two-factor authentication on a person's Apple Account. The list is the Account Holder accepting pending agreements, registering an App ID that matches your bundle ID, creating the app record with a platform, name, primary language and SKU, creating a beta group, and answering the export compliance question for every build unless you set ITSAppUsesNonExemptEncryption in the app's Info.plist.
Then there is the key itself. Devin authenticates with an App Store Connect team key carrying the App Manager role, not an Apple Account, and you store four values as secrets. Apple lets you download the private key file once, so if you lose it you revoke the key and generate another. Anyone holding that file can upload builds and manage TestFlight for every app on the team, which is a good reason to keep it out of a repository. The practical steps on the Apple side are the same whichever tool produced the binary, and they are written up in publish to app store.
Newly sits at the other end of the same problem. You describe the app in plain English and get a real React Native and Expo project you own, with two-way GitHub sync, iOS builds uploaded to TestFlight, publishing to Google Play internal testing, and a standalone Android APK when you need a file to hand someone. It costs $25 a month and there is no free tier. It will not press submit on the App Store for you, and that is deliberate: Apple guideline 4.2.6 says apps created from a commercialized template or app generation service will be rejected unless they are submitted directly by the provider of the app's content, and that these services should not submit apps on behalf of their clients. Any builder offering to submit for you is offering a rejection.
One last honest note on choosing. If your app exists and you want a backlog cleared, hire the engineer: that is what Devin is sold as, and its iOS and Android support is unusually well documented for a coding agent. If nothing exists yet, paying by the task to get to a first commit is an expensive way to start, and a generator gets you a project faster. The same reasoning applies when your starting point is a database rather than a repo, which is the subject of notion to mobile app.
Apple, App Review Guidelines, guideline 4.2.6, read 22 October 2026
Questions people ask about Devin and mobile apps
Yes, and Cognition documents it rather than hinting at it. Devin runs on macOS virtual machines, and the macOS support page says this means Devin can build and test iOS and macOS applications and upload builds to TestFlight. The session image ships the latest Xcode 26 release as the default plus an Xcode 27 prerelease alongside it, one iOS Simulator runtime per installed Xcode, and xcodebuild, xcrun, simctl and Swift. There is a step-by-step tutorial in the docs where the prompt is one sentence asking for a game and Devin creates the Xcode project, fixes build errors, runs it in the Simulator and plays it. Read on 22 October 2026.
If there is no repository yet, start with the app.
Write down the screens, the one thing the app has to do on a phone with no signal, and who holds the Apple account. That list is the brief, and it is the same brief whether an engineer or a generator writes the first commit.
Start building