1. Understand the task and environment.
Identify users, target devices, connection conditions and the existing systems involved. Define the useful result rather than starting with a list of screens.
Process
Test the difficult device behavior early.
A small checked example can clarify the product approach before a large feature scope is agreed.
2. Check the uncertain capability.
Use a focused prototype where device access, offline behavior or distribution needs affect the choice. Record limitations and supported conditions.
3. Build one complete flow.
Connect interface, validation, backend storage and confirmation. Preserve existing records and define a controlled testing environment.
4. Test interruptions and failures.
Try an expired session, denied permission, lost connection and repeated action where relevant. Confirm that pending work and the stored result remain distinguishable.
5. Prepare release and ownership.
Review the target platform's current requirements, agreed device tests and support responsibilities. Account, release and maintenance ownership should be explicit.