Android First Week

Wow, what a week! The response from the community on Monday's mechanical man SDK unleash has been overwhelming. Our forums are flooded and we're glad to be serving to folks dig in writing new applications.

A handful of fast notes for this Friday evening:

We've discharged a fast point-revision of the SDK to mend some high-priority problems. you'll currently transfer M3-RC22a and skim the discharge notes. remember to induce Eclipse to update the ADT plugin.

A couple of fine articles on the online for your reading pleasure:

A developer's perspective on Google's mechanical man SDK

Why Google selected the Apache software package License set over GPLv2 for mechanical man

Google Calling: within mechanical man, the gPhone SDK

Finally, we've split our forums into topic areas to create them a little easier to manage. take care to see out the small print and be a part of the discussion.

Have a good weekend, and happy mechanical man cryptography.

Let Me Know Your Code

Activities? Intents? SimpleCursorAdapter? Huh? Hmm...how do I proceed?

you've downloaded the SDK and ar currently ready to make subsequent killer app for mobile (and presumably win some $$ within the methodology ;)

Well, that depends on your vogue. Some would require to rigorously undergo all the documentation top-to-bottom, whereas others might like better to dive right in to code.

Either path can finally result in the sample applications provided within the SDK � these samples are going to be valuable in your go after robot mastery. The samples include:

Source code and resources for these applications ar offered within the SDK (samples/) also as online: http://code.google.com/android/samples/

API Demos
A 'kitchen sink' application that covers the foremost helpful aspects and elements of the robot genus Apis. you will see totally different implementations of Activities, Services, Notifications, Layouts, also as ways for operating with graphics and text. This application provides a stunning supply of templates for your comes and a respect to 'How do I do this?'-type queries.
Lunar Lander
A game that demonstrates a way to load and draw graphics, animation techniques, taking user input, saving state once the user pauses the sport, and more. committal to writing mustn't be this fun!
Note Pad
you will find out how to create use of Intents to open a replacement screen, access an area information, and more. This sample could be a pretty introduction to application flow and life cycle management, that ar very important in developing a lot of complicated applications.

Here ar some suggestions on what to try to to next:

scan through every application's manifest file (AndroidManifest.xml) to find out regarding the standard structures in associate degree robot application.
Alter the code to acquaint yourself with the building and testing methodology.
Use a selected code piece as either a base templet or to urge some required practicality for your own project (why reinvent the wheel?)

Put these sample applications through their paces; and within the event you stand still, post your inquiries to the robot Developers Discussion cluster.

Android you're looking for

Following last week's announcement of the Open handset Alliance, today we're happy to supply associate early investigate the android SDK. We're eager to get feedback from lots of developers in our discussion group. We're conjointly providing developer documentation and this diary to help you get on my feet and going.

You're probably speculative regarding what's out there today. This preview of the SDK will permit you to develop android applications that you simply will run, test, profile, and correct exploitation the copycat and also the other enclosed tools. Note that the planning and feel of the interface in the copycat may be a placeholder for a final version that is beneath development.

One of our goals in cathartic the android SDK is to unleash the creative thinking of application developers on the platform. We'd conjointly wish to get feedback early enough that we {are able to} create changes before the first Android-powered devices are out there to the general public. we decide to release updates to the SDK frequently which suggests that there'll be additions and changes to the arthropod genus and user experience — buy this diary to remain up thus far.

We're really wanting forward to seeing all the wonderful applications that developers will create on associate open mobile phone platform. In fact, you will even want to enter your application into the android Developer Challenge — a USD$10 million challenge sponsored by Google to support and acknowledge developers WHO build nice applications for the android platform.

You cannot rush perfection, but currently you'll be able to file bugs against it

They expected immeasurable attention when they launched the first look of the android SDK, & that is definitely what they got! Developers haven't been back in speaking their minds on our Discussion groups, & we have been listening. we have conjointly been hard at work on android, & in the meantime the Developer Challenge has been heating up & the submissions have started coming back in.

We have been up that "early look" & are preparing for ensuing massive SDK unleash, therefore it is time to take the whole factor up a notch. As they move toward the primary handsets, it is time to formalize the method, & the primary step in that is to change a problem huntsman for developers to submit feedback.

I do grasp an excellent immeasurable developers are waiting thirstily for this, therefore i'm happy to be able to say that the problem huntsman on the android project on Google Code Project Hosting is currently open for business. you'll be able to notice the problem huntsman here: http://code.google.com/p/android/issues/list

We are currently actively following that technique, & they invite developers to file a problem to allow us to understand any problems you discover with the SDK.

When you submit a problem, detain mind that the additional detail you'll be able to offer, the additional probably the problem is to be self-addressed. (They enjoy the refined & delicious flavors of duplicable sample code.) Of coursework, you'll still be able to raise answers & recommendation on the Discussion groups, therefore don't cease posting there. We'll be reviewing submitted problems frequently & keeping the information up to this point, so that you'll be able to depend on it as a reliable & timely resource.

I think everyone will notice this handy -- I do grasp I definitely will. Happy coding, & now: happy reporting!