Mobile Applications: Architecture, Design, and Development: Architecture, Design, and Development

By Valentino Lee

The miniaturization of PCs in the form of Pocket PCs, Tablet PCs, and other mobile devices has provided new ways for users to interact with computers. This has led to a need to deploy and re-deploy... This description may be from another edition of this product.

• Format: Paperback
• Language: English
• ISBN: 0131172638
• ISBN13: 9780131172630
• Release Date: April 2004
• Publisher: Prentice Hall
• Length: 368 Pages
• Weight: 0.55 lbs.
• Dimensions: 0.9" x 7.0" x 9.2"

Customer Reviews

Concepts of Mobile Application Development.

This book shows how to go for designing and developing mobile applications. This book is designed for all audiance, who are in mobile application development or would like to go for it. Person who haven't started mobile application and wants to know more about mobile technology can also go for this book. This book cover all aspects of mobile application development starting from designing to deployment. Also cover the topic to how to prepare existing applications to support mobility. It also covers the security issue, which is very much important aspect of all application development. This book is very good book who are taking start up project in mobile area and have very good experience in windows and webbased application. They just need to have concept or quick guide that they can find here in the book. Overall, This is good book to have in your book shelf.

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.

Definitive .NET Mobile Applications 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.

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.