Quick hit: I lost my phone in a cab last night, and while the sweetest kid EVER found it and got it back to me, it made me think twice about my mobile contingency plan. I realized I had a few holes, so I wanted to share what I’ve already done, and how I’m patching the holes. All of these are Android-specific; I haven’t investigated iOS options for my iPad yet.

• Contacts. All of my contacts are through my Google Apps account for deannazandt.com, so we’re good there.Apps. I’ve rooted my phone, so I use Titanium Backup Pro to create regularly scheduled backups of the application and application data on my phone. The free version sends the backups to your SD card; I bought the Pro version so I could have those apps backed up to Dropbox, too.SMS & MMS. I use Backup to Gmail for this. It automatically sends your SMS, MMS and Call Log to your Google account, and files them in the Archive with appropriate labels.

  Photos. This was the big one for me: I have a lot of photos on my phone that aren’t shared on my social networks. I was mourning the potential loss of some precious Christmas photos, for example. I’m now trying out SugarSync to back these up to SugarSync’s cloud, and then to my laptop; I chose this one because many services wanted to use public social networks for the backup. That was too risky for me. Plus, it seems that SugarSync has good reviews on managing battery and scheduling, and you get 5GB of free space.

  Locator. Tara Hunt turned me on to Prey, which is a full suite of services for a lost phone. You can locate the lost device, send messages to it for the finder to tell them how to get in touch with you, and if they don’t comply, you can brick the device.

  Those were the biggies for me. What else am I missing?

Google Forms are great: they’re dead simple to build, and they can be accessed on the web via Google and (through the use of <embed> code) any other website as well.  Support for email publishing is great, and Google Forms work seamlessly with Google Docs spreadsheets.  It’s been my experience that within small and mid-sized businesses that are already using Google Apps, the internal use of Google forms has become routine.

What’s interesting, though, is that you tend to see them being used much less often out there in the wilds of the public internet.

That’s because Google Forms have one major weakness: unlike within the Google Apps ecosystem, public submissions are completely anonymous – so there’s no way check against users submitting multiple responses to the same form.  Granted, it’s not an easy technical problem: browser cookies are one option, but users can always delete them. Comparing the IP address of each submission against those of previous submissions?  That’s not a perfect solution either: consumer ISPs typically issue dynamic IP addresses, multiple legitimate users could be sharing the same internet connection, and lastly, there are, as always, privacy concerns.

And that’s just the technical side of the issue – from a PR perspective, of course Google has to be very careful about being perceived as being in the business of anything remotely resembling the tracking of users out there on the public web.  Still, it’s hard to imagine why Google hasn’t yet implemented a transparent, user opt-in system to prevent multiple public Google Forms submissions (even if it might reduce the number or submissions).

In the meantime, for all the <embed> code and URL access, Google Forms is essentially crippled as a public web service.

OK, so that’s the web – what about Google Forms sent via email to a private finite set of known respondents?  Here, the privacy issues (both real and perceived) are much reduced – and technically speaking, identifying data could easily and securely be embedded within the ‘Submit’ link contained within each email – but yet, even privately emailed Google Forms responses are completely anonymous (and therefore uncontrolled) as well.  As a result, a Google Forms email survey subject could ‘game the system’ by clicking on the ‘Submit’ link in their single email any number of times.

Conclusion   As a public web service, Google Forms has great potential – but addressing the unique/multiple submission issue would involve technical challenges, privacy concerns, and a potential for third party misuse that are clearly beyond Google’s comfort level.  As a result, any serious use of Google Forms remains limited to within the Google Apps platform.

Sure, a nod has been made towards the public use of the service (Google URLs, <embed> codes, email distribution) – but it seems that Google’s comfortable with letting Google Forms remain merely a Google Apps value-add.

In the meantime, here’s a completely anonymous (and therefore completely meaningless!) Google Forms survey for you.

Vote early, vote often!

Microsoft has a web browser – Google comes out with a browser.

Google has a great search service – Microsoft comes out with a great (bing) search service.

Microsoft has an operating system – Google plans an operating system.

Google’s recent announcement to have a Chrome operating system available in about a year has generated a lot of chatter lately – but is it really a Windows-killer?  I think not – not anytime soon, that is.  Although the era of Vista will soon be behind Microsoft and Windows 7 (still in beta) is earning favorable early reviews, the primary reason Google’s OS won’t vanquish Microsoft’s Windows operating systems is that while the two companies’ browsers and search engines fulfill exactly the same roles, a direct Windows-Chrome OS comparison is a lot less apt.

Read the rest of this entry »