nnguyen682 / CECS491ATeam4

Team4Alexa
1 stars 3 forks source link

Implement Device Address API #42

Open AnthonySMyers opened 6 years ago

AnthonySMyers commented 6 years ago

Device Address API will be able to give location-based recommendations to the user. For the scope of this project this may include clinics that specialize in depression therapy.

jespinoza17 commented 6 years ago

https://www.youtube.com/watch?v=sZ7GCMqhjv0

jespinoza17 commented 6 years ago

https://github.com/alexa/skill-sample-node-device-address-api

jespinoza17 commented 6 years ago

The link above is a sample skill with that utilizes the device address api. Hopefully it is more straightforward then the video. I will be reviewing this code to see how we can implement the api in our own skill.

AnthonySMyers commented 6 years ago

This link includes a tutorial on how to implement the Device Address API. It covers the coding and practices for user consent handling, along with user address pulling.

https://developer.amazon.com/zh/blogs/alexa/post/0c975fc7-17dd-4f5c-8343-a37024b66c99/alexa-skill-recipe-using-the-device-address-api-to-request-information

jespinoza17 commented 6 years ago

Below is a link to an Alexa skill that utilizes the google directions api. Note: you will need to make a google developer account in order to get a google maps API key. https://github.com/luigidc25/alexa-google-directions

AnthonySMyers commented 6 years ago

This link has an article describing the requirements and process for connecting an Alexa Skill to the Google Places API. He combines the AWS Device Address API with the Google Places API using a python-based library to manage string values for location suggestions.

https://blog.njsnet.co/bar-finder-alexa-skill/

jespinoza17 commented 6 years ago

Google places API key: AIzaSyAbIuKzBw8Xyh17gp_2QQaynZVnIZ_Bng0

AnthonySMyers commented 6 years ago

As of right now, we will put a hold on this task. We will have enhanced versions of the current features for user testing, which will not include location references and suggestions. After conducting more research on the Device Address API, Device Location API, and Google Places API we have found this feature to be far to difficult to gain any application quality benefits from. Device Address and Location APIs only give information regarding the user's address based off of account information and device locations. These APIs do not handle relative location searches. The Google Places API would handle location searches, but it had a limited list of locations it could identify. After searching the Google Places API list of locations it mostly consisted of chain stores (Starbucks, Target, etc.) as opposed to clinics and help centers that would be beneficial to the users of Good Vibes. For this reason we put this task on hold.