Task and environment
- What does the user need to finish, and where?
- Which devices and input methods matter?
- What interruptions or connection problems are likely?
Planning resources
Decide what “works on mobile” needs to mean.
Use these questions for your own notes. This page does not collect answers or upload project files.
Device and distribution needs
- Which specific capability is required?
- Could the task be completed in a suitable mobile website?
- Who owns distribution accounts and future releases?
Offline behavior
In a fictional field checklist, distinguish a locally saved draft from a record accepted by the server. Decide what the user sees before reconnection, how a failed upload is handled and what happens if someone else changed the record.
Accounts and notifications
Define permissions, session expiry and the destination of a notification. Consider what information is suitable on a lock screen and how the user reaches the current record after tapping it.
A useful first release
Choose one complete flow with known test devices and clear saved or failed states. Include backend and support ownership. Platform availability and release requirements need review for the actual product.