We are building a community-written web site which has also been used to create an
O'Reilly Cookbook, both of them about how to build great Android applications.
The site and the book are full of how-to information along with code snippets that
illustrate the ideas presented; most of the code samples are available as complete projects
on github.
It features both how-to's that overlap with the
official documentation, and material that goes beyond this to be
more tutorial, more in-depth, or explaining "lessons from the trenches":
what actually works to get the application functioning well.
Unlike most books written by one, two or a few individuals,
this one has input from dozens of contributors, who were all
able to view and comment on each others' recipes before the book was published.
The published version(s) include printed books, eBooks, and other uses.
And long after the book was first published in 2012,
this site will continue to exist -
with a larger collection of recipes
than will fit in the published book -
and serve as an Android developer resource site long after.

We welcome contributions from anybody who has something useful to say
about how to make usable and successful Android applications.
There are several ways of contributing: experienced Android developers
can write recipes; newer ones can suggest recipes that they'd like to
see; anybody can read and comment on recipes;
anybody can sign up and vote for existing recipes (voting indicates that you
like the recipe and/or think it should be included
in the published edition of the book).
All we ask of contributors is the following:

When writing a new recipe, you put your contribution into the standard Cookbook form
("Problem", "Solution", "Discussion") as described on the
Add New Recipe
form;

Only paste in code fragments that have been compiled and run;

And of course you assert that the work is your own.
Do not copy from others' books or published works; if we wanted to
reprint existing stuff we could just find it on the web.
And if you are working for an organization, you assert that you have permission
to use portions of their code.

Of course, everyone who contributes a Recipe gets credit for it on the site.
In addition, everyone who contributed one or more Recipes that are chosen -
at the editors' discretion -
for inclusion in the published work, received an ebook
copy of the finished edition (readable in all supported O'Reilly eBook formats).

T-Mobile’s parent company says no to pre-installed bloatwareDeutsche Telekom also states that Android updates will now come directly from manufacturers. Could this be a beginning of something new for Android users? Read more...What is Bitcoin Cash? — a short guideWondering what is Bitcoin Cash, what makes it different from Bitcoin, and where can you get it? Here's everything you need to know. Read more...10 ways to become a certified project managerWhatever project management certification you're gearing up for, This bundle is bound to have all the materials you need. Read more...When Android P drops, Samsung will discontinue Samsung Movie MakerSamsung Movie Maker is a hidden app that appears when you edit video on a Galaxy device. Samsung will discontinue the app when Android P lands. Read more...Google Pixel Buds might get customizable tap gestures (Update #2: not quite yet)According to Android dev Daniel Stone, the double-tap to skip tracks gesture is likely caused by a Google Assistant bug. Read more...

Courtesy of AndroidAuthority.com

Site News...

Historical interview for the release of the first edition.On 2017-09-06, Ian said:Just found this: Interviewed at O'Reilly's only AndroidOpen Conference, in 2011 Read more...

2nd Edition listed on Amazon!On 2016-10-12, Ian said:Amazon already have the 2nd edition of the print book available for pre-order. Read more...

New Published Edition, New Site Software Real Soon NowOn 2016-09-30, Ian said:We are on the cusp between editing and review of the 2nd Edition of the published work,
and at the same time working on cutting over the software to a new version (the original site
software is 5 years old, and no longer maintainable). Both these changes will happen this year.
Expect perturbations on the site, it may switch back and forth from new to old software.
At the moment you can preview the new software by using .net instead of .com in the URL.