Mobile Applications: Architecture, Design, and Development

Paperback (Print)
Rent from
(Save 67%)
Est. Return Date: 07/27/2015
Buy Used
Buy Used from
(Save 41%)
Item is in good condition but packaging may have signs of shelf wear/aging or torn packaging.
Condition: Used – Good details
Used and New from Other Sellers
Used and New from Other Sellers
from $1.99
Usually ships in 1-2 business days
(Save 96%)
Other sellers (Paperback)
  • All (13) from $1.99   
  • New (6) from $26.88   
  • Used (7) from $1.99   


Delivering high-value mobile applications-from start to finish

This is the definitive guide to building successful mobile applications. It covers every facet of development and deployment, including business issues, architectural design, integration with existing web and legacy applications, and the management of mobile application development projects. It also presents three application case studies that demonstrate best practices at work in real projects. Coverage includes:

  • Requirements, design, development, integration, testing, release, and maintenance
  • "Mobilizing" existing application architectures
  • Building effective user interfaces for mobile applications
  • Fat-client and thin-client scenarios
  • Managing client-server data transfer
  • Securing mobile applications: authentication, encryption, and data self-destruction
  • Full Microsoft .NET code examples for cell phones, Pocket PCs, and Tablet PCs

Mobile Applications is indispensable for everyone who needs to deliver robust, high-value mobile solutions: project managers, technical leaders, architects, and experienced developers alike.

Read More Show Less

Product Details

  • ISBN-13: 9780131172630
  • Publisher: Prentice Hall
  • Publication date: 4/20/2004
  • Series: HP Professional Series
  • Pages: 368
  • Product dimensions: 7.00 (w) x 9.00 (h) x 1.00 (d)

Meet the Author

VALENTINO LEE is a Principal Solution Architect for Hewlett-Packard. Over the course of his career, he has worked as a developer, architect, technical leader and project manager on numerous legacy, web and mobile application development projects. He holds Master's degrees in Biology, Electrical Engineering, and Computer Science from Oxford, Columbia, and London Universities.

HEATHER SCHNEIDER formerly worked as a lead software developer for HP, designing and developing web and mobile applications using VB, Java, .NET and J2EE. She holds a Master's degree in Computer Science from Pace University.

ROBBIE SCHELL is a lead software developer at HP who has developed many diverse legacy, web, and mobile applications using C, C++, C#, VB, Java, .NET, J2EE, and other leading technologies.

Read More Show Less

Table of Contents

Foreword by Nick Grattan.


1. Introduction.

What Is Mobility?

Developing Mobile Applications.


2. Business Context.

Who Is Going Mobile?

What Do People Want to Do?

Why Mobilize Your Enterprise?


3. Mobile Application Architectures.




Connection Types.


Interesting Architectural Patterns.

Good Architectural Design Tenets.


4. Mobile Infrastructure.

Mobile Device Types.

Mobile Device Components.

Connection Methods.


5. Mobile Client User Interface.

User Interface.

Application Content.

User Experience.

Best Practices for Developing a User Interface.


6. Mobile Client Applications.

Thin Client.

Fat Client.

Web Page Hosting.

Best Practices.


7. Client-Server Data Transfer.


WAP and WML.

Synchronization Software.

RDA and Merge Replication.

SOAP and Web Services.

Message Queues.



8. Mobilizing Existing Application Architectures.

Evolution of Enterprise Architectures.

Anatomy of an Enterprise Web Architecture.

Considerations When Mobilizing Existing Applications.


9. Security.

Mobilized Enterprise Web Architectures.

User-to-Mobile Client Security Issues.

Mobile Client Security Issues.

Client-Server Communications Security Issues.

Existing Web Architectures and Back-End Systems Security Issues.


10. Mobile Application Development Management.

Project Management.



Code Development and Integration.

Integration and System Testing.

Deployment and Release Management.

Re-Evaluation and Reiteration.

Operations and Maintenance.


11. Mobile Museum Case Study.

Use Cases.


Client Detailed Design.

Server Detailed Design.

Mobilizing the Existing Application.




12. Mobile Biologist Case Study.

Use Cases.


Pocket PC Client Detailed Design.

