Runable builds iOS apps without Xcode

Runable is pitching a mobile release workflow that removes one of Apple development’s usual constraints: a local Mac running Xcode. The company said it can build iOS and Android production binaries in its cloud environment and push them to Apple’s App Store and Google Play from the same flow. The claim surfaced in a public demo and challenge campaign tied to Apple’s developer ecosystem, though Runable has not yet published a dedicated technical document laying out the full mobile pipeline end to end. Apple’s own submission rules make the claim more specific than “no Xcode.” Since April 28, 2026, apps uploaded to App Store Connect must be built with Xcode 26 or later and use the latest Apple SDKs, according to Apple’s developer requirements. That means any third-party system promising direct App Store delivery still has to run Apple’s current toolchain somewhere in the process, even if developers do not install it on their own laptops. (runable.com) ### If there is no local Xcode, what is Runable actually replacing? Runable’s public product materials describe an agent that writes code, runs commands, installs packages and executes multi-step tasks inside an isolated sandbox. The company says Agent Mode can build projects, search the web, start servers and handle execution inside that environment, rather than on a user’s machine. (developer.apple.com) Runable’s documentation does not say Apple’s toolchain disappears. Apple requires Xcode 26 or later for App Store uploads, and Xcode 26 includes the iOS 26 SDK and related platform SDKs. The practical change is where the toolchain runs: in a hosted environment instead of on a developer’s Mac, if Runable’s demo reflects the production path. (docs.runable.com) ### Why does Apple’s April 28 rule matter so much here? Apple set a hard baseline on April 28, 2026: App Store Connect accepts uploads only if they are built with Xcode 26 or later. Apple’s submitting guidance and upcoming requirements pages both state the same requirement. That requirement narrows what any “without Xcode” pitch can mean. (developer.apple.com) A service can remove the need for developers to install or operate Xcode locally, but it cannot bypass Apple’s mandated build chain for App Store submission. Apple has also continued updating App Store Connect for Xcode 26.5 release candidates and TestFlight support, underscoring that the official tooling remains part of the upload path. ### What has Runable published that supports the broader claim? Runable’s website says its product can “build websites and apps,” and its documentation says the agent can write code, run commands and deliver projects from a private sandbox. The docs also say the system asks clarifying questions, then builds and iterates inside that environment. The company has published extensive material on agent behavior, sandbox execution and workflow modes, but the available docs reviewed here do not include a standalone page describing iOS code signing, provisioning, App Store Connect authentication or binary upload steps for native mobile apps. (developer.apple.com) That leaves the public demo and challenge as the main evidence for the mobile release claim at this stage. (runable.com) ### What problem is Runable trying to solve for developers? Runable’s materials present the product as a single agent that can build, create and ship work from one interface. In mobile development terms, the pitch is that developers would not need a Mac laptop configured with certificates, provisioning profiles and an up-to-date Xcode install just to cut a release, provided the hosted workflow handles those steps. (docs.runable.com) Apple’s current policy makes that especially relevant in 2026 because teams had to move to Xcode 26 by April 28 for App Store submissions. A hosted system that keeps pace with Apple’s SDK deadlines could reduce the maintenance burden on individual machines, though Runable has not publicly detailed how it manages those operational pieces. ### What comes next for verifying the claim? (docs.runable.com) May 14 is early for independent confirmation. Runable’s website, docs and status page show an active product and public documentation hub, but the company has not yet posted a primary technical explainer dedicated to the mobile build-and-submit flow reviewed here. The next concrete checkpoint is whether Runable publishes fuller documentation or third-party users reproduce the workflow through its public product. (developer.apple.com) For now, developers can find the company’s current materials on its website and docs, while Apple’s submission requirements remain the governing standard for any iOS release pipeline. (runable.com)