book

Mobile Applications: Architecture, Design, and Development

Name: Mobile Applications: Architecture, Design, and Development
ISBN: 0131172638

by Valentino Lee, Heather Schneider, Robbie Schell

April 2004

Intermediate to advanced

368 pages

7h 58m

English

Pearson

Read now

Unlock full access

Copyright
Praise for Mobile Applications: Architecture, Design, and Development
About Prentice Hall Professional Technical Reference
Hewlett-Packard® Professional Books
Foreword
Preface
Intended AudienceAcknowledgmentsDownload Site
1. Introduction
1.1. What is Mobility?1.1.1. Portability1.1.2. Usability1.1.3. Functionality1.1.4. Connectability1.2. Developing Mobile Applications1.2.1. Umbrella Considerations1.2.2. Fallacies About Mobile Application Development1.3. Summary
2. Business Context
2.1. Who is Going Mobile?2.1.1. Workers2.1.2. Consumers2.2. What Do People Want To Do?2.2.1. Communication2.2.2. Work2.2.3. Entertainment2.2.4. Education2.2.5. Location2.3. Why Mobilize Your Enterprise?2.3.1. Pros2.3.2. Cons2.4. Summary
3. Mobile Application Architectures
3.1. Client-Server3.1.1. Layers3.1.2. Tiers3.2. Client3.2.1. Thin Clients3.2.2. Fat Clients3.2.3. Web Page Hosting3.3. Server3.3.1. One-Tier Architecture3.3.2. Two-Tier Architecture3.3.3. Three-Tier Architecture3.4. Connection Types3.4.1. Always Connected3.4.2. Partially Connected3.4.3. Never Connected3.5. Synchronization3.5.1. Continuous Communication3.5.2. Store-and-Forward Synchronization3.6. Interesting Architectural Patterns3.6.1. Pattern Matrix3.6.2. Zero-Layer, Three-Tier, Always Connected Architecture3.6.3. Three-Layer, Three-Tier, Partially Connected Architecture3.7. Good Architectural Design Tenets3.7.1. Requirements3.7.2. Technology Independence3.7.3. High Performance and Availability3.7.4. Scalability3.7.5. User System Requirements3.8. Summary
4. Mobile Infrastructure
4.1. Mobile Device Types4.1.1. Pagers/RIM Devices4.1.2. Cellular Telephones4.1.3. PDAs4.1.4. Tablet PCs4.1.5. Laptop PCs4.1.6. Hybrids4.1.7. Capability and Cost Considerations4.2. Mobile Device Components4.2.1. CPU4.2.2. Operating System4.2.3. Memory4.2.4. Disk4.2.5. Batteries and Power4.2.6. Connection Ports4.2.7. Screen4.2.8. Keyboard4.2.9. Mouse, Stylus, Pen, and Voice4.2.10. Peripherals4.3. Connection Methods4.3.1. Wired4.3.2. Wireless4.4. Summary

