outaTiME (refinn dot com)

We’re back in action after a Thanksgiving break filled with turkey, stuffing, and pumpkin pie. Now it’s the holiday season (at least, here in the U.S.) and we’re filled with good will toward developers. Today I wanted to talk about a couple things we just finished polishing up.

First, the Android 1.0 SDK, release 2 is now available. Like the previous 1.0_r1 release, this new 1.0_r2 build creates applications that are compatible with Android 1.0 devices, such as the T-Mobile G1. This new release fixes a few bugs. In 1.0_r1, it was possible for developers to write technically-illegal code by using the Java Reflection APIs to access private or protected fields and methods. 1.0_r2 fixes that problem by enforcing private/protected visibility of items accessed via Reflection. Meanwhile, the class android.R.styleable was included in 1.0_r1 primarily for documentation purposes as a way for developers to look up the style attributes available to them to use. However, actually referring to that class via source code would result in applications that might break when run on future versions of the Android platform, so 1.0_r2 corrects the oversight and removes access to the class from the android.jar file. (The class remains in the documentation for reference purposes, though.)

Both of these problems are obscure “future-proofing” issues, and I’d be quite surprised if they actually caused problems for anyone, but now they’re fixed. 1.0_r2 also includes a few other smaller changes; check out the release notes for all the details.

Second, many of you have asked if developer devices will be available. We’ve worked with our partners to create a program for developers to purchase devices that enable them to test and debug applications more easily.

I think these new tools will be quite helpful to developers, and I’m looking forward to seeing what people do with Android, next.

(Via Android Developers Blog.)

Over the past year, we announced Android, released several SDKs (eventually resulting in the 1.0 SDK), gave out the first half of the $10,000,000 prize money for the Android Developer Challenge, and prepared the first Android-powered device for users. Tomorrow, the T-Mobile G1 goes on sale.

But today, we’re making what might just be the most exciting announcement of all: we and our Open Handset Alliance partners have now released the source code for Android. There’s a huge amount of code and content there, so head over to http://source.android.com/ for all the details.

I’d like to offer a huge thank you and congratulations to my colleagues and the Alliance partners for what I hope will be a red-letter day for the open source community, and openness in the mobile industry.

(Via Android Developers Blog.)

About this time last year, my colleagues and I were preparing for the first of the “early look” SDK releases. I remember being a little freaked out—November 12 was starting to sound awfully close! But I think I can safely speak for the entire Android team when I say that we were all very excited about that upcoming release. In the year since, we’ve run and concluded the first Android Developer Challenge, given away $5,000,000, released more SDK builds, and worked with our partners to prepare the first device for users. It’s been quite the whirlwind of a year.

In one of those strange cosmic symmetries, here we are a year later, and we’re once again very excited about an upcoming release. I’m referring, of course, to the first Android-powered device that our colleagues at T-Mobile have just announced—the T-Mobile G1. We can’t wait to see our hard work on store shelves and in the hands of users, but today we’re almost as excited because we’re announcing the brand-new Android 1.0 SDK, release 1.

Yes, that means we’re officially at 1.0. Of course the SDK won’t remain static—we’ll keep improving the tools by adding features and fixing bugs. But now developers can rely on the APIs in the SDK, and can update their applications to run on Android 1.0-compatible devices. The Android Market beta will also launch with the T-Mobile G1, providing developers an easy and open way to distribute their applications on that and later devices. I’ve already seen a lot of applications that have me stoked, and I can’t wait to see things really come together as developers cross that final mile to prepare their applications for Android 1.0.

So what’s next for us? Well, we’ll keep working on the SDK, as I said. But we’re also working hard with our partners in the Open Handset Alliance on the open-source release, with the aim of making the code available in the fourth quarter. The second Android Developer Challenge is also on the horizon—watch this space for more details. We’re also already working on the future of the Android platform, and on more devices. We’ve updated the Developer Roadmap, and we’ll keep updating it as more information becomes available.

It has indeed been quite an exciting road to get to where we are today. The road stretches on ahead though, and we’re not slowing down for a moment. I look forward to meeting and working with many of you developers out there—and trying out your apps on my phone!

Happy Coding!

(Via Android Developers Blog.)

Today, T-Mobile announced the world’s first Android-powered phone. This marks an important milestone in the young history of Android. It was less than a year ago, on November 5, that the Open Handset Alliance, a group of more than 30 technology and mobile companies, announced plans to create a complete mobile platform that would facilitate the development of advanced mobile applications and give users the best the web has to offer on a mobile device.

Software developers are key to driving innovation on the web, and also for mobile. That’s why, over the past year, we’ve released several early versions of the Software Developer Kit (SDK) and worked with developers from around the world to make it better and more complete. This has culminated in today’s release of the Android 1.0 SDK R1. Through the SDK, developers have unprecedented access to the hardware and software capabilities of the device, enabling them to innovate freely. More than 1,700 applications were developed as part of the Android Developer Challenge. Google engineers have also been busy developing Android applications. Many of our products (Search, Gmail, and Maps, among others) are available on a wide range of phones such as the iPhone, BlackBerry, Windows Mobile devices, and many more. Today, they’re also available on Android, and you can check out the Google Mobile blog for more details.

But there’s more to the Android story. Not only does it allow all applications open access to the phone’s functionality; the platform itself will also be open. The Open Handset Alliance has announced its intention to open source the entire Android platform by the end of the year. Along with the other members of the Alliance, we hope that Android can provide a meaningful contribution to all players in the mobile ecosystem: the developers, the wireless carriers, the handset manufacturers, etc. Everyone will be free to adopt and adapt the technology as they see fit. By doing so, we hope that users will get better, more capable phones with powerful web browsers and access to a rich catalogue of innovative mobile applications.

Developers will soon be able to distribute their applications to real handsets through the beta version of Android Market. Handset manufacturers and wireless carriers will be able to incorporate Android innovations into their own new handsets and service offerings. And users will get better handsets and more choice. We think it’s another step towards realizing the full potential of the mobile phone.

Posted by Erick Tseng, Lead Product Manager, Android Team

(Via Official Google Blog.)

I’m pretty happy today, for two reasons. First, I’m happy because I get to let everyone know that we’re releasing a beta SDK. You can read about the new Android 0.9 SDK beta at the Android Developers’ Site, or if you want to get straight to the bits, you can visit the download page. Once you’ve got it, be sure to visit our Developer Forum if you have any questions.

Back in November, we made some SDK builds available that we referred to as “early look” SDKs. The goal was to give developers insight into the platform as early on as possible, and to get some initial feedback. Since then, we’ve been working with our Open Handset Alliance partners to incorporate much of that feedback, and finish the first devices. Since those devices are shipping in the fourth quarter, the platform is now converging on a final “Android 1.0″ version.

The beta SDK that we’re releasing today is the first big step on the SDK’s road to compatibility with 1.0. Since this is a beta release, applications developed with it may not quite be compatible with devices running the final Android 1.0. However, the APIs are now pretty stable and we don’t expect any major changes. If you’re one of the many developers who were waiting for something a bit more mature, this might be a good time to take another look.

Since we’re now moving quickly toward 1.0, it may also help to know which direction we’re headed. To help out, we’ve also prepared a development roadmap. This will be a living document, and we’ll keep it up to date as the Android landscape evolves. Currently it covers the next few months, roughly through the end of the year and a bit into next year. We’ll update it with additional detail as we are able to, but even right now it can help give you a picture of how things will play out as the first phones draw near.

Enough of that though — you’re probably wondering what’s actually new in the SDK. Well, you should read the Release Notes, the Change Overview and the API Delta Report for all the details, but here are a few highlights:

• First and most obviously, the new Home screen is included, along with a ton of UI changes for 1.0.
• Some new applications are included: an Alarm Clock, Calculator, Camera, Music player, Picture viewer, and Messaging (for SMS/MMS conversations.)
• Several new development tools were added, such as a graphical preview for XML layouts for users of Eclipse, and a tool for constructing 9-patch images.
• Since we’ve got a new Home screen application now, we thought the now-obsolete version from the M5 early-look SDK might be helpful to developers, so its source is included as a sample.
• A number of new APIs are fleshed out and improved, and others are now close to their final forms for 1.0.
• Tons of bugs were fixed, of course. (If you had problems with the MediaPlayer, try it now!)

There are a lot of changes — the ones in the list above are just my personal favorites, so you should check out the links above for the full story. Not all the changes are additions, though: I’m sorry to say that we had to remove a few things, such as the GTalkService (for security reasons), and the Bluetooth API. There’s a bit more detail in the links above, and we’ll follow up on those in particular here in this blog to give you the scoop. In fact, we’ve got a little list of topics we want to talk about here, so stay tuned.

At the top of this post I said I was happy for two reasons, and now you know one of them — but what about the other? Well, the second reason is because now that this is out I can finally go get some sleep!

(Via “officialgoogleblogs-dev” via Google Reader in Google Reader.)