You are previewing Mobile Design and Development.

Mobile Design and Development

Cover of Mobile Design and Development by Brian Fling Published by O'Reilly Media, Inc.
  1. Mobile Design and Development
    1. SPECIAL OFFER: Upgrade this ebook with O’Reilly
    2. Preface
      1. Who This Book Is For
      2. How This Book Is Organized
      3. Conventions Used in This Book
      4. Using Code Examples
      5. How to Contact Us
      6. Safari® Books Online
      7. Acknowledgments
    3. 1. A Brief History of Mobile
      1. In the Beginning
      2. The Evolution of Devices
    4. 2. The Mobile Ecosystem
      1. Operators
      2. Networks
      3. Devices
      4. Platforms
      5. Operating Systems
      6. Application Frameworks
      7. Applications
      8. Services
    5. 3. Why Mobile?
      1. Size and Scope of the Mobile Market
      2. The Addressable Mobile Market
      3. Mobile As a Medium
      4. The Eighth Mass Medium: What’s Next?
      5. Ubiquity Starts with the Mobile Web
    6. 4. Designing for Context
      1. Thinking in Context
      2. Taking the Next Steps
    7. 5. Developing a Mobile Strategy
      1. New Rules
      2. Summary
    8. 6. Types of Mobile Applications
      1. Mobile Application Medium Types
    9. 7. Mobile Information Architecture
      1. What Is Information Architecture?
      2. Mobile Information Architecture
      3. The Design Myth
    10. 8. Mobile Design
      1. Interpreting Design
      2. The Mobile Design Tent-Pole
      3. Designing for the Best Possible Experience
      4. The Elements of Mobile Design
      5. Mobile Design Tools
      6. Designing for the Right Device
      7. Designing for Different Screen Sizes
    11. 9. Mobile Web Apps Versus Native Applications
      1. The Ubiquity Principle
      2. When to Make a Native Application
      3. When to Make a Mobile Web Application
    12. 10. Mobile 2.0
      1. What Is Mobile 2.0?
    13. 11. Mobile Web Development
      1. Web Standards
      2. Designing for Multiple Mobile Browsers
      3. Device Plans
      4. Markup
      5. CSS: Cascading Style Sheets
      6. JavaScript
    14. 12. iPhone Web Apps
      1. Why WebKit?
      2. What Makes It a Mobile Web App?
      3. Markup
      4. CSS
      5. JavaScript
      6. Creating a Mobile Web App
      7. Web Apps As Native Apps
      8. PhoneGap
      9. Tools and Libraries
    15. 13. Adapting to Devices
      1. Why Is Adaptation a “Necessity”?
      2. Strategy #1: Do Nothing
      3. Strategy #2: Progressive Enhancement
      4. Strategy #3: Device Targeting
      5. Strategy #4: Full Adaptation
      6. What Domain Do I Use?
      7. Taking the Next Step
    16. 14. Making Money in Mobile
      1. Working with Operators
      2. Working with an App Store
      3. Add Advertising
      4. Invent a New Model
    17. 15. Supporting Devices
      1. Having a Device Plan
      2. Device Testing
      3. Desktop Testing
      4. Usability Testing
    18. 16. The Future of Mobile
      1. The Opportunity for Change
    19. Index
    20. About the Author
    21. Colophon
    22. SPECIAL OFFER: Upgrade this ebook with O’Reilly
O'Reilly logo

Strategy #1: Do Nothing

Our first of four multiserving strategies is to simply do nothing, or rather to wait for the technology to adapt to our principles—which actually isn’t as foolish as it might sound.

In 2005, the W3C created the Mobile Web Initiative (MWI) to attempt to bring the standardization it achieved with the desktop web to mobile. This was a difficult challenge, because the W3C had not issued any specifications for mobile standards. The announcement of the effort included an introduction from Tim Berners-Lee about the importance of “One Web,” a concept that has been a hotly debated topic in both the web and mobile communities ever since.

Initially, the W3C defined One Web this way:

One Web means making the same information and services available to users irrespective of the device they are using.

In other words, content should be published once and the device should be smart enough to know what to render; effectively, we wouldn’t need to do anything more than ensure that our content meets the content standards. This actually makes a lot of sense, as we’d be able to write once and publish everywhere to multiple devices and multiple contexts.

This do-nothing approach is actually a multiserving system in its own right: it detects devices, though without the need of a device database; it adapts content based on the requested device through thoroughly separated content and presentation and renders it to the requesting device. The multiserving system in this scenario is the browser, ...

The best content for your career. Discover unlimited learning on demand for around $1/day.