5. Mobile Client User Interface
5.1. User Interface5.1.1. Device I/O5.1.2. Keyboard5.1.3. Mouse5.1.4. Stylus, Pen, and Touch-Screen5.1.5. Speech5.1.6. Scanner5.1.7. Screen5.2. Application Content5.2.1. Text5.2.2. Images5.2.3. Animation5.2.4. Sounds5.2.5. Movies5.3. User Experience5.3.1. Page Layout and Navigation5.3.2. Personalization and Customization5.3.3. Help5.3.4. Search5.4. Best Practices for Developing a User Interface5.4.1. Consider Hardware Dependencies5.4.2. Consider Software Dependencies5.4.3. Consider Absolute and Relative Sizing and Positioning5.4.4. Reduce Horizontal Scrolling5.4.5. Use Text Extensively5.4.6. Check Image Scaling5.4.7. Reduce Image Size and Quantity5.4.8. Reduce Animation5.4.9. Reduce Input and Typing5.4.10. Implement Separate Page Sets5.5. Summary
6. Mobile Client Applications
6.1. Thin Client6.1.1. Development Considerations6.1.2. Architecture6.2. Fat Client6.2.1. Development Considerations6.2.2. Common Use Cases6.2.3. Architecture6.2.4. Presentation Layer6.2.5. Business Layer6.2.6. Data Access Layer6.3. Web Page Hosting6.3.1. Development Considerations6.3.2. Architecture6.3.3. Presentation Layer6.3.4. Business Layer6.3.5. Data Access Layer6.4. Best Practices6.4.1. Consider Thin Versus Fat Versus Web Page Hosting6.4.2. Increase Code Abstraction and Reusability6.5. Summary
7. Client-Server Data Transfer
7.1. HTTP and HTML7.2. WAP and WML7.3. Synchronization Software7.4. RDA and Merge Replication7.5. SOAP and WEB Services7.6. Message Queues7.7. TCP/IP7.8. Summary
8. Mobilizing Existing Application Architectures
8.1. Evolution of Enterprise Architectures8.1.1. Client-Server Architecture8.1.2. Web-Enabled Service-Centric Architecture8.1.3. User-Centric, Single Sign-On Web Architecture8.2. Anatomy of an Enterprise Web Architecture8.2.1. Architecture8.2.2. Logical View8.3. Considerations When Mobilizing Existing Applications8.3.1. Architecture8.3.2. Users, Roles, and Entitlements8.3.3. Presentation Tier8.3.4. Application Tier8.3.5. Database Tier8.3.6. Existing Back-end Systems8.3.7. Authentication8.3.8. Enrollment8.3.9. Administration8.3.10. High Availability and Performance8.3.11. Scalability8.3.12. Security8.4. Summary
9. Security
9.1. Mobilized Enterprise Web Architectures9.1.1. Vulnerabilities9.1.2. Threats9.1.3. Mitigation9.2. User-To-Mobile Client Security Issues9.2.1. Authentication9.2.2. Smart Cards9.2.3. Biometric Authentication9.3. Mobile Client Security Issues9.3.1. Automatic Logout and Credentials Re-Entry9.3.2. Data Destruction9.3.3. Database Encryption9.3.4. Code-Embedded Usernames and Passwords9.4. Client-Server Communications Security Issues9.4.1. Communication Encryption9.5. Existing Web Architectures and Back-End Systems Security Issues9.5.1. Firewalls and Tier Separation9.5.2. Application Services and Port Lockdown9.5.3. Communication Encryption9.5.4. Database Authentication9.5.5. Database Encryption9.6. Summary
10. Mobile Application Development Management
10.1. Project Management10.1.1. Management Models10.1.2. Planning10.1.3. Team Resources10.1.4. Status Reports and Status Meetings10.1.5. Financials10.1.6. Environment10.1.7. Version and Change Management10.1.8. Training10.1.9. Common Managerial Headaches10.2. Requirements10.2.1. Requirement Types10.2.2. Gathering Requirements10.2.3. Documenting Requirements10.3. Design10.3.1. Design Documentation10.3.2. Design Considerations10.4. Code Development and Integration10.4.1. Coding10.4.2. Unit Testing10.5. Integration and System Testing10.5.1. Testing Process10.5.2. Testing Documentation10.5.3. Testing Considerations10.6. Deployment and Release Management10.6.1. Mobile Client Production Releases10.6.2. Server Production Releases10.7. Re-Evaluation and Reiteration10.7.1. Re-Evaluation10.7.2. Reiteration10.8. Operations and Maintenance10.8.1. Day-to-Day Operations10.8.2. Monitoring10.8.3. Backup and Restoration10.9. Summary
11. Mobile Museum Case Study
11.1. Use Cases11.1.1. Use Case Actors11.1.2. Existing Web Site Use Cases11.1.3. Mobile Web Site Use Cases11.2. Architecture11.3. Client Detailed Design11.4. Server Detailed Design11.4.1. Existing Presentation Layer11.4.2. Business Logic Layer11.4.3. Data Access Layer11.5. Mobilizing the Existing Application11.5.1. Architecture11.5.2. Users and Roles11.5.3. Presentation Layer11.5.4. Business Logic Layer11.5.5. Data Access Layer11.5.6. Authentication11.5.7. Enrollment11.5.8. Administration11.5.9. Mobile Device Support11.5.10. Presentation Layer Detailed Design11.6. Discussion11.7. Extensions11.8. Summary
12. Mobile Biologist Case Study
12.1. Use Cases12.1.1. Use Case Actors12.1.2. Mobile Client Use Cases12.1.3. Web Site Use Cases12.2. Architecture12.2.1. Overall Architecture12.2.2. Process Flow12.3. Pocket PC CLIENT Detailed Design12.3.1. Presentation Layer12.3.2. Business Logic Layer12.3.3. Data Access Layer12.4. Tablet PC CLIENT Detailed Design12.4.1. Presentation Layer12.4.2. Business Logic Layer12.4.3. Data Access Layer12.5. Server Detailed Design12.5.1. XML Web Service12.5.2. Presentation Layer12.5.3. Business Logic Layer12.5.4. Data Access Layer12.6. Discussion12.7. Extensions12.8. Summary
13. Mobile Zoo Case Study
13.1. Use Cases13.1.1. Use Case Actors13.1.2. Existing Web Site Use Cases13.1.3. Mobile Web Site Use Cases13.2. Architecture13.2.1. Overall Architecture13.3. Client Detailed Design13.3.1. Presentation Layer13.3.2. Business Logic Layer13.3.3. Data Access Layer13.4. Server Detailed Design13.4.1. XML Web Service13.4.2. Presentation Layer13.4.3. Business Logic Layer13.4.4. Data Access Layer13.5. Discussion13.6. Summary
A. Further Reading
A.1. BooksA.2. Online Resources
Bibliography
B. Pocket Web Host Design
B.1. ArchitectureB.1.1. Hosting Web PagesB.1.2. EnvironmentB.1.3. PWHCOMPB.1.4. PWHOSTB.2. Development ProcedureB.2.1. General ProcedureB.2.2. ExampleB.3. Summary

Overview

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.

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Publisher Resources

ISBN: 0131172638Purchase book

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills