Today, trying OpenPhone requires a full AOSP build (64GB RAM, ~700GB disk). Anyone without that hardware bar can't even boot the OS locally. This is the single biggest onboarding friction the project faces.
Ask
Publish sdk-repo-*-system-images.zip (both arm64 and x86_64) as assets on GitHub Releases, alongside SHA256 checksums that scripts/verify-prebuilt-emulator-image.sh (already exists) can consume.
Impact
docs/quickstart.md becomes truly "quick" (minutes, not hours).- Contributor onboarding for the assistant, docs, integrations, and schemas becomes practical without a build host.
- Bug reports get a common reproducible baseline.
Related: existing run-emulator-smoke.sh proves the emulator flow works end-to-end; this issue is about making the artifact publicly consumable.
Size: M
Today, trying OpenPhone requires a full AOSP build (64GB RAM, ~700GB disk). Anyone without that hardware bar can't even boot the OS locally. This is the single biggest onboarding friction the project faces.
Ask
Publish
sdk-repo-*-system-images.zip(botharm64andx86_64) as assets on GitHub Releases, alongside SHA256 checksums thatscripts/verify-prebuilt-emulator-image.sh(already exists) can consume.Impact
docs/quickstart.mdbecomes truly "quick" (minutes, not hours).Related: existing
run-emulator-smoke.shproves the emulator flow works end-to-end; this issue is about making the artifact publicly consumable.Size: M