Speechly Design Philosophy

How Speechly should be used to improve your application’s user experience?

Speechly is solving voice in a completely novel way. Our API is fully streaming to enable a few key concepts that we think are the missing piece in voice. We have put together a number of best practices that are worth considering when developing your application.

They are split into four short “chapters”, with the following content:

Chapter 1: Setting the right Context

  • Resist the temptation to build an assistant
  • Design the interactions around commanding not conversing
  • Give visual guidance on what the user can say
  • Use voice for the tasks it is good for

Chapter 2: Receiving Commands from the User

  • Onboard the user
  • Avoid using a wake word
  • Prefer a push-to-talk button mechanism
  • Signal clearly when the microphone button is pushed down

Chapter 3: Giving Feedback to the User

  • Use non-interruptive modalities for feedback
  • Minimize latency with streaming natural language understanding
  • Steer user’s gaze and visual attention
  • Minimize visual unrest in triggered events

Chapter 4: Recovering from Mistakes

  • Show the text transcript
  • Fail fast
  • Enable corrections both verbally and by using touch
  • Offer an alternative way to complete the task

Profile image for bigdatabaracus

Last updated by bigdatabaracus on April 16, 2021 at 08:59 +0300

Found an error on our documentation? Please file an issue or make a pull request