There is a really interesting conversation around Voice User Interaction ( VUI ) going on between myself and a few others over at https://community.jovo.tech/t/testing-tuesday-escape-the-room-alexa-skill/50
and it also overflows a little into Twitter here...
I LOVE it! 😍— Florian Hollandt (@FlorianHollandt) March 20, 2019
If you're interested in #VoiceGames, you should check out (and join!) this fascinating discussion about #VUI design choices (e.g. complex vs simple) in Escape-The-Room-type puzzle games, sparked by yesterday's #TestingTuesday episode (featuring @falicon). https://t.co/RxHlfoWCQv
I've been thinking a lot about this specific topic as I try to finish up version one of my Adventure Game Plugin for Jovo.
The plugin itself will support a ton of commands and so it will be up to the game developer to determine which ones to include in their game, and how best to reveal these to the player...but since I'm going to also release a couple of 'starter' games using the plugin myself (and need to be able to show people how to implement the plugin)...really I feel like I need a "recommended" approach to this problem.
As I mention in the threads above, my thought is that I would probably try to use the "level up" approach...introducing new commands as players hit specific spots of the game.
However, I do really like this concept of a very limited initial control set...something akin to the classic joystick. So that the player can mentally map it to a "known interaction" very quickly (and still have a pretty large amount of flexibility as to what they can accomplish with that basic control).
The mini-game approach is also really interesting...in my plugin, this is probably more closely mapped to the 'puzzles' concept where the game developer can define specific puzzles for rooms, objects, characters, and other things (though this applies mostly on the game logic side, not really on the VUI part -- so I'll have to think about this all a bit more).
Anyway - there's a lot of interesting things to think about and dig into around all of this...so I hope you do jump into the conversation somewhere and let us all know what you think!
This post has received 6 loves.
Kevin also talks in more depth about many of the these things around twice a month via his drip campaign and has a day job as CTO of Veritonic. You can also check out some of his open source code on GitHub or connect with him on Twitter @falicon or via email at kevin at falicon.com.
If you have comments, thoughts, or want to respond to something you see here I would encourage you to respond via a post on your own blog (and then let me know about the link via one of the routes mentioned above).