Frequently asked Questions

There are 3 main steps to get your first show

Step 1 ( <1 sec)

Create a site API on our platform by adding your website url

Step 2 ( ~5 mins)

We give you a divshow_builder script tag that you can add to BUILD your show on your localhost or test site (we recommend in hte HEAD section, but you can add anywhere in the HTML tag). Adding this tag will ask for audio permissions and show a control button near the bottom right corner of the screen. You can use the control button to record, replay and save your shows. Once you save the show we generate a show_id that you can view and edit on the DivShow website.

Step 3 ( ~30 seconds)

We now have a new divshow script tag ready for you to PLAY the show. Include this new tag on your website and create the trigger to start the show. Push the changes live and you'll have your shows running on your site.

For more details please login and view the instructions page.

Yes. When you play a show a presentation banner pops up near the bottom. It has a "Stop Show" button to stop the running presentation

No. We want users to start thinking differently from traditional videos. The intention for DivShow is to keep shows really short so there is a clear focus of what is being communicated to the user and no need to place larger cognitive load on the end user to be thinking about pausing and consuming information before moving forward again.

Absolutely! We encourage users to build small shows as the content and relevance is to the point. These are also easy to update as you make modifications on your website. Becuse of this recommendation we expect users will have multiple shows running on the same page.

No. We encourage service owners to talk about what's infront of their users. Navigating to a new page means a new shows for that page.

Shows recorded on a device are for that specific device. They don't cross a "device boundary" yet. If your site layout doesn't change much your show will work just fine. However, if your layout changes significantly for each device, then you'll have to record the same show for the different layouts you support.

Moreover, given shows are meant to be short, they rarely cross a section boundary. This means the change in layout that spans a show is small and might not need a re-recording.

Give DivShow a try and test this out yourself!

It depends! If the changes are minor, your show may still work on the same page. Stylistic changes will have no impact on the show. Structural changes might have an impact, but the good news here is you can test out if the show works in test mode and if the structural changes are large enough, then record a new show for the new layout.

We can provide support in case you wish to keep the audio for your show, but want to update the mouse movements. However in most cases, users prefer to just record the show again. It's not only faster, but the correct path to take in most cases, because structural changes typically mean new information added into the audio flow.

Yes! Just get in touch with us and we'll help you push the show builder to your live site that allows your users to easily record their issues and report them back to you for further analysis.

This feature is on our todo list. Unfortunately we don't have a timeline available for its release this yet.

Our shows don't work on some browsers (e.g Safari ) and don't play well with some tracker blocking plugins (eg: Ghostery). We're working on trying to get these issues resolved soon.

We recommend you build your show on localhost / locally andn push the player code live.

However sometimes our customers prefer pushing the builder script live to their site as well. In this case you have to make sure the page is served over https.

If you're still experiencing issues feel free to contact us on [email protected]