Next: , Previous: , Up: Preface   [Contents]

4.3 Philosophy and guidelines

Big disclaimer: This book is, at times, very opinionated. Mea culpae, the core of this book comes from my years on the IT battlefield, and I’ve learned the hard way what works and what doesn’t.

I beg you to differ and share your view about any subject covered in this book in the discussion group (see the following How to use this book section). For this book, I have positioned some tools that I find work great in the context of Android project development. They may not be the best tools on the market, but they are the best I have found to get the job done. (They also happen to be the tools I know and use every day). I will explain the process I use to select tools among many equivalents in the chapter on technological watch. You will be able to use these concepts beyond Android app development

I’ve developed the book examples on Linux and haven’t fully tested these on Windows or OSX. However, due to the portable nature of Android (and Java), they should work out-of-the-box on any platform. Generally, for the sake of agility, I do my best to select tools that are platform-independent or web-based. If some examples or scripts don’t work as expected in your development environment, I encourage you to submit a bug report to me with as much detail as possible (and if you happen to find a solution specific to a platform, send that as well). If I can help you, I will, or another reader might be able to give you a hand.

I designed the content of this book as a greenfield project (that is from scratch or without the legacy) and for a team of one or a “two-pizza team”5 in mind. At times, the tools and processes I present will seem like killing a fly with a bazooka if you’re a lone developer, but they will help you structure your work and keep you organized. In fact, if you end up growing your app business (and I hope you will!), you will be grateful that you have observed a Spartan discipline with your Android projects because the best practices already will be assimilated by you and your team, and they will serve as the cornerstone of your Android business.

All designs, processes, examples, concepts, and such presented in this book had to meet the following criteria before being included:

All of this was taken into account for the sake of helping you reduce the time-to-market for your apps and let you focus on developing great ones.



An expression coined by Jeff Bezos, CEO of Amazon. A small team (usually between 6 to 10 people) you can feed with two pizzas.

Next: , Previous: , Up: Preface   [Contents]