Park a Mobilebox phone and its installed apps, app data and logins stay for the next run while billing stops; resume starts Android again with all of it in place. A parked phone is free and a running one costs $0.01 a minute, so your agent can come back to the same signed-in app the next day, as long as the app’s own session is still valid.
Park keeps the phone’s stored state, not its running session. That changes what the agent should assume after resume.
What park keeps
Installed apps and their stored data remain. App logins remain to the extent that the app itself stores and accepts the session. Server-side expiration, revocation, and security checks still belong to the app; parking cannot guarantee that a third-party login will remain valid forever.
Running processes do not remain live. Apps start fresh after resume, like after a reboot. Do not expect an unsaved form, an in-memory navigation state, or an active socket to survive.
The lifecycle calls
# Shut down; retain app data.
curl --fail-with-body -X POST "$MSB/v1/phones/$ID/park" \
-H "Authorization: Bearer $MOBILESANDBOX_API_KEY"
# Resume and wait for readiness within this request's timeout.
curl --fail-with-body -X POST "$MSB/v1/phones/$ID/start?wait=ready" \
-H "Authorization: Bearer $MOBILESANDBOX_API_KEY"A wait call can return before boot is ready. Inspect status and poll the same phone; do not duplicate it. The quickstart includes a bounded polling example.
When delete is better
Delete removes the phone and its data. Use it for disposable tests, incompatible state, or a task whose data should not be retained. Park is appropriate when the next task should reuse the installed app and its stored session.
A parked phone keeps its state until you delete it, so a parked fleet still needs intentional ownership and cleanup, even though parked time is free. Keep names meaningful and decide who may resume each one. Two keys in the same project share access to the same phones; they do not give you separate test inventories.
Choose the right reset
Closing an app, uninstalling it, parking a phone and deleting a phone are different operations; none is a generic “reset”. A returning-user test that accidentally starts fresh loses the login you meant to exercise. A first-run test on a reused phone can skip onboarding and permissions without telling you. Name the state the test should cross, then pick the operation.
| Operation | Useful purpose | Do not assume |
|---|---|---|
| close_app then open_app | Restart an app process and verify saved state | App data was erased |
| Park then start | Stop compute while retaining the phone’s stored data | Unsaved buffers or processes survived |
| Uninstall then install | Recreate an app’s local installation state | Remote account records were removed |
| Delete then create | Start with a different disposable sandbox | External services forgot previous actions |
Mobilebox does not expose an arbitrary public shell or a general clear-app-data endpoint; the supported operations are in the API reference. Choose among those rather than inventing an ADB command in an agent prompt.
Verify persistence explicitly
Write a harmless value in your test app, confirm it is saved, park, resume, reopen the app, and read the value. That is stronger evidence than seeing the app icon remain installed.
An earlier recorded run did this on November 3, 2026, on a cloud Android 14 phone (arm64). It saved a release checklist in Fossify Notes, then terminated and reopened the app. It parked and resumed the phone, reopened the app, and found the checklist still there. This is a recording, not a live phone. It shows one app’s saved data. It does not cover unsaved state and is not a promise for every app. Details: how it was captured and captured operations and frame hashes.
If the app returns to sign-in, distinguish a lost local state from an expired remote session. Observe before retrying credentials or reinstalling. The phone lifecycle and the application’s session lifecycle are related, but they are not the same contract.
Clean up the external side too
Deleting the phone does not delete an order, message, uploaded file or account record already created on a remote service. Use staging accounts and unique harmless markers, and define separately how those remote records are removed. For a disposable test, delete the phone in finally and check that the delete succeeded. Workflow evaluation covers assertions that survive a fresh process.