Another side effect of using the api was that we found the mics in phones are much better then computer microphones. The audio we get from call in audio is cleaner by far compared to a microphone in the computer.

The solutions for voice over microphone for websites were out there. A simple “plugin and go” solution for phone to website never existed until MyVox came on the scene. We were on the brink of trying to fumble and set up our own goofy solution until MyVox saved us. To add to it all, they revenue share.

I already hate using my phone, I’d rather have a flash widget that recorded the audio.

Anybody know of an audio recording service with an API that uses flash, or if these guys are planning to?

This is an interesting twist. It stays out of the app game and hence the need to build a company around one app, instead giving developers the ability to build their own voice-powered apps. This is likely a quicker way to get to a level of call volume that is large enough to build an ad network around.

The strength in call in audio application is that telephones are ubiquitous and that audio input by use of the MyVox api is near instantaneous. Which is to say the moment you finish the phone call your application has the audio data in hand.

@3 - The audio ads are fairly quick and painless. I made the map application and I had to test a lot meaning I had to hear quite a few ads. They’re not bad at all.

The map application is written entirely in javascript (with exception of the flash audio player). And when i say entirely in javascript I mean that I didn’t have to even set up a database or table to store the data. All data is stored and handled by the API. Including password protection. It’s a very robust and flexible API.

@2 it is like video, it depends on the listener/viewer interest level. if it’s something you are interested in, you probably will accept the linear nature. fast-forwarding video isn’t the same as skimming, yet video is pretty darn popular I think these days.