Rental acceptance checklist
Real Android device rental: a project acceptance checklist
A practical guide from CloudPhoneBase, the service provider.
The short answer
Before renting a real Android phone, write down the specific app journey and hardware requirements your project must complete. For each requirement, record what you requested, what the service confirms, and how you will check it after activation. CloudPhoneBase offers physical phones hosted in the USA for $15 per month each; this worksheet covers an ordinary working setup, not an automated testing platform.
Start with one representative action, then work backwards through installation, account access, browser handoffs, and required phone inputs. Physical hardware alone does not establish a particular model, feature, network identity, or app result.
Copy the worksheet into your project record. Leave Confirmed open until the detail is answered or demonstrated, then use the same task to check the hosted phone after activation.
Take the worksheet from requirements to an order decision
Use the physical phone rental allocation guide to decide how many project contexts need real hardware. Then compare the US-hosted physical Android service and its per-device monthly price after the requested app and input details are confirmed.
Define one task that would make the rental useful
Describe the outcome: open the project app with the intended account, perform the main action, and follow any required browser handoff. This is a proposed task, not a claim that CloudPhoneBase has tested that app.
Record the app source, current account requirements, and exact action. Add required notifications, uploads, files, or inputs. Installation alone does not show that the task can be completed.
- Name the outcome and responsible contact.
- Describe the intended installation and sign-in path.
- Specify the main action and browser step.
- List essential inputs or configuration details.
Use a requested-versus-confirmed worksheet
Keep Requested and Confirmed separate. The example rows are questions, not service promises. Date each confirmed answer, mark open questions, and record the observed result after activation.
If a detail remains open before payment, decide whether the project can proceed without it.
| Check | Requested | Confirmed | Acceptance action |
|---|---|---|---|
| App installation | App and installation source. | Dated provider answer. | Open the app. |
| Account access | Sign-in and account checks. | Confirmed access path. | Sign in with the intended account. |
| Main action | Exact task and expected result. | Confirmed task details. | Perform and record the result. |
| Web handoff | Required browser link or page. | Confirmed handoff details. | Follow the link end to end. |
| Configuration | Essential region or device setting. | Confirmed available setting. | Check it during setup. |
| Hardware input | Required camera, NFC, sensor, or other input. | Confirmed input access. | Use it in the task. |
| Activation and access | Required access and timing. | Agreed details before payment. | Open the active phone. |
Ask about the exact hardware inputs
CloudPhoneBase hosts real Android hardware in the USA. Confirm the exact model, Android version, camera path, NFC function, or other input only when your task needs it. Record the answer before making it an acceptance criterion.
US hosting does not itself establish a phone number, SIM service, or particular IP type. Ask support if one is essential and record the answer.
This checklist covers an ordinary app workflow. The service is not an automated testing platform, API, scripted runner, or bypass for app account checks.
- Describe the input as part of a specific action.
- Request configuration details that affect the task.
- Date the answer and record the result after activation.
Check quantity, price, and activation
Each USA-hosted physical Android phone costs $15 per month. Checkout supports one to 50; select the count needed for real-hardware projects. The table below uses the current configured price.
Confirm availability, activation timing, and access before payment. Checkout uses fixed crypto addresses; payment review and activation are manual.
| Physical phones | Price per phone / month | Monthly total |
|---|---|---|
| 1 | $15.00 | $15.00 |
| 3 | $15.00 | $45.00 |
| 5 | $15.00 | $75.00 |
Record the result and decide what to do next
After activation, run the task in order. Date the result and identify the exact step that stopped. One successful action does not establish every account, version, or feature.
For a blocked task, tell support the project ID, app, account stage without secrets, required action, and result. Repeat the check after a material app change.
Common questions
Does a real phone guarantee my app will work?
No app result follows from the hardware description alone. Check installation, account access, and the main action after activation.
Which hardware details should I ask about?
Ask about the model, Android version, setting, or input only when your task requires it.
Is this an automated Android testing platform?
No. The offer is a hosted physical phone for an ordinary app workflow, without promised test automation or API.
What is the monthly price?
Each phone costs $15 monthly. Checkout accepts one to 50, with availability and activation details confirmed before payment.
What should I do after activation?
Run the written task, record the result, and tell support the exact failing stage if needed.