Tablet PC Client Detailed Design.

Server Detailed Design.




13. Mobile Zoo Case Study.

Use Cases.


Client Detailed Design.

Server Detailed Design.




A. Further Reading.

B. Pocket Web Host Design.


Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star


4 Star


3 Star


2 Star


1 Star


Your Rating:

Your Name: Create a Pen Name or

Barnes & Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation


  • - By submitting a review, you grant to Barnes & and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Terms of Use.
  • - Barnes & reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously
Sort by: Showing all of 3 Customer Reviews
  • Anonymous

    Posted July 30, 2004

    Definitive Mobile App book

    This book is the definitive book for mobile .NET applications. Although the authors are very experienced programmers, from HP, I disagree with some of their opinions. For example, I think one-tier applications are more scalable than three tier applications, whereas the authors of this book think the opposite. Given that I do not agree on everything, the book is still complete, detailed, well thought out, and beyond doubt a first-rate coverage of mobile apps. I have not read a better book on mobile applications and especially if you are a .NET programmer, you will have a difficult time finding a better book on this topic. Aside from some architectural disagreement, I also did not like the UML sprinkled in. I HATE UML. The authors cover scenario based solutions and chose UML to do it. As much as I HATE UML, I really like the scenario based writing. Too many books just cover the same thing as the API reference. This book covers everything the documentation does not. For example, when SOAP is useful and when it should be avoided. I really believe that after reading the book, I will design better mobile applications and will have a broader view of mobile applications. Given that many mobile application projects fail or leave the project sponsor unsatisfied, this excellent book should be a definite read. It's also nice to see a mobile application book that really focuses on .NET. There are awesome facilities in .NET that blow away Java/J2EE. This book points them out. The book is not code heavy (after all that is obvious). Instead the book covers hard questions, like whether to use a data access layer or not and how to write a good one.

    Was this review helpful? Yes  No   Report this review
  • Anonymous

    Posted August 3, 2004

    I highly recommend this book.

    This is an excellent book for Architects, Developers, Project Managers, and anyone else who wants a detailed look at where the industry's Mobile Applications stand today. The book covers mobile application architecture, design, development and deployment. It also discusses business objectives, the development process of mobile application projects, integrating with existing web applications, and interoping with legacy applications. The authors do an excellent job of mixing just the right amount of high level businesses goals and low level technical information to make this book a good candidate for teams (Architects, Developers, Project Managers, etc.) to use as a starting point on first time mobile projects. It would get everyone up to speed and on the same page very quickly. I highly recommend this book. There are few books written this well on the market. It covers everything it says it does in the editorial review, and covers it in an in-depth easy to understand manner.

    Was this review helpful? Yes  No   Report this review
  • Anonymous

    Posted May 2, 2004

    Objective, vendor-neutral

    To a programmer, an IDE means an Integrated Development Environment. An environment in which you can program, with a lot of supporting utilities. Well, this book is also an IDE in its own right, where here IDE means an Integrated Design Environment, in the context of mobile applications. Aimed at the burgeoning field of smart portable devices, that usually communicate in a wireless fashion. The authors describe two main types of design efforts. The first is that of designing the UI for these mobile devices. Typically, there are severe constraints of screen size, resolution and power consumption. Care has to be taken because, after all, this is what the user sees. The second effort is in choosing and designing an architecture for this UI to interact with a server. Various issues are discussed, like how much 'intelligence' will reside on the device ('fat' versus 'thin'). And on the server, whether to have a 1, 2 or 3 tier system. The authors are at HP, and the book is part of the HP Professional Books series. Yet, search though I did, I could find no bias towards HP. In the narrative, there is only one mention of an HP product, OpenView, but this is in the context of listing various vendors' offerings. A very commendable, objective, vendor-neutral text. The design guidelines could be applied to most choices of current hardware, on the mobile device and on the server side. Plus, at the software level, you could choose a J2EE/J2ME or .NET approach. The book's advice supports both.

    Was this review helpful? Yes  No   Report this review
Sort by: Showing all of 3 Customer Reviews

If you find inappropriate content, please report it to Barnes & Noble
Why is this product inappropriate?
Comments (optional)