Round 2 - Address feedback from certification team / beta users

Certification Team:

_FUNCTEST_FAILED Failure below will prevent this version from publishing to Live Adding one requirement:

The skill does not exit when users say “cancel”. Rather, it responds with something like "OneBusAway could not locate a OneBusAway region near cancel..." Please see test case 4.13 from our Submission Checklist for guidance on skill exiting.

Consensus with Amazon was that this is an Amazon issue, not an OBA Alexa issue

Recommendations:

The third example phrase should not contain the wake word if it is not in a one-shot format. The example phrase should be changed to one of the following:

-> Alexa, tell OneBusAway to set my stop to 6497

Set my stop to 6497

Issue with the store listing - I fixed this.

After setting a stop number, the skill responds with "Ok, your stop number is 75414 in the Puget Sound region. Great. I am ready to tell you about the next bus." and the stream closes. Ideally, the skill would go right in to telling the next bus information or prompt users to ask for this information while leaving the stream open so the skill would not have to be relaunched.

Ticketed at https://github.com/OneBusAway/onebusaway-alexa/issues/68.

User Feedback (raw):

· Lastly, after I set up, I didn’t know what to do. I can’t remember what the skills said. Something like “now your location is set.” and then that was it. I wanted to hear something like, “Now your location is set. To find out bus schedule information, just say “Alexa, open OneBusAway” or whatever other common terms will work.

Ticketed at https://github.com/OneBusAway/onebusaway-alexa/issues/68.

· My bus stop (#700) is one of the busier ones and the list is daunting – it is possible to add bus filters (only 545 and 268 for example)?

Ticketed at https://github.com/OneBusAway/onebusaway-alexa/issues/67

· Wondering if the skill could/should support other types of utterances, not just the no-intent ones. For example, I’d like to ask “ask OneBusAway when is the next 8 bus coming” so that it doesn’t give me the times of arrivals for other lines I don’t use. My stop only has two bus lines, but I think this could be very useful for users who frequent a bus stop with multiple bus lines.

Ticketed at https://github.com/OneBusAway/onebusaway-alexa/issues/67

· set up did not go smoothly as the Android app for OBA doesn’t display bus stop numbers unlike what’s shown on their github page.

Updated wiki for finding your stop to say that you need to download the latest OBA Android beta to see the stop numbers in the app - https://github.com/OneBusAway/onebusaway-alexa/wiki/Finding-your-stop-number#in-your-onebusaway-mobile-app.

· After giving the city and stop number, Alexa said that she was ready to help but then the session ended. I was expecting she would either let me ask “when is the next bus arriving”, or that she would provide some instructions on how to ask for information in the future, like the types of info devs provide for a Help query, like “To know when the next bus is arriving, just say “open OneBusAway”.

Ticketed at https://github.com/OneBusAway/onebusaway-alexa/issues/68.

· These utterances did not work: “Alexa, ask OneBusAway when is the next bus”, ““Alexa, ask OneBusAway when is the next bus coming”. However this one worked… but maybe she just heard OneBusAway correctly: “Alexa, ask OneBusAway when is the next bus arriving”. Does it just support no intent requests?

Ticketed at https://github.com/OneBusAway/onebusaway-alexa/issues/69.

· When I did get Alexa to report my bus data, the result was not well-optimized for speech. There was one bus line that had four upcoming busses, and she repeated the name of the line with every arrival. It would have been a better experience if she had said something like “The next bus on Route 45 university district east green lake is arriving in 2 minutes. Route 45 will arrive again in 10 minutes, 18 minutes, and in 32 minutes based on the schedule."

Ticketed at https://github.com/OneBusAway/onebusaway-alexa/issues/70.

· I rely on buses quite a lot, and as a result I live within an easy walk of three bus stops. I regularly take one of those stops in both directions, which makes four stop numbers I regularly use. To be really useful, I’d need to be able to name those four stops, or, ideally, tell it all the stops I care about and ask by route. So, for example: “Alexa, ask OneBusAway when the next E Line bus is coming.” OBA should be able to check the four stops on my list and realize that the E line stops at exactly one of them, then give me E Line arrival times on that route.

Ticketed at https://github.com/OneBusAway/onebusaway-alexa/issues/71

OneBusAway / onebusaway-alexa

Round 2 - Address feedback from certification team / beta users #65