Frontend UX/UI considerations

[jkdru]

Study both mobile and desktop versions to identify what is useful/theft-worthy to adapt vs. improveable:

SAMHSA's Find Treatment Locator

1. Go to https://findtreatment.samhsa.gov/locator
2. Type "Philadelphia, PA, USA" in the search bar
3. Experiment with 2 location options:
   [ ] County (just Philadelphia: this limit made sense when we were focused on serving HFP/PDPH)
   [ ] Distance: 15 mi (maybe more practical for referrals than limiting to just city boundaries)
4. Uncheck "SU & MH" and check "SU" [substance use], then click the dropdown carat next to "SU" to explore analogs to our mobile X-4 mockup
5. Check "Buprenorphine Practitioners" to add their dots to the map and see listings

Screenshots for desktop:
Map+filter menus: Philadelphia county, SU
Map with SU + BP dots: Philadelphia county
Map with SU + BP: within 15 miles of Philly center (19102)

• Study mobile layouts & functionality

MOUD (Medications for Opioid Use Disorder) Locator, Washington Recovery Help Line
http://www.warecoveryhelpline.org/moud-locator/

Three theft-worthy features in opening desktop version of WA MOUD:

• Adapt CONTENT of their opening filters for ours? (two desktop screenshots below)
• Emulate more INVITING/RELATABLE address of their opening filters (vs. SAMHSA's more detached approach)?

"I'm seeking the following medication..." | "I can pay with..." | etc.
"I am also interested in the following services..."

• Offer language translation options? If simple, include 1-3 options for Philly (Spanish, others TBD), otherwise just include on future wishlist

• Study mobile layouts & functionality