The gatekeeping intensifies
Apple is systematically blocking or removing code-execution apps from the App Store under Guideline 2.5.2. Anything, a vibe-coding app that lets users build native iOS apps on-device, has been removed twice since March 2024. Replit and Vibecode face similar blocks. The enforcement centers on Apple's concern that users could download malicious code or build harmful apps and then claim they passed wiki:app-review.
Anything's co-founder, Dhruv Amin, explained that even when the company got on calls with Apple and rewrote the app four times to comply, the fundamental issue remained: Apple does not want apps marketed as "app makers" on iOS. The company is now pivoting to desktop companion apps and exploring iMessage-based building experiences. Android is on the table as a more open alternative.
This is not a marginal enforcement action. It directly impacts the emerging category of AI-powered code-generation tools that promise to let users build apps through natural language prompts. The timing is particularly sharp: the same quarter Apple blocked these apps, the company reportedly saw an 84% jump in app submissions driven by AI-powered coding tools. The human-led review process is under strain from exactly the kind of automation Apple is blocking at the user level.
Meanwhile, the tooling arms race accelerates
While Apple locks down on-device code execution, the rest of the ecosystem is doubling down on AI-assisted development. Google previewed Gemini Nano 4 for Android AICore, delivering advanced on-device AI capabilities with a developer preview now available. Apple researchers published details of SQUIRE, an experimental AI tool designed to help developers explore and refine interface prototypes with more control than typical vibe-coding systems offer.
Google I/O 2026 in May will feature sessions on Android 17's "Adaptive Everywhere" reality, Jetpack Compose UI improvements across foldables and desktops, and agentic automation features that let users "get more done faster." Firebase is positioning itself as an "agent-native platform" with integrations to AI Studio and Antigravity for full-stack vibe-coding. The messaging is clear: AI-powered app creation is the future, as long as it happens in sanctioned environments.
The Android Emulator now supports zero-configuration peer-to-peer connectivity across multiple virtual devices, eliminating the manual port forwarding complexity that previously made wiki:ab-testing multi-device interactions painful. This is critical infrastructure for testing the kind of cross-form-factor experiences Google is promoting.
The indie developer playbook still works
Amid the platform policy chaos and AI hype, RocketSim's trajectory offers a stabilizing counterpoint. The Xcode simulator tool grew to nearly $100K ARR entirely through organic growth by solving one problem ruthlessly well: giving developers time back. The pitch is simple—five minutes saved per day, multiplied across a team, multiplied across a year. That ROI is undeniable.
RocketSim's creator, Antoine van der Lee, maintained a public roadmap and let users vote on features. When the top-voted network monitor shipped, daily active trials jumped from 40 to 120. The lesson is that building exactly what users ask for does not just retain your audience—it re-engages churned users who left because a specific capability was missing.
The case also illustrates the danger of going full-time indie without discipline. When van der Lee finally matched his salary and quit his job, productivity initially dropped. The extreme time scarcity of nights-and-weekends work had forced ruthless prioritization. With five open days a week, that discipline evaporated. He had to consciously rebuild strict habits to recover output.
The friction point for ASO practitioners
For app marketers, the collision between platform policy and AI tooling creates immediate challenges. Screenshot and preview assets remain manual, time-intensive work. Apple Frames 4, a shortcut that frames screenshots with official device bezels, just shipped a major update that reduces complexity from 800+ steps to ~300, adds frame color customization, and introduces proportional scaling when merging screenshots from different devices. A new CLI version integrates directly into Terminal workflows.
This is critical infrastructure for anyone doing wiki:visual-assets work at scale. The ability to script screenshot generation and framing into automated pipelines means asset production can keep pace with the accelerating app submission velocity that AI coding is driving. If human review is struggling with 84% more submissions, human asset creation will bottleneck even faster.
Apple also released beta versions 26.5 across all platforms along with Xcode 26.5 beta. The window for testing compatibility and adopting new SDK features before public release is narrowing. Developers who wait until general availability to test will face compressed timelines to fix issues before user-facing releases.
What this means for practitioners
The platforms are not aligned on where app creation happens. Apple wants it off-device and tightly controlled. Google is building on-device AI into the OS and promoting agent-native workflows. Both are investing heavily in AI-assisted development tools for sanctioned environments.
For app marketers, the ASO implications are indirect but real. If submission velocity continues rising, store algorithms will have more data to work with for ranking factors and search visibility. Apps built through AI pipelines may converge on similar metadata patterns, making differentiation harder. The bottleneck shifts from building the app to positioning it correctly in an increasingly crowded store.
The RocketSim lesson applies broadly: solve time constraints, and the market will pay. Whether that means automating screenshot generation, streamlining localization workflows, or building tools that let non-technical teams update metadata without engineering dependencies, the value is in velocity.
Apple's enforcement of code-execution policies is not going away. Developers building tools in this space need alternative distribution strategies now—desktop apps, web-based builders with export flows, or Android-first approaches. The App Store is not a neutral platform for development tools anymore.