Using Emutize online
The dashboard: your app library, live sessions, and the player.
The app library
Every APK you upload becomes a library entry with its name, package id, size, and upload date. Launch as many sessions of the same app as capacity allows; delete removes the APK and its entry.
Uploading a new build of the same app? Upload it as a new entry (or delete and re-upload) - sessions always install exactly the APK in the library.
Sessions
The Active sessions table shows what's running: app, device, backend, and age. Open player rejoins a session; Stop ends it. A session belongs to whoever launched it - staff accounts see everyone's.
| Property | Value |
|---|---|
| Boot time | Seconds (a fresh container per session) |
| Idle timeout | 15 minutes without anyone viewing - then auto-wiped |
| Isolation | One container per session, destroyed on release |
| State | Nothing survives the session - by design |
The player
Click to tap; press-drag to swipe; the toolbar gives Back / Home / Recents; the text box types into the focused field. The fps counter shows live stream rate. If the page says Session ended, the device was reclaimed - launch a new one from the library.
Sharing a session
For login-free sharing (a teammate, a client, an iframe), create the session via the
API and hand out its embed_url - a capability link that dies
with the session. Dashboard player pages, by contrast, require your login.