Native Android with Kotlin/Java, Gradle, tests and APKs — alongside Web/PWA development, MCP and governed workspace files. Every workflow is permission-gated.
Rollout is owner-canary only. This is product documentation, not a public account invitation, device control console or public developer API reference.
Developer workflows
01 / NATIVE ANDROID
Native Android app development
Work with Android Studio-compatible projects, Kotlin/Java, manifests and resources. Build, test and package APKs only when an authorized JDK/Android SDK/Gradle provider is available.
SAMPLE PROMPT (NOT EXECUTED)@Velyga Inspect my authorized native Android project, Kotlin/Java, Gradle and AndroidManifest. Check toolchain readiness; do not build yet.
Use the verified rootless Web/PWA starter, develop HTML/CSS/JavaScript and preview the result. Public sharing is tied to device availability and Preview policy.
SAMPLE PROMPT (NOT EXECUTED)@Velyga Inspect my authorized website project and suggest a safe local Preview. Do not publish it yet.
Use Chrome and chatgpt.com for the illustrated custom MCP plugin setup. Registration and OAuth must complete before a client can discover permitted tools.
SAMPLE PROMPT (NOT EXECUTED)@Velyga Check the status of my authorized Android device.
The browser only renders sample prompts. Android verifies all requested work; an MCP URL alone does not grant permissions. MCP setup has its own Connect guide
Check availability before you start
Account registration and public APK release are still restricted. Device commands remain governed by Android-local authority.