The hosted preview stays out of your release build.
App Store Guideline 2.5.2 addresses apps that download, install, or execute code that changes functionality. Buildy's editor and hosted preview run separately from the project you compile. This removes that specific platform-preview pattern; it does not guarantee approval, because Apple reviews every final app and its behavior.
What Guideline 2.5.2 covers.
“Apps should be self-contained in their bundles, and may not read or write data outside the designated container area, nor may they download, install, or execute code which introduces or changes features or functionality of the app, including other apps.”
The relevant risk is behavior in the submitted app, not the name of the tool used to create it. A problematic pattern has three parts:
- A distributed app receives new executable code after review.
- That code changes features or functionality available to the user.
- A runtime inside the app executes the downloaded code.
A self-contained build avoids that pattern, but App Review also considers completeness, privacy, payments, content, minimum functionality, and the app's own dependencies. Architecture can reduce a known risk; it cannot decide the review outcome.
Preview infrastructure and release output are separate.
The Buildy editor and hosted preview are development services. The release project is a separate output that you review and compile for distribution.
On buildy.me
Buildy bundles the current project for a sandboxed browser preview. That hosted preview is used for iteration and device testing.
Export
Paid plans can export the project for the selected target: Expo, Kotlin, SwiftUI, or React with Vite. Buildy's preview service is not added to that source.
Signed build
The build process packages the project into a signed Android or iOS artifact. Final compliance still depends on the code, dependencies, content, and runtime behavior of that app.
This separation is an architectural control, not an approval guarantee. Review the generated and edited project before every submission, just as you would with code produced by any development tool.
Review what is specific to your app.
- Inspect dependencies and remove any runtime code loader you do not need.
- Test the signed build on physical devices, not only in the hosted preview.
- Complete privacy disclosures, permissions, payments, and review notes.
- Confirm that metadata and screenshots match the functionality submitted.
Apple's guidelines are living requirements and can change. Read the current App Review Guidelines.
Build with a clear separation between preview and release.
Use the hosted preview to iterate, then inspect and compile the project you intend to distribute.