How Buildy separates preview and release output

A precise look at Buildy's hosted preview boundary, App Store Guideline 2.5.2, and the checks that still belong to every submitted app.

App Store Review Guideline 2.5.2 addresses apps that download, install, or execute code that changes their functionality after review. The relevant question is what the submitted app does at runtime.

The Buildy boundary

Buildy's editor compiles the current project for a sandboxed, hosted browser preview. That preview helps with iteration and can be shared as a PWA for testing. It is separate from the project used to create a signed Android or iOS build.

What this separation reduces

Buildy's preview service is not inserted into the release project by default. This avoids one pattern in which a distributed builder app receives and executes generated code. It is an architectural control, not an App Store approval guarantee.

What still needs review

Before submission, inspect the generated and edited code, dependencies, permissions, privacy disclosures, payments, content, and metadata. Test the signed artifact on physical devices and follow the current Apple guidance for the app you are actually distributing.