Android is hot. Gartner predicts that by 2014, Android will be the No. 2 mobile OS, second only to Symbian. As a matter of fact, at the time of this writing, Google reports that there are 200,000 Android activations per day.

Google's backing, its willingness to work with and by the terms of manufacturers and carriers, the fact that it's open source and, to a certain extent, its timeliness have transformed Android into a seemingly unstoppable phenomenon. For this and many other reasons, Android is therefore increasingly attracting developers' attention, eager to develop new applications for the platform, port their existing products to it or add support for it within their existing products. Fortunately, Google has made it easy for everyone to jump in. Not only has the platform been designed for ease of development from the ground up, but Google also:

  • provides a lot of documentation on all aspects of the system,
  • distributes a well-rounded and well-packaged suite of development tools, and
  • makes the entire system's source code available under an open source license.

Needless to say, Google's openness hasn't gone unnoticed. A community of developers and enthusiasts has started forming around Android, delivering Apps, posting blogs, projects, source code, tutorials, etc. Android is therefore no longer just what Google makes of it, but rather an entirely new ecosystem akin to Windows, Symbian, iOS and others before it.

Approaching Android

For all the interest and the buzz, however, you and/or your team may rapidly be faced with a number of questions when approaching Android:

  • Where do we start?
  • What is important and what isn't?
  • What are the development options available?
  • For a given task, what's the best method to go about doing that in Android?
  • What information isn't readily available out there and where will we find it?

Maybe you've even started progressing in learning Android but feel that you've still got many unanswered questions.

Therefore, while we are confident that you can very much learn Android on your own, the key questions will be:

  • How much time will learning Android take?
  • Will we have to spend weeks learning the ropes?
  • How much time will it take to become truly effective?
  • What impact will this have on the project's schedule?
  • How can we make sure that we are fully prepared to tackle our next Android project?

Perhaps you've even spent time investigating Android already and feel you aren't making progress fast enough.

Opersys' Training

Opersys has built its Android Development Training with a keen eye on development teams' most precious assets: Time and Resources. We have put together a training class that introduces our customers to a wide array of topics covering the state of the art of Android development, including unique insight regarding aspects not covered by Google's own documentation or readily available online. Most importantly, this class builds on over a decade of Mobile and Embedded know-how and our unique mastery of Android's core building block: embedded Linux. Given by Karim J. Yaghmour, author of O'Reilly's seminal Building Embedded Linux Systems, this intensive 5-days hands-on training class will enable you to rapidly acquire a very strong basis for all your future Android development.

We look forward to having you in our class!