Lead scanner: require consent confirmation before first scan

Open
#163 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript
Domain
mobile

Research direction

Start by locating the scanner's first-load flow and the existing state used to remember sponsor confirmation. Verify how the expo opening day is represented, then ensure the confirmation is required on initial use and again on the first day the expo hall opens; done means sponsors cannot scan until they confirm consent requirements.

Written by the indexing model from the issue text.

Description

enhancement lead-retrieval

Add a confirmation prompt on first load of the scanner requiring sponsors to confirm they will only scan badges of attendees who have given permission. Should reset on the first day the expo hall opens so they have to confirm again.

Context: at least one attendee complained of a sponsor aggressively scanning badges without consent.

*Migrated from *psf/pycon-us-mobile#67

Dominant language
TypeScript
Stars
4
Forks
2
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PyCon/pycon-us-mobile

All issues in PyCon/pycon-us-mobile

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.