# Mobile app bug report

Report ID: [pseudonymous identifier]
Short title: [observable problem, e.g. Saved note missing after restart]
App and exact build: [name/version/build]
Device model: [model]
OS version: [version]
Account state: [new/returning/signed out; never include credentials]
Permission state: [relevant allowed/denied permissions]
Network state: [offline/Wi-Fi/mobile; avoid precise location]

## Reproduction steps

1. [starting state and first action]
2. [next action]
3. [action where behavior differs]

Expected result: [what the app or task led you to expect]
Actual result: [what you actually observed]
Frequency: [e.g. two of three attempts; unknown is acceptable]
Workaround attempted: [what changed, if anything]
User impact: [lost work, blocked task, confusing message or visual issue]

## Optional evidence

Attach a redacted screenshot or short recording only when it helps explain the problem. Remove personal messages, names, tokens, email addresses and payment details. A written reproduction can be sufficient. Do not upload passwords, recovery codes, session cookies or production data.

Evidence reference: [safe attachment or report reference]
Approximate failure time: [only when necessary for authorized log investigation]

## Owner investigation

Observed again on: [build/device, or not reproduced]
Related findings: [report IDs]
Decision: [investigate / fix / defer / request clarification]
Reason: [brief evidence-based explanation]
Assigned role: [team role]
Retest build: [build]
Retest outcome: [resolved / remains / changed]

Record the problem without guessing its cause. "The save button returned an error" is an observation; "the database is broken" needs separate investigation. Keep a negative finding eligible for report approval when it contains the agreed evidence.

Template by RateMyApp: https://ratemyapp.io/resources/app-testing-templates/
Free to copy and adapt for your team's private testing. No attribution required.