Lead scanning - Request to require sponsors confirm they will only scan badges with permission
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- mobile-dev
Research direction
Start by locating the lead scanning app workflow and the screen shown before a sponsor scans a badge. Trace how first-load or persisted confirmation state is stored, then determine how the app identifies the first expo-hall day. Done means the permission confirmation blocks scanning initially and is required again on the specified reset date.
Written by the indexing model from the issue text.
Description
I'm submitting a ... (check one with "x")
[ ] bug report
[X] feature request
[ ] support request
Request
I'd like to add an extra confirmation that sponsors promise to only scan badges from attendees who consent the in lead scanning app workflow
Desired result
On a user's first load of the app scanner before they can continue on to scan a badge, require them to confirm they will only scan badges of attendees who have given them permission to do so. The app should also reset on the first day the expo hall opens (in 2024, this is May 16), so they have to do it again.
Why
At least one person complained of a sponsor aggressively scanning. While attendees already have a way to see who scanned them & report if they didn't consent, it doesn't hurt to make sure anyone using our lead scanning app is reminded of appropriate behavior.
Thank you!
@ewdurbin
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PyCon/pycon-us-mobile
-
Selecting an open space from the schedule does not have a `back` option to return to the schedule. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
PyCon/pycon-us-mobile#279 · 1 comment ·
-
bug speakers ui/ux
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
PyCon/pycon-us-mobile#157 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
PyCon/pycon-us-mobile#313 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
PyCon/pycon-us-mobile#312 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
PyCon/pycon-us-mobile#311 · 3 comments ·
All issues in PyCon/pycon-us-mobile
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
fullcalendar/fullcalendar#8106 ·