I started writing this book on July 1st, 2014, and it has been in progress ever since. You can download a free copy (.mobi, .pub or .pdf) in its current state on the official website (http://www.agiledroid.com). Agile Android Software Development is published under a Creative Commons NonCommercial ShareAlike licence. The ebook has been downloaded more than 5,000 times, and the mailing list totals more than 1,600 subscribers.
And that's only the beginning! I now want this book to go to the next level: release 1.0.
How I will do it
The book idea was in my head for months before I decided to start writing. I was taking notes in the form of a mind map to jot down what was missing from the Android programming books I had read while learning Android.
Over the months, I've managed to put in place a series of tools that enable me to do "continuous publishing" of my book. The book "Pro Git" by Scott Chacon was a great source of inspiration, and I chose to use the same tools he used for his book because it allows me to work with tools I'm used to as a developer: Markdown, Git, Jenkins, etc. This suite of tools proved from the start that I can produce ebooks easily—and not just after I have written the entire book. The main benefit for readers is that they always have an up-to-date copy when they download the book.
So now the only constraints remaining are time and financing. And that's where you come in.
How the funds will be used
The funds will help to pay for a professional copy-editor, hosting costs (for the website and the ebook distribution), printing and shipping the physical book, and the costs related to producing the other perks.
If this project happens to become overfunded, I will add more content to the book.
How far along your project is
The writing of the book is already in progress, and if this campaign is successful, it will speed up the process—a lot!
I estimate that I have between 3-5 months of work remaining to complete the book (version 1.0). I already have a detailed plan of the book and the actual Table of Contents seen in the ebook should not change a lot.
What will happen after release 1.0?
When the book reaches a "releasable" state, I plan to start accept change requests, translations, and more from the community (estimated December 2016 - January 2017) through the book GitHub repository.
By opening up the book's content, I hope to see the Agile Android Software Development book live on, continue to evolve, and be driven by the community.
At some point, I hope to see it become the defacto book for Android best practices.
Risks and challenges
The main risk is that I spend all the hours planned to work on the book before I've completed it.
If that happens, I will release what I have managed to complete on the git repository so others can come in and lend a hand.
Technically, there are not a lot of risks. I mean, the release pipeline for the book has been in place since day 1 (or 2). And, whenever I release new content, Jenkins (the gerbil in charge of building the book) happily spits out updated files on the book website—just seconds after I do a "git push" on the repository. So that part doesn't frighten me.Learn about accountability on Kickstarter
- (35 days)