Yesterday saw the launch of MyVox 1.1, which added a number of new features to the product. Perhaps the most significant is the concept of the call-initiated app.
In 1.0, every MyVox application was written with the expectation that a user would be sitting in front of some sort of screen in order to start the voice recording process. That could be a Web page, a desktop widget, a mobile app, even an email or text message… but you needed to take some screen-based action in order to start a MyVox session, and get the phone number necessary to call and make your recording.
We realized a while ago that there was a whole class of applications that opened up if a user could start the recording interaction simply by picking up the phone. Freed of the need for a screen-based interaction, suddenly you can have people making recordings while they are out and about, untethered. People can call in from cars, concerts, nightclubs, on bikes, hiking trails, at museums, in classrooms… wherever. But importantly, the recording can still be tied back to an application, which takes it and makes use of it.
1.1 makes this possible. These “call-initiated” apps still use the same structure and API; the main differences have to do with how you set up your voice recorder (the core object of the MyVox API – each app has one), and with the assignation of a specific phone number to each application (as opposed to the traditional MyVox app, where a phone number is handed out for each recording session).
1.1 also offers…
* Identification of call-initiated users by caller ID, access code, or both, allowing (among other things) the gating of access to such apps
* One-time collection of a touchtone code at the beginning of the call, to use however you will; think zip code collection, product ID entry, etc.
* Caller ID as an attribute available on any call/recording
MyVox 1.11 will be launching very soon as well. Keep an eye out!