Just tried to send the form to apply [1] but it seems to be broken. It says please complete all required fields despite that I completed all of them (double checked)
Start building Actions on Google
51–60 of 66 posts
Re: Start building Actions on Google
#52API.AI is really great but I really don't like this UX. From using and developing for the Amazon Echo for the last year or so this "Conversational" setup just sounds super unnatural. You want bus times: Amazon: "Alexa, ask [nextbus] [for the next bus]" Google: "Hey Google, let me talk to [nextbus] when is the next bus?" Perfect: "[keyword], when is the next bus?" (context set in advance for the specific bus you care…
IIRC, the perfect examples where you neither say "Alexa" or "Hey Google" aren't going to happen any time soon - those recognition phrases are hard-coded for performance reasons, and adding custom ones will be difficult.
Performance may be a small part of it, but it's more about branding. The trigger word is the brand, the functionality is the product.
Re: Start building Actions on Google
#53I was looking at the page earlier today, wondering when it's being launched. Great timing as my days at work are over for the rest of the year. I'm working on a public-transport chatbot in South Africa, planning on making it available on Twitter, Facebook, and Allo (though less users here). Going to be a fun December and January!
good luck! do you have a progress blog or something?
Our website is movinggauteng.co.za, I'll blog about progress on our blog over the weeks
Re: Start building Actions on Google
#54Pretty neat, but from a user's perspective I'm a little disappointed that the current implementation seems to require me to explicitly tell Google what app I want to interact with. I'd rather be able to just ask Google "Find me a movie ticket for Rogue One on Thursday" and have it be able to infer that I want to use the movie tickets app installed on my phone, than for me to have to explicitly say "Let me talk to Fan…
The problem with protocol activation is that there are a million different endpoints and you either * Keep a list of every single one that apps can opt into. This is how you end up with "midsized_sedan_carwashing" in an enum list. It's a developer drain for Google/Microsoft/Amazon and creates "wait for the next release for 'largetruck_carwashing' so you can release your app". * Let apps run wild and claim any protoco…
Yup! we are thinking along these lines. Please see the baby step on discovery that you can use today called "Deep Link Discovery" https://developers.google.com/actions/distribute/invocation-...
Re: Start building Actions on Google
#55Just tried to send the form to apply [1] but it seems to be broken. It says please complete all required fields despite that I completed all of them (double checked) 1. https://assistant.google.com/developer/eap/
I am sorry you had a problem with the form. I just doubled checked and it seems to work now. Can you please try again, and if not drop me a line http://twitter.com/brada
Re: Start building Actions on Google
#56Earlier quoted context omitted.
The problem with protocol activation is that there are a million different endpoints and you either * Keep a list of every single one that apps can opt into. This is how you end up with "midsized_sedan_carwashing" in an enum list. It's a developer drain for Google/Microsoft/Amazon and creates "wait for the next release for 'largetruck_carwashing' so you can release your app". * Let apps run wild and claim any protoco…
Maybe Assistant could somehow monitor what kind of things users are asking a particular app to do and use that to determine defaults for specific actions in future interactions. Imagine: "Okay Google, get me movie tickets for Rogue One on Tuesday" "I'm sorry, I don't know how to do that yet. Try telling me to ask another service like Fandango or MovieTickets.com." "Ask Fandango" "Okay. [Switches to Fandango.] What th…
That's probably step 2 (or 8). The current situation seems like a good step one, though.
Re: Start building Actions on Google
#57to be honest, considering Google's 0-fucks-given for its non-paying users, which is the majority, i hesitate to touch and build on any of its tech/APIs. someone correct me if i'm wrong, constructive criticism welcome.
I've gotten great service from their Play store customer help. I can't recall a single bad experience I've had with them. They've not only solved my issues but exceeded my expectations with some of them. I'd say that qualifies as "giving a fuck" about their non paying customers.
Re: Start building Actions on Google
#58Pretty neat, but from a user's perspective I'm a little disappointed that the current implementation seems to require me to explicitly tell Google what app I want to interact with. I'd rather be able to just ask Google "Find me a movie ticket for Rogue One on Thursday" and have it be able to infer that I want to use the movie tickets app installed on my phone, than for me to have to explicitly say "Let me talk to Fan…
The problem with protocol activation is that there are a million different endpoints and you either * Keep a list of every single one that apps can opt into. This is how you end up with "midsized_sedan_carwashing" in an enum list. It's a developer drain for Google/Microsoft/Amazon and creates "wait for the next release for 'largetruck_carwashing' so you can release your app". * Let apps run wild and claim any protoco…
This problem is reminiscent of indexing the early web.
Re: Start building Actions on Google
#59Would google focus on paying taxes worldwide action ?
Sad, Google!
Re: Start building Actions on Google
#60API.AI is really great but I really don't like this UX. From using and developing for the Amazon Echo for the last year or so this "Conversational" setup just sounds super unnatural. You want bus times: Amazon: "Alexa, ask [nextbus] [for the next bus]" Google: "Hey Google, let me talk to [nextbus] when is the next bus?" Perfect: "[keyword], when is the next bus?" (context set in advance for the specific bus you care…
IIRC, the perfect examples where you neither say "Alexa" or "Hey Google" aren't going to happen any time soon - those recognition phrases are hard-coded for performance reasons, and adding custom ones will be difficult.
Privacy reasons as well. Every ounce of what you say after "Alexa" or "OK, Google" is submitted to Amazon/Google.
I don't see them changing this ever, so having a recognition phrase is perfectly fine by me.