As an individual I can decide which platform I would like to target with my
shiny new application, but when working for a company we have to target both
industry leaders at the same time. Although I like a good challenge, I am
really glad the mobile world now only consists of iOS and Android.
When I first started looking at building consumer applications, Blackberry
was still in the picture. My enterprise mobile experience consists of all
Microsoft technologies, but that was in a different lifetime using Windows
CE, Pocket PC, and Windows Mobile.
This book is a great book for looking at how some of the most commonly used
functionality compares across the Android and iOS environments. I have listed
the table of contents below to give you an idea of what topics are covered.
Part I: Overview of Mobile App Development
1. Why Mobile Apps?
2. App Design Issues and Consideratio... (more)
Designing developing natural user interfaces for touch and gesture on mobile
devices is not the same as web and desktop UI design and development. Mobile
devices are used in different contexts, and bring different personas to the
table. Having web and desktop UI design experience does not make you a
qualified mobile UI designer.
Although it was much worse back in the Dot Com Boom days, I still see
publication and commercial print designers trying to design web sites the way
they design a magazine. A lot of them finally figured out web design is
different, and we are now dealing w... (more)
When the agile movement re-cast the roles of the SDLC they did so with small
projects as the baseline of their experience. A typical minimal SDLC method
includes subject matter experts (those who execute the current workflow
activities), a Project Manager, a Business Analyst, a Software Architect, UX
specialists, Developers, DBAs, and Testers. A Scrum Team consists of a
Product Owner, the Development Team, and a Scrum Master. The typical SDLC
method responsibilities for activities, and the skills needed to get them
done, went from 8 roles down to 3. For small projects that is gre... (more)
As an enterprise and software architect the one thing I hate most about my
job is documentation, yet the importance of doing documentation on sizable
projects is what I find myself preaching about the most.
One reason I understand the importance of documentation is that I came from
an electronic engineering background. As an electronic engineer 93% - 97% of
my time was consumed doing proof of concepts and documentation. Almost all of
that time was documentation.
It was just my luck that my boss was an English grammar teacher before moving
into engineering. My documents came back v... (more)
This review is for two books. It is for Android: How to Program (2nd Edition)
and Android for Programmers: An App-Driven Approach (2nd Edition) . Why?
Because Android: How to Program (2nd Edition) includes the entire Android for
Programmers: An App-Driven Approach (2nd Edition) book.
Android: How to Program (2nd Edition) is in black and white and it also
includes a Java language overview/reference. This book is great for the
programmer coming from another language. Having the Java reference included
as the second half of the book comes in really handy. Lately I have spent
most of... (more)