Tuesday, November 29, 2011

Introducing Au-to-do, a sample application built on Google APIs

Author Photo
By Dan Holevoet, Developer Relations Team

A platform is more than the sum of its component parts. You can read about it or hear about it, but to really learn what makes up a platform you have to try it out for yourself, play with the parts, and discover what you can build.

With that in mind, we started a project called Au-to-do: a full sample application implementing a ticket tracker, built using Google APIs, that developers can download and dissect.

Au-to-do screen shot

Au-to-do currently uses the following APIs and technologies:
Additional integrations with Google APIs are on their way. We are also planning a series of follow-up blog posts discussing each of the integrations in depth, with details on our design decisions and best practices you can use in your own projects.

By the way, if you’re wondering how to pronounce Au-to-do, you can say "auto-do" or "ought-to-do" — either is correct.

Ready to take a look at the code? Check out the getting started guide. Found a bug? Have a great idea for a feature or API integration? Let us know by filing a request.

Happy hacking!

Dan Holevoet joined the Google Developer Relations team in 2007. When not playing Starcraft, he works on Google Apps, with a focus on the Calendar and Contacts APIs. He's previously worked on iGoogle, OpenSocial, Gmail contextual gadgets, and the Google Apps Marketplace.

Posted by Scott Knaster, Editor


  1. Thanks, this is the kind of stuff we need from Google.

  2. I'd like to see a working version of this I can demo to see if it's something I could use.

  3. Nice work!
    By any chance, will you guys release a java version of it?

  4. ooh dear, should I be hearing warning bells based on the fact that GWT was left out of the mix? Even Google haven't used it for the client-side portion of this application.

  5. Yes please create a JAVA version of this application. And yes whey didn't you use GWT? Can we get another application like this that shows off JAVA + GWT + OAUTH2.0 + GOOGLE APIS!!?

  6. Ian, I have exactly the same thoughts about GWT... Google's position on GWT is pretty unclear for me...

  7. GWT is not everything and there's not only Java in the world. Python is a good choice for this project...

  8. As per the post:
    Have a great idea for a feature or API integration? http://code.google.com/p/au-to-do/issues/list

  9. I love that it's in Python. Thanks.

    In addition to it being a good sample to study, it would be nice if it's also a tool I can use and extend for real work. To that end, I'm not sure why tickets can be added by email only! Also, I can't comment on or add to a thread directly from the app. Is it intended to be an email tracking tool?

  10. Python is a good choice for this project

  11. Anyone has a workign instance of it?

  12. I went through the getting started guide. But the critical last step is adding the app as a member to a Google Group via the "Add members directly" option. Unfortunately this feature has been removed from Google Groups as of July (http://groups-announcements.blogspot.com/2011/07/new-in-google-groups.html). I think one could devise a means of answering the groups invite via Python to get over this bump in the road.

  13. Why do you guys care about a GWT/Java version? Python is an excellent choice for a project like this.

    Language diversity is healthy.

  14. @ernest, I believe the 'Add members directly' option is still supported via Google Apps groups, and it was only removed for non-Apps groups.

    There is also a feature request on our project page for supporting tickets that don't come from email: http://code.google.com/p/au-to-do/issues/detail?id=1. Please star this request if you're interested.

  15. @Dan, many thanks for the guidance re:Add members directly. I'll try to dig into where I went wrong on that.

    I've stared the feature request and will keep an eye out for updates.