OpenCode Mobile vs OpenCode Web on Android
Both interfaces can reach an OpenCode server from a phone. Choose based on the workflow, not on the assumption that an installed app is automatically better.
| Need | OpenCode Mobile | OpenCode Web |
|---|---|---|
| Installation | Android beta or APK | No client installation |
| Updates | Play beta or new APK | Updated with the server |
| Session monitoring | Native mobile workflow | Browser workflow |
| Voice follow-ups | Dictation and foreground conversation mode | Depends on browser UI |
| Task notifications | Supported Android completion alerts | Depends on browser/background behavior |
| Focused files and terminal | Native compact surfaces | Browser-provided surfaces |
| Server requirement | OpenCode server/API | opencode web server |
| Remote route | LAN, VPN, tunnel, proxy, SSH forward | Same network choices |
Choose OpenCode Mobile when
- you regularly check or redirect sessions away from your desk;
- native navigation, voice input, or Android notifications matter;
- you want a focused control surface instead of a complete desktop-style UI;
- you are comfortable installing a community-built beta.
Choose OpenCode Web when
- you want zero client installation;
- the browser interface already fits your workflow;
- you use several device platforms and want one interface;
- you prefer the server release to control UI updates.
They can coexist
Use opencode web when you want the browser UI and API from the same server. Depending on the deployment, the API may be at the origin or below a prefix such as /api. OpenCode Mobile must receive the API base, not merely a URL that returns an HTML page.
Regardless of the client, do not expose an unauthenticated server publicly. Use the remote-access overview and security guide.
To try the native client, follow the OpenCode Android app setup. If an existing deployment returns HTML or 404 responses, use the troubleshooting checklist.