Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proximate Location for Symptom Check-Up #1941

Open
2 tasks done
brunobowden opened this issue Feb 13, 2021 · 4 comments
Open
2 tasks done

Proximate Location for Symptom Check-Up #1941

brunobowden opened this issue Feb 13, 2021 · 4 comments
Assignees
Labels
client-ui Client user interface f:symptom-tracker Symptom tracking flow. Product definition, design, content, and assets are a WIP. source:team From active team members

Comments

@brunobowden
Copy link
Collaborator

brunobowden commented Feb 13, 2021

Summary

The Symptom Check-Up tool should ask the user for their proximate location. This could be a zip code, regional name or local equivalent. This is to tailor the advice help with tracking the efficacy of the app. This data should only be reported to the server with user permission.

Desired Solution

Different countries may need different options, e.g. zip code, UK outward code or city name. The former could be implemented with regex validation, while the latter could be done with Google Maps Autocomplete API. There is a Flutter SDK for Google Maps, authored by Google, but unclear if that also covers the autocomplete API: https://pub.dev/packages/google_maps_flutter. Potentially this might require building out a Flutter library that abstracts the Places SDK on iOS and Android.... but let's have a discussion around that as it could be a lot more work that I'm more hesitant about doing.

The proximate location information that should be reusable in other parts of the app at a later point. It should be configurable to allow someone to skip entering this information. Then there's another question about UI for reporting permission. If reported to the server, this should be done with the new Firestore Native implementation.

Checklist:

@brunobowden brunobowden added client-ui Client user interface f:symptom-tracker Symptom tracking flow. Product definition, design, content, and assets are a WIP. source:team From active team members labels Feb 13, 2021
@brunobowden
Copy link
Collaborator Author

@bezfeng - are you good for this as a starting project?

@bezfeng
Copy link
Contributor

bezfeng commented Feb 13, 2021

@brunobowden - absolutely, happy to take this on!

@bezfeng bezfeng self-assigned this Feb 13, 2021
@brunobowden
Copy link
Collaborator Author

@bezfeng - thanks for your help. I'll work on getting #1935 landed, which will make this work easier.

@shawndimantha
Copy link

Initial PRD to align on implementation for reference: https://docs.google.com/document/d/1g3YgDxKV9ribHW2aARl5-mrE88d5OnnMFC5Sq7O9u10/edit#

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client-ui Client user interface f:symptom-tracker Symptom tracking flow. Product definition, design, content, and assets are a WIP. source:team From active team members
Projects
None yet
Development

No branches or pull requests

3 participants