[HamletDRC]

From a brief look... the blog is part aggregation and part original content. So that links to posts outside the domain are going to vary greatly in quality.

Most of the tutorials focus on how to mechanically get something done. For instance, reading a SOAP service, changing some fonts and backgrounds, and others. This will not tell you how to design a program. It just tells you how to accomplish some small task. There is no guidance on abstractions and code organization, just tips on getting some little thing done.

I don't know of any design-oriented android resources. The Google Dev Guide is quite good and offers a lot of advice. Read it like it is a book. The "Busy Coder Guides" are highly touted, but they are again about implementation and not design/organization. Also, I have Pro Android and it too suffers from this problem, despite being over 100 pages long!

My advice is keep it as simple as possible. Avoid too much abstraction and redirection unless you benefit from it; just build what you need today. If you ever write an object called ServiceFactoryContainerBundle then stop and simplify. And if you find yourself writing a "form generator" framework then stop and ask yourself "what is my product?". Unless you're trying to sell a form generator framework then again stop and simplify. Just my 2 cents.

[TheCapn]

The issues you address aren't Android specific though and probably shouldn't be addressed by "Android" tutorials since they aren't specific to the platform.

[nextparadigms]

There's thenewboston.com for video tutorials, and also anddev.org.