Putting Google App Engine and related cloud services to work on Google Voice features.
In the process of migrating my personal and family voice communications to all digital IP-based components with wireless, cable, and femtocell, I jumped on the Google Voice bandwagon as the provider for voicemail access beyond our home and into the multiple devices we collectively use throughout the day. The experience of walking in the door to a flashing message light and scrolling through a caller ID list on a last-generation handset would be replaced with a cloud-based multi-modal solution. I had it all mapped out to be a sweet setup with my wife and I both having our smartphones and laptops as extensions of our home during the workday.
One problem ... Google Voice didn’t support my use case. The new message notification settings were locked down to a single outbound email address. Intentional or not, for me it was clearly broken but not beyond repair or replacement given my MacGyver-like DIY tendencies. It had been on my list to do a bit of deeper R&D and analysis into the Google developer platforms in general and App Engine specifically, so why not mix business and pleasure for personal and professional gain? Here goes ...
We have a saying in engineering about improving something until it no longer works. Another one goes “if it doesn’t fit, force it – and if it breaks, it should’ve been replaced anyway.” Both may apply to Google’s recent short circuit.
ArsTechnica staff explain their attempts to incorporate Google Wave into their communications portfolio: