Skip to main content

Previewing your application

How to preview changes made to the application in order to anecdotally validate whether the changes had the desired effect.

Previewing in Dashboard

In the simplest case you can preview your application in Speechly Dashboard by going to Application Preview. Press the microphone button, say something and you will receive a transcript in real-time. If your application uses any NLU features, they will be visible here, too.

Please note that you can't preview undeployed changes. After you have made changes, deploy the application, wait for the deployment to finish and then preview it.

Dashboard preview

Indentify errors

Use Preview to identify transcription or annotation errors. When you encounter the, it's usually an indicator that you need to add more and/or better example utterances for the tricky cases. Once you've updated your example utterances, deploy the changes and preview the application to see if it had the desired effect.

Tip

Text adaptation will get you quite far, but many tricky cases benefit from Audio adaptation. In general, audio adaptation results in higher accuracy than text adaptation alone. We recommended using both audio and text adaptation to achieve the highest possible accuracy

Viewing speech segments

You can open the browser developer console to see the JSON response that's emitted for each speech segment. This might be very handy when you are debugging.

{
"id": 0,
"contextId": "1dce01bf-3380-4690-9847-6cd7ae75cf04",
"isFinal": true,
"words": [
{
"value": "schedule",
"index": 2
},
{
"value": "for",
"index": 3
},
{
"value": "october",
"index": 4
},
{
"value": "tenth",
"index": 5
}
],
"entities": [
{
"type": "date",
"value": "2022-10-10",
"startPosition": 4,
"endPosition": 6,
"isFinal": true
}
],
"intent": {
"intent": "schedule",
"isFinal": true
}
}

Production and development applications

Another common pattern is to have a separate production and development applications. This will insure a clean separation between development and production versions of your application, and that nothing from your development application will cross into your production deployment until you want it to.

A two application workflow might look like this:

  1. Create two different applications (e.g. Acme Dev and Acme Prod) with identical configurations
  2. Deploy new changes to Acme Dev and preview the application
  3. In your local/staging development environment, use the Acme Dev App ID for testing
  4. Repeat steps 2-3 as needed
  5. Once satisfied with the changes, copy the changes from Acme Dev to Acme Prod
Tip

Copying changes between applications using Speechly Dashboard requires you to manually do it. If you are comfortable using Speechly CLI, then the download and deploy commands will speed up your workflow.