Mobile Applications: Architecture, Design, and Development

Mobile Applications: Architecture, Design, and Development

ISBN-10:
0131172638
ISBN-13:
9780131172630
Pub. Date:
04/20/2004
Publisher:
Prentice Hall
Select a Purchase Option
  • purchase options
    $27.77 $49.99 Save 44% Current price is $27.77, Original price is $49.99. You Save 44%.
    icon-error
    Note: Access code and/or supplemental material are not guaranteed to be included with textbook rental or used textbook.
  • purchase options

Overview

Mobile Applications: Architecture, Design, and Development

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.

Product Details

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

Table of Contents

Foreword by Nick Grattan.

Preface.

1. Introduction.

What Is Mobility?

Developing Mobile Applications.

Summary.

2. Business Context.

Who Is Going Mobile?

What Do People Want to Do?

Why Mobilize Your Enterprise?

Summary.

3. Mobile Application Architectures.

Client-Server.

Client.

Server.

Connection Types.

Synchronization.

Interesting Architectural Patterns.

Good Architectural Design Tenets.

Summary.

4. Mobile Infrastructure.

Mobile Device Types.

Mobile Device Components.

Connection Methods.

Summary.

5. Mobile Client User Interface.

User Interface.

Application Content.

User Experience.

Best Practices for Developing a User Interface.

Summary.

6. Mobile Client Applications.

Thin Client.

Fat Client.

Web Page Hosting.

Best Practices.

Summary.

7. Client-Server Data Transfer.

HTTP and HTML.

WAP and WML.

Synchronization Software.

RDA and Merge Replication.

SOAP and Web Services.

Message Queues.

TCP/IP.

Summary.

8. Mobilizing Existing Application Architectures.

Evolution of Enterprise Architectures.

Anatomy of an Enterprise Web Architecture.

Considerations When Mobilizing Existing Applications.

Summary.

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.

Summary.

10. Mobile Application Development Management.

Project Management.

Requirements.

Design.

Code Development and Integration.

Integration and System Testing.

Deployment and Release Management.

Re-Evaluation and Reiteration.

Operations and Maintenance.

Summary.

11. Mobile Museum Case Study.

Use Cases.

Architecture.

Client Detailed Design.

Server Detailed Design.

Mobilizing the Existing Application.

Discussion.

Extensions.

Summary.

12. Mobile Biologist Case Study.

Use Cases.

Architecture.

Pocket PC Client Detailed Design.

Tablet PC Client Detailed Design.

Server Detailed Design.

Discussion.

Extensions.

Summary.

13. Mobile Zoo Case Study.

Use Cases.

Architecture.

Client Detailed Design.

Server Detailed Design.

Discussion.

Summary.

Appendices.

A. Further Reading.

B. Pocket Web Host Design.

Index.

Customer Reviews

Most Helpful Customer Reviews

See All Customer Reviews

Mobile Applications: Architecture, Design, and Development 4.7 out of 5 based on 0 ratings. 3 reviews.
Guest More than 1 year ago
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.
Guest More than 1 year ago
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.
Guest More than 1 year ago
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.