Difficulty: Intermediate
Type: UI/UX
Background
GuildPass Mobile provides QR code scanning for Guild Pass verification. Event entry often depends on scanning being quick and reliable, yet scanner failures caused by poor lighting, invalid QR codes, camera permissions, or temporary network delays currently provide limited guidance to users.
Improving the verification experience will reduce failed scans and make the application more reliable during live events.
Problem
The scanner provides little feedback about why verification failed or how users can recover. In many cases users must manually retry the process without understanding whether the issue was caused by the camera, connectivity, or the QR code itself.
Expected outcome
Create a more resilient scanning experience that clearly communicates scanner status, verification progress, and failure reasons while minimizing unnecessary user interaction.
Suggested implementation
- Categorize scanner failures (camera unavailable, permission denied, unreadable QR code, unsupported format, network timeout, verification failure).
- Display contextual error messages with recovery guidance.
- Add a verification loading state while server validation is in progress.
- Automatically reset the scanner after recoverable failures instead of requiring users to reopen the scanning screen.
- Improve camera permission handling and provide instructions when access has been permanently denied.
- Add visual success and failure animations to improve user confidence during verification.
Acceptance criteria
Likely affected files/directories
src/features/scanner/, src/components/, src/screens/, src/navigation/, src/hooks/
Difficulty: Intermediate
Type: UI/UX
Background
GuildPass Mobile provides QR code scanning for Guild Pass verification. Event entry often depends on scanning being quick and reliable, yet scanner failures caused by poor lighting, invalid QR codes, camera permissions, or temporary network delays currently provide limited guidance to users.
Improving the verification experience will reduce failed scans and make the application more reliable during live events.
Problem
The scanner provides little feedback about why verification failed or how users can recover. In many cases users must manually retry the process without understanding whether the issue was caused by the camera, connectivity, or the QR code itself.
Expected outcome
Create a more resilient scanning experience that clearly communicates scanner status, verification progress, and failure reasons while minimizing unnecessary user interaction.
Suggested implementation
Acceptance criteria
Likely affected files/directories
src/features/scanner/,src/components/,src/screens/,src/navigation/,src/hooks/