# Web or mobile: task decision worksheet

Task:
User role:
Where it happens:
Frequency:
Device / OS / browser actually used:

## Requirements to prove

For each requirement, record must-have / optional, a test device, expected result, observed result and evidence.

- Link-based access and occasional use
- Large-screen review and comparison
- Camera / file capture
- Work with an interrupted or absent connection
- Delayed upload and recovery after reconnecting
- Notifications on the specific target devices
- Accessibility with the intended input method
- Account identity and permissions
- Store distribution, review and update responsibilities

Do not mark a capability supported because a framework advertises it. Check the actual target platform and workflow.

## One complete example

Start condition:
Inputs:
Saved record:
Visible confirmation:
Next person's action:
Interrupted-request behavior:
Repeated-request behavior:
Permission-denied behavior:

## First release decision

Chosen surface:
Requirement that determines the choice:
Requirement still unproven:
Smallest complete workflow to validate:
Who approves the result:
What would justify adding a second surface:

araNET Studio — https://www.aranetsolutions.com/blog/web-app-mobile-app-or-both