Head First Mobile Web

Appendix A. Leftovers: The top six things (we didn’t cover)

Ever feel like something’s missing? We know what you mean... Just when you thought you were done, there’s more. We couldn’t leave you without a few extra details, things we just couldn’t fit into the rest of the book. At least, not if you want to be able to carry this book around without a metallic case and caster wheels on the bottom. So take a peek and see what you (still) might be missing out on.

#1. Testing on mobile devices

Mobile testing sucks. There, we said it. There’s no way to sugarcoat it. When one phone model behaves quite differently depending on which carrier network it is on, you know you’re on the bleeding edge and you can’t assume anything.

Here are some of the things we’ve done to try to keep our sanity.

1. Start with valid code in a desktop browser.

   If it breaks in the desktop browser, it will also break on mobile. Might as well start where you’re more comfortable and the tools are better. Be sure to validate your code to help you find errors early.

2. Use mobile emulators and simulators.

   Nearly every mobile platform provides an emulator or a simulator. Maximiliano Firtman put together the ultimate list of emulators and simulators for his book Programming the Mobile Web. He updates the list regularly at http://www.mobilexweb.com/emulators.

3. Invest in a small number of devices.

   Buying a few phones is unavoidable. Which ...