Book Image

PhoneGap 2.x Mobile Application Development HOTSHOT

By : Kerri Shotts
Book Image

PhoneGap 2.x Mobile Application Development HOTSHOT

By: Kerri Shotts

Overview of this book

<p>Do you want to create mobile apps that run on multiple mobile platforms? With PhoneGap (Apache Cordova), you can put your existing development skills and HTML, CSS, and JavaScript knowledge to great use by creating mobile apps for cross-platform devices.</p> <p>"PhoneGap 2.x Mobile Application Development Hotshot" covers the concepts necessary to let you create great apps for mobile devices. The book includes ten apps varying in difficulty that cover the gamut – productivity apps, games, and more - that are designed to help you learn how to use PhoneGap to create a great experience.</p> <p>"PhoneGap 2.x Mobile Application Development Hotshot" covers the creation of ten apps, from their design to their completion, using the PhoneGap APIs. The book begins with the importance of localization and how HTML, CSS, and JavaScript interact to create the mobile app experience. The book then proceeds through mobile apps of various genres, including productivity apps, entertainment apps, and games. Each app covers specific items provided by PhoneGap that help make the mobile app experience better. This book covers the camera, geolocation, audio and video, and much more in order to help you create feature-rich mobile apps.</p>
Table of Contents (19 chapters)
PhoneGap 2.x Mobile Application Development HOTSHOT
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
InstallingShareKit 2.0
Index

Some things to keep in mind


Often, the details are what matter. Here are some tips to help make sure you have not only a great-looking app, but a great-feeling app as well:

  • Avoid novel or undiscoverable interactions. Or, if you do want to use such interactions, try to also provide a second discoverable method for achieving the same thing. One could argue that the slide menu a la Facebook could be considered novel, but should the gesture not be discovered, the button that triggers the menu is highly visible and likely to be tapped.

  • Respect your user's expectations of what UI elements and gestures do. At first this seems obvious; you wouldn't send an e-mail by clicking on a trashcan. That said, there are plenty of ways you can do things that the user didn't expect, even in a subtle manner. Your user's expectations are highly specific according to the platform, so following your platform's HIG will help out significantly in this area.

  • Do blend in. By this I mean that your app should look like it belongs on your user's device. This means that your app should respect the HIG for the platform. It also means your app should give the appearance of being a native app. Failing to do so may cause your users to feel like your app is a second-class citizen on the device. By giving the appearance of being native, your app should also do its best to feel native – that is it should have speed and response close to that of a native app. (It may not always be easy, or even possible, on some platforms using PhoneGap. In this case, you should try to get as close as you can without impacting your project and its timeline.)

  • Be a perfectionist. By this I mean that you should make sure that all your objects align nicely, your textures blend seamlessly, images are scaled correctly (especially according to aspect ratio), and so on. This requires painstaking attention to detail, but in the end your app will look and feel better for it.

  • Be responsive. Whenever possible, avoid freezing the user interface. If you must freeze the UI, then put up an indicator to the user so they know their inputs will be ignored. When it comes to being responsive, this isn't simply being responsive to a tap on a button, but also with regards to scrolling performance. If an app scrolls in a herky-jerky fashion, the app will feel slow.

  • Sip your data. While your app may often be used on a Wi-Fi connection, don't forget about your users who may have to deal with a cellular connection instead. Not only might their connection itself be slower, but they are usually under pretty onerous data caps. Cache extensively. Avoid downloading what you've already downloaded. If it can be compressed, by all means, compress it. Alternatively, give your user an out – if your app is going to use a lot of data no matter what, you might want to let them disable the portions of your app that use a lot of data when on a cellular connection.