Google's I/O Developer Conference, held at the Moscone Center in San Francisco. Android Community will be there, bringing you all the news, but thanks to our friends at Google we've also got three I/O tickets to give away to Android Community members! Last year, Google used the conference to show off their latest Android prototype and discuss their view of cloud connectivity and the future of Android. This year, after successful commercial launches of actual Android handsets, we're expecting even more news and insight. With Apple launching iPhone OS 3.0, Palm's Pre expected next month and Windows Mobile 6.5 chomping at the bit for release, this is Google's opportunity to wow us with the next generation of Android innovation. To stand a chance of winning one of the three Google I/O Developer Conference tickets, we're asking you to tell us about your most memorable experience with the Android platform. We'll pick three, and those people will have access to the conference at the end of the month - if you can even get hold of a ticket they normally cost $400 each. Remember, you'll need to get yourself to San Francisco for the conference, plus have somewhere to stay. Terms and Conditions Competition is open to residents of the US over the age of 18. Family members of Google and R3 Media are not permitted to enter. Competition entries are only accepted in the forum thread for this article; entries left in the comments of any other post will not be recognized. Entries should be submitted before midnight pacific time on Sunday May 24th; one entry per person. The winners will be announced on this site and contacted via email; they will be expected to respond within 48 hours else their prize may be forfeit and another winner selected. Editors decision is final and no correspondence will be entered into. Winner agrees that their name and details of their entry may be used for promotional purposes by, but not limited to, R3 Media. Each of the three prizes consists of a single ticket to the Google I/O Developer Conference, held May 27th to 28th in San Francisco. There is no cash alternative. Winners are responsible for any travel, accommodation or sundry expenses incurred in visiting the conference.
One Google IO attendee asked for more details of second round of Android Developer Challenge; more specifically when is the start date. Jason replied saying that they still need to complete round 1 of the Android Developer Challenge and that it’s most definitely be after Android devices hit the market or probably early next year. About Jason Chen Jason is currently a developer advocate at Google where he works on ensuring that developers for the Android platform are successful. He previously led the developer support team for Google Checkout. Prior to joining Google, Jason worked at IBM and Urchin Software. [youtube]http://www.youtube.com/watch?v=I0bGWv6k57o[/youtube]
Ed Burnette of ZDNet, we have a few more questions answered as well as clearing up some confusion regarding the Android platform. The Introduction to Android platform session lasted around 90-minutes. Jason announced that the source code to Android is currently available to Google's Open Handset Alliance (OHA) partners. The general public will get access to the source code when the first handset (that being the Android HTC Dream phone) ships. At such time, Android will be called "Android Version 1.0." Android version 1.0 will be available to everyone and anyone who wants to download and port Android to any phone or any other devices they so desire. Once Android version 1.0 hits the street, you do not have to be an OHA member and you don't need to sign anything or ask for anyone's permission to install Android on any device. The audience wanted to know when will Android version 1.0 be available. Unfortunately, Google would not provide any specific dates other than "the second half of 2008." When pressed, a Google source stated that it wasn't really their call alone to make. The release date is largely up to OHA members, especially manufacturers making the phones and the carriers who will sell and distribute the Android phones. Lets hope all 31+ OHA members don't take too long to decide when's the best time to release Android version 1.0. After his presentation, Jason opened up the floor for questions... Q. What if somebody wants to build an application that is similar to a Java Virtual Machine (JVM) that can run other programs. What security implications are there for these kinds of applications? A. It's possible to do but we haven't thought about it. There is a large security team working on Android. There are languages that are working to port their bytecode to the Dalvik VM, so it won't just be for the Java language. Q. Traditionally carriers rip out things. What steps do you take to prevent somebody like Cingular from making an "almost-Android" phone? A. They could do that if they wanted because it's open source. But Android is a complete stack of software so why would you want to break it? There's value in a full stack and in a lot of applications. There's no incentive to alter it in ways that wouldn't be compatible. We want manufacturers and operators to customize in ways they can differentiate. They don't all have to have the same home screen, the same look and feel, and so forth but they should be able to run any Android apps. Q. When do developers get hardware? A. When everybody else does (when retail phones are for sale). Q. Does Android platform development follow the JSR (Java Specification Request) model? A. Android is not Java technology. It uses the Java programming language but Dalvik is not a JVM. It's not claiming to be Java tech. Q. Is support for Flash lite planned? A. Not at the moment. Q. Will there be an SDK for PPC Macs? A. Don't think so. Just Intel. Q. Will you have aesthetic standards like the iPhone? A. We're working with UI designers to put out a user interface guideline. Also android provides standard UI widgets. About Jason Chen Jason is currently a developer advocate at Google where he works on ensuring that developers for the Android platform are successful. He previously led the developer support team for Google Checkout. Prior to joining Google, Jason worked at IBM and Urchin Software.
[youtube]http://www.youtube.com/watch?v=p05FcwoYej0[/youtube]In the next article/video, I’ll walk you through the “other side” of this room to tour the different groups just hanging out and chit chatting about YouTube, Google Web Toolkit, Google Data APIs, Gears, OpenSocial Application, Android, etc. As Robert of Scolbleizer.com put, “How can you tell what’s hot at a conference?” Come to the party and check out the size of the crowds around the tables.
[youtube]http://www.youtube.com/watch?v=quM0S3ZXhEw[/youtube]More videos from the Android Fireside Chat coming soon.
Android prototype demonstration, the developers sat down for a Q&A session. The question on everyones' lips was what exactly the demo hardware consisted of, and who made it; while the answer to the latter was under NDA, we were given some details of the former. Based on a 528MHz Qualcomm processor, the smartphone used a Synaptics capacitive touchscreen and the UMTS cellular standard; the demo itself was carried out using a 3.6Mbps HSDPA connection. Android's memory requirements continue to be reasonable: the prototype had 128MB of RAM and 256MB of flash.
iPhone 2.0! As our exclusive demo videos show, the Android team have been putting in some long hours bringing the user interface up to the standard people expect. The iPhone sets the bar high, and leftfield rivals like Samsung's TouchWiz GUI really pile on the pressure. What they've given us is, at first glance, a blend of the successful parts of each of those, together with a dose of Google's own minimalist aesthetic. Hopefully you'll agree with us, once you've looked through the photos and watched the video, that the design is a winner. In this first video, we see an overview of the new interface and menu structure, including the clever pattern-based unlock screen. Much of the GUI can be interacted with - for instance pulling down the title bar reveals missed calls and new messages - using the familiar palatte of swipes and taps. You can also see the straightforward way to create shortcuts on the home screen; a matter of holding down your finger and then following through the contextual menus. [youtube]http://www.youtube.com/watch?v=arXolJrLVEg[/youtube] Next up, Google's Street View gets the Android treatment with a built-in compass. That lets you pan around the location-based image, turning the handset into something of an augmented reality device. As you can tell by the applause, this was one of the most popular apps! [youtube]http://www.youtube.com/watch?v=4PRfVKzuUJ4[/youtube] Google briefly touched on their work with developers, including the latest round of entries in their Android Developers Challenge. Here you can see a port of Pacman, developed for the handset: [youtube]http://www.youtube.com/watch?v=DfruA4RzzpQ[/youtube] In this last video, a demo of Google Maps, you can see how closely the Android experience matches that of the desktop. All of the usual mapping options are present - satellite views, traffic, etc. - and, with a 3G network, load and update quickly. [youtube]http://www.youtube.com/watch?v=iBHx5jHsqiU[/youtube] Pac-Man on Android for the firs time! [youtube]http://www.youtube.com/watch?v=4q3gGNtbxhQ[/youtube] Customize how you want to unlock Android [youtube]http://www.youtube.com/watch?v=JGCIlAwrpvI[/youtube] [gallery]