Desktop bugs depend on things a phone report never needs: OS build, display setup, user rights, what else is running. This template adds those fields. For the basic structure of a report, see the general bug report template.
The template
Copy everything below and fill it in.
TITLE: [one line: what breaks, where]
APP
- App name and version / build number:
- Installed how (installer, package, portable, store):
- Fresh install or updated from version:
SYSTEM
- OS and version (Windows: edition + build, e.g. from winver; Mac: macOS version):
- Hardware (Mac: model/chip; PC: CPU, RAM, GPU if relevant):
- Displays (how many, resolution, scaling %, which one the app was on):
- User account type (standard / admin):
- Language and region settings:
- Security software, VPN or other tools running that may matter:
STEPS TO REPRODUCE
1.
2.
3.
EXPECTED RESULT:
ACTUAL RESULT:
HOW OFTEN: [always / sometimes (x of y tries) / once]
ATTACHMENTS
- Screenshot or screen recording:
- Log files or crash report (path or file):
- Does it happen after a restart of the app? Of the computer?
ANYTHING ELSE: [sleep/wake, plugged-in display, file on network drive, ...]
Filled example (Example, invented)
TITLE: Export to PDF freezes the window when a second monitor is attached
APP
- App name and version / build number: ExampleDraw 2.3.1 (build 2310)
- Installed how: installer
- Fresh install or updated from version: updated from 2.2.0
SYSTEM
- OS and version: Windows 11 Pro, build 22631
- Hardware: laptop, 16 GB RAM, integrated graphics
- Displays: 2; laptop 1920x1080 at 125%, external 2560x1440 at 100%; app on the external one
- User account type: standard
- Language and region settings: German (Germany)
- Security software: default system protection only
STEPS TO REPRODUCE
1. Open any project with at least one image.
2. Drag the window to the external monitor.
3. File > Export > PDF.
EXPECTED RESULT: Save dialog opens.
ACTUAL RESULT: Window stops responding for about 20 seconds, then the dialog opens off-screen.
HOW OFTEN: always (3 of 3 tries); does not happen with only the laptop display
ATTACHMENTS
- Screen recording: attached
- Log: app.log from the app's data folder, attached
- After restart of the app: yes, still happens
ANYTHING ELSE: started after the update to 2.3.1
Adapt it
- Remove the lines that do not apply to your app, but keep OS, build, steps and expected versus actual result.
- Add a field for anything your app depends on, such as a plugin version, a connected device or a license type.
- Tell testers where your app writes its logs and, if it has one, where crash reports are saved. For ideas on triaging what comes in, see how to read and prioritize crash reports.
- Offer a "send log" menu item in your app if you can; it removes the hardest field for non-technical testers.
What AppReviewX covers
AppReviewX accepts apps by store link from Google Play, the Apple App Store, the Mac App Store and the Microsoft Store. Windows and Mac apps must already be published in their store, and AppReviewX does not distribute builds or installers. Feedback is private and structured, one accepted feedback = one credit, and store ratings are voluntary, unpaid and never required. This page is general guidance.
Start free and get private feedback on your app.
Related: Windows and Mac app testing guide, Windows app testing checklist, Ratings for desktop apps.