doozzoo logo

Guide for our open beta

Join the Open Beta And
Make a Difference in Music Education!

doozzoo is gaining momentum, and we are thrilled to have you join us on this exciting journey. As we embark on the next phase of development, we are delighted to extend to you an exclusive invitation to explore our pre-release version, known as Beta. Allow us to guide you through the simple steps to join our open beta testing phase. Please bear in mind that while we strive for a seamless experience, some minor hiccups may still occur during the Beta stage.

4 Steps for a
Successful Beta-Test

Icon-Nr1

Sign in

Visit beta.doozzoo.com and log in using your doozzoo credentials. You'll find all your existing data from your regular doozzoo account, including your media library.
Tip: Regularly refresh the page!

Icon Nr 2

Select Students

We recommend starting small by choosing a few of your tech-savvy students and asking them to log in through beta.doozzoo.com. Instead of conducting an entire day of classes on the beta interface right away, this approach allows for a smoother transition.

Icon Nr 3

Local Latency Setting

Before your first beta lesson, we suggest you and your students readjust the local latency compensation. Simply go to the settings and recalculate the latency compensation.

Icon Nr 4

System Requirements

For the best and most stable experience, we recommend using doozzoo on the Chrome browser. If you prefer using other browsers, please let us know in your feedback. Feel free to explore all the features of the doozzoo Beta using your favorite microphone and headphones

New Features

We’ve made some changes and added new features.

Here are the highlights:

  • App menu bar on the right now
  • Screen division is changed and fixed
  • PDF view with a fixed position
  • Audio player with a fixed position
  • New (hidden) features. Can you find them?
Provide Feedback

If you encounter any issues or if something doesn’t behave as expected, we’d appreciate it if you could provide detailed descriptions of how the error occurred or what behavior you were expecting from doozzoo instead.

 

If you encounter any issues or if something doesn’t behave as expected, we’d appreciate it if you could provide detailed descriptions of how the error occurred or what behavior you were expecting from doozzoo instead at beta@doozzoo.com

 

Important Information for Your Feedback:

  • Operating system and version
  • Browser and version
  • Peripheral devices used, such as microphones or interfaces
  • Can the error be reproduced or triggered?
  • Did you notice similar behavior on the student side?

Ready for an open beta test?

Start now and help us to make doozzoo even better