Channels ▼

Developer Reading List

, December 03, 2013 Ruby, Python, ASP.NET, Android development, PDF, and more.
  • E-mail
  • Print

Murach's Android Programming

by Joel Murach

The Murach series of tutorials are carefully designed volumes that aim to be self-paced tutorials. They present the principal topic as a series of bite-sized (almost always two pages) explanations that build on each other. Almost every nugget starts with the words "How to…" and this get-it-done orientation pervades the book. It's a supremely hands-on approach that works well. Judging by the reviews in various forums, this pedagogical style goes over very well. (So much so, that I'm surprised other publishers have not seized upon this approach.) While it might not be to everyone's liking, it is particularly well suited to topics that contain many sub-topics. And few topics today are more filled with smaller discrete and independent tasks than Web programming and mobile development. As the title suggests, the author is squarely attacking the latter (although, predictably, the topic does drift into the former).

Murach presumes only Java in the reader's skill set. He starts by explaining the basic operations: How to use Eclipse for Android development; how to move code to the device; testing; debugging; and so on. Much of the book is dedicated to layouts, widgets, themes, events, and the other core elements of the user experience (UX).

He then moves into more-challenging topics: services, notifications, location (and maps), and even running the SQLite database on Android. There is no scrimping on the contents here. The chapter on using SQLite, for example, is 40 pages in length — plenty to show how to do the necessary prep, create a database, access it, and add/update data. That is, exactly what you'd hope to get from a tutorial.

In the last few sections, the book explains how to deploy a finished app and publish it on Google Play.

The tone of the work is friendly and approachable. The explanations are clear, supported by many images for the UI examples (black and white images in the hard copy version, color in the eBook), and invariably backed by clear code with illustrative quality that is never lost in details of little relevance.

Overall, this is an excellent volume and almost certainly the best place to start for Java developers new to Android programming.






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.