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

Store bar location against user #18

Open
TomSeldon opened this issue Jul 20, 2017 · 0 comments
Open

Store bar location against user #18

TomSeldon opened this issue Jul 20, 2017 · 0 comments

Comments

@TomSeldon
Copy link
Owner

Currently a bar location has to be entered for each session. This would be better to change and store the user's choice so we do not have to ask them (or require they provide it) each time.

This involves:

  • Add DynamoDB resource the serverless.yml
  • On setting a bar location, store it (lots of docs available on this)
  • Possibly (probably) add in basic state machine for obtaining bar location, and moving on to available questions

Possible flows:

First time user

> Alexa, ask Tiny Rebel to suggest a drink

[check if user has provided bar location before]
[=no]

>> Should I check Cardiff or Newport?

> Cardiff

[store bar location as Cardiff]

>> You might like.... (etc.)

Returning user with set bar location

> Alexa, ask Tiny Rebel to suggest a drink

[check if user has provided bar location before]
[=yes]

>> You might like.... (etc.)

Returning user, overriding bar location in request

> Alexa, ask Tiny Rebel to suggest a drink in Newport

[check if user has provided bar location before]
[=yes (Cardiff)]

>> You might like.... (etc.)

etc.

Alexa SDK supports state flows and per-user attributes as would be required to implement this. See SDK docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant