Google I/O Ticket Giveaway
Google I/O, a two-day, in-depth conference for developers, will be held May 28th and 29th at the Moscone Center in San Francisco. Sessions with top Google engineers will cover tools developed both inside and outside the company, including yet-to-be announced initiatives designed to move the web forward. GigaOM has 10 tickets to give away; simply post in the comments section why you, more than anyone else, deserve to go. Make sure you enter a valid email address! The 10 best will be picked by our editorial staff.
Related research and analysis from GigaOM Pro:
Subscriber content. Sign up for a free trial.

Because I am the first to post in the comments!
I guess being the first to comment will not count as a valid reason :-)
Here are couple of real reasons
– early stage company building a social application on Google appengine. having access to information straight from the horse’s mouth would be a great jumpstart
– Early stage = broke = cheap founders. free is always welcome
I deserve to go more than anyone else because I am sure it will be a comfortable environment to doze off and catch up on sleep :)
On a serious note, a couple of weeks ago, I just began working on a new web-based project (a lot more than just a website) which will continue for the next 3-4 months. Since I am new to this and doing it on my own, I can use all the help I can get in terms of getting upto speed with open tools and standards for the purpose. This will hopefully accelerate my work and/or give me new ideas/perspectives.
In return, I’ll share my experiences here :)
I would be very interested in learning more about the App Engine and will in exchange create a write up about it.
I’m willing to take the time and effort to trek out to California from the middle of the country to attend, given enough lead time to plan. I bet no one else within several hundred miles will, but people nearby will gladly listen to me tell about what I saw and learned…and I take great notes. It’s not quite bringing the road show out here, but it’s pretty good.
I deserve the free ticket because I’ve built a breaking-even business around a useful Facebook app with more than 400,000 users. For some of my next-level ideas I’d love the get a bit of an inside track on what’s going on chez Goog.
I just got my appengine account and I started playing with it. I would love a chance to ask them questions regarding issues and roadblocks that I encountered. Perhaps the 10 people that goes can come up with tips for how to better use Google tools.
Because I have tokens to our alpha test site in exchange. ;)
I deserve to go the most because i’m a struggling computer science student here in San Francisco. The choice between eating for the week and $50 dollars for the conference is a tough one but i’d probably have to choose the food. I’d really love to go I/O and learn a lot about these APIs. Help support for the future of CS! :D
Two weeks ago, we were not sure we going to enter the Android developer challenge. Last Thursday, we decided to give it a shot. The new dateline is Monday, April 14. We have to port Fon11 and Open Landmark (iPhone version) to Android in less than 10 days. Can we make it?
On Saturday, we concluded our mobile Web version is not going to cut it. We can’t invoke the Location API, native map and address book to integrate our app with the Android platform.
We have to write native Android apps.
Android XML-based UI layout is easy to recreate the Fon11 UI on Android. We need to figure out how to manipulate the UI elements with dynamic data. This shouldn’t be too difficult. Calling Android location API, native map and address book is quite straight forward.
This is Tuesday night now. We got together at a code camp at 1 PM last Sunday. Ten of us got together. Most of them were my former/current students. Patrick and Tim led the project with Thomas, P. Hetroy, Eric, HsiaoYun, Lex, Chetan and Martin. By 8 PM, we have all the Fon11 pages created on Android. Next, we have to modify the UI dynamically from Java.
Tonight Patrick, Tim and Lex are trying to figure how to invoke REST APIs on the server side. Oh, oh, we have a problem consuming the JSON object from JSON. This is not an Android problem. It is a known problem with Jersey (we use Jersey to create our REST API). Okay, Lex wrote a hack.
Everyone really likes Android now. They are sold. The programming model is cool. Full Java on mobile is cool. Well, I think we have a native Android Fon11 app to enter the challenge. We will submit both Fon11 and OpenLandmark. Fon11 as a native Android app. OpenLandmark as a Web app. Fon11 will launch OpenLandmark.
The iPhone Web app version is 100% compatible on Android browser. Android is an iPhone competitor.
I can use a pass or two. They are not for me. I want to give them to my students at the code camp.