In his latest book, Dino Esposito walks through the myriad of mobile design decisions for business, appropriately titled Architecting Mobile Solutions for the Enterprise.

The work starts from a high-level, breaking through many of the current myths that surround mobile device development including which platforms to build on (hint: it depends on your user base and budget) to where to start coming up with good UX design (hint: it depends on form factors). Because the book takes an approach that’s a deliberative one, if you’re a developer or project manager looking for a simple answer, you may be turned off by the more rigorous approach Esposito recommends, precisely because there is no one-size-fits-all result. If you’re looking for a “only develop on Android” or “stick with iOS” response, you’ll leave disappointed, as Esposito reviews the benefits of all the major platforms, as well as devices that aren’t even smartphones.

Beyond the basics, Esposito’s approach delves deeply into the processes of how to develop useful applications, and here both developers and project managers will benefit from reading. From gathering good use cases to paying close attention to screen real estate, each page was a great reminder of the items that should be driving mobile development. The only negative I realized as I read through the easy prose was that, in theory, this sort of development process should’ve taken place years ago with the *web* work and design. If shops are only now thinking about what “customers” want, rather than blinking text and flash-based games, they’re going to have a big gear shift to move into mobile.

This, then, is the conclusion that Esposito reinforces throughout the book: shops that have a mature development cycle focused on customer needs will be able to leverage mobile solutions to deliver value to them. By contrast, organizations that are merely reactive will build a sub-par application for a single platform and garner ill-will. Mobile, thus, is the chance to get things right for many organizations that haven’t leveraged their development as they should’ve in the past. Whether they use a mobile-designed website, or a full-featured application to achieve their goal, savvy organizations would do well to read through this volume before they embark on a mobile strategy.

Related Blog Posts

Microsoft Azure - The jump to Hyperscale

There’s really no better way to describe yesterday’s Azure announcement except to say that everything is getting bigger and better. Before we discuss new announcements let’s look at where we are now. Per this excellent Ars Technica Article, Azure is already massive: 600,000 servers per region More than 11 million total servers Moving forward, Azure […]

Chromeless YouTube Videos for Responsive Pages

By default, embedded YouTube videos are contained in a player chrome that contains video controls and branding. While developing our new responsive video tips page, we wanted a clean visual style with the following attributes: Video player that expands and contracts responsively Display a high definition version of the video Deliver the video in a […]

Microtagging with Drupal and

Out of the box, Drupal 7 and 8 provide support for microtagging using RDF. What does this mean, why should you use it, and how can you customize it to model the objects on your site?

Using Icons in Web Development: The move to SVG

Background SVG, Scalable Vector Graphics, is an XML format for 2D graphics. As the name implies, a document in SVG format can scale to any size, effectively filling up any size container. Also, being a vector based format means that each portion of the graphical image is actually comprised of primitive parts, called “paths.” These […]