In other words, VoiceXML programming is complicated, as if speech technology wasn't complicated enough on its own. One of the things that usually saves developer's sanity when writing in other programming languages is a decent "development tool" that helps make the task of programming easier. The tool will often automate certain tasks, find errors in the program, and sometimes even help the developer remember all the various features of the programming language. I've had one situation, programming in a new (to me) language, where the right tool spelled the difference between success and disaster.
The name of that important tool, by the way, is Eclipse. Eclipse is an open-source project that has a modular structure. People build new tools on top of Eclipse to support new programming languages as well as new methods to program — for example, a new way to visualize the program you're writing. Over the years I've tried a few packages that purport to provide VoiceXML language programming via Eclipse, and never found one that was satisfactory. I embarked on a quest to find a decent tool — which led me to organize and run a public demonstration of different tools at a recent industry conference.
A company I often work with, Voxeo, announced the purchase of VoiceObjects today. VoiceObjects makes an Eclipse-based VoiceXML editor. This is a funny coincidence because I'm in the middle of writing up an assessment of that public demonstration of speech application tools and VoiceObjects is one of them; I'll reveal in advance of my article that I liked VoiceObjects.
I recommend a look at Voice Object's extensive documentation to get a better idea of what they offer. I particularly like the idea of generating project documentation from within the design tool. Even more importantly, Voice Objects' tool output is "standard" VoiceXML, not a proprietary flavor, and the output interoperates with many VoiceXML platforms (not just Voxeo's, for example). This quote from Voxeo's press release is particularly important:
Voxeo will continue to openly and actively support VoiceObjects' application deployment on multiple VoiceXML platforms including Aspect, Avaya, Genesys, Intervoice and Nortel.In other words, Voxeo is smart enough (as usual) to realize that they should compete on cost and service instead of attempting to lock in their customers through the use of tools that generate output that only works on their system. I know that I prefer a tool that interoperates over one that does not.
Strategically, this fills out Voxeo's suite of tools. Their current design tool ("Evolution Designer"; I've never used it) is suitable for entry-level programming; VoiceObjects is suitable for high-level developers. Speech technology programming is difficult work, with only a (relative) handful of VoiceXML practitioners worldwide; from Voxeo's perspective, the more programmers, the more speech technology applications and the more business for Voxeo.