Experimental functionality

Android project hosting

warp_android_build reads an external Cargo project, generates a disposable cargo-apk wrapper, mirrors the project source tree, and creates a NativeActivity entry point that calls the project’s existing renderer through warp_core::run_android. The Android host owns the window, wgpu device/queue, surface lifecycle, touch delivery, egui delivery, storage root, and presentation.

The source validation note describes the production path as:

Warp project → Android host → wgpu → Vulkan

This is useful evidence of a real target path, not a claim of a polished public mobile SDK. Projects still own their gameplay and UI semantics.

Browser and external tools

The workspace contains a wasm/browser path and an optional CEF host. The editor also catalogues integrations such as Shader, 3D Renderer, Storyboard, ComfyUI, Voicebox, VS Code, and local-agent tooling. These are source-visible features with target gates or external dependencies; they should not be marketed as one uniformly supported product surface.