[cjfont]

Viv is being presented as a platform for other developers to build on top of, and these 3rd party developers will be the ones responsible for fleshing out the specifics of how the queries will work given the domain they are implementing for. They will be the ones who will need to anticipate all of the different ways a user can request for something in particular and include all of the edge-cases that might trip-up the API.

In the end I think queries for certain types of well-established services like asking about the weather are probably going to yield better results than more obscure/complex things like placing an order for building custom furniture from a small workshop.

[kowdermeister]

I'm aware of that, but will people realize that? They will just say Viv sucks despite the Netflix app was sloppy.

It's also not clear that what went wrong in certain cases. In one request part of the parameters can be handled by Viv core, part by Netflix and part by another app.

[tedmiston]

Yes, but who is in control of whether "find me a hotel" searches hotels.com, or Kayak, or Expedia, ...

[kowdermeister]

I think 80% of commands will be handled by Viv's core app, then the third party apps take control seamlessly. It will also learn that you always prefer AirBnb over Hotels.com.

[cjfont]

Whatever the default search target for travel stay is, if there is one, will probably determine a large percent of what users will simply stick to using without bothering to change it to another preference, since they may not know better. This default does leave an opportunity for some companies to have an edge over others, and potentially pay to make it so.

[jonathankoren]

Not if there's only one intergration.

The problem with third party integration is that you're going to end up getting a bunch of duplicate "skills", to use Alexa terminology, of varying quality and capability. It's the App Store problem, and bot store problem all over again.