1. Modified from slides provided by Joseph Sant & Ann Cadger

2. Online/Desktop Web vs. Mobile Web Similarities Mobile Web Design Challenges Advantages The Mobile Web Ecosystem One Step at a Time

3.  Mobile uses same “plumbing” as the Desktop Web  Same general tools are used:  HTML/CSS/Javascript  Dynamic Pages using JSPs, PHP, ASP.Net  XML  HTTP and HTTPS used for Transport  Same networks are used..  For Mobile…At least one link in the transport of requests and content between the user's device and the content server is over the air

4.  Display Size… Smaller  Battery Life… Shorter  Memory  Stringent memory restrictions  Impacts amount of data that can be stored  Network  Slower transfer rates  WAP gateway can have size and content limitations  Latency (measure of time delay) Latency  Calculated either one-way (source  destination) OR round-trip (source  destination  source)  Well designed web sites try to reduce impact of latency by reducing number of round trips to fetch a page WAP: Wireless Application Protocol

5. Some of the challenges for Mobile Web might disappear over time. Which of the items mentioned on the previous slide would probably remain an issue and which will probably become less important?

6.  First Layer: device hardware  Second Layer: operating system  Third Layer: applications and mobile web

8.  Sending web signals  Near real-time content updates that push data directly to the phone (timely updates)  Push content  Server-side push communication allows sending of information to the browser regardless of back-end server technology  Queue forms online  Automatically queues pages for submittal when user re- enters coverage  Can include web feeds using the built-in RSS function  Access GPS functionality  Create widgets  Offers all the benefits of web development while also permitting access to all the API’s and content stored on the device API: Application Programming Interface

10. Features of the Mobile User (repetitive now, bored now, urgent now)

11. Small Screen. Difficult Input. Less powerful processors. Many other important issues.

12. Bandwidth Latency Cost

13. Original markup of content often altered at the carrier's server by a transcoder For a more in-depth overview of transcoder issues: Chapter 12 – How to Play Well in the Mobile Ecosystem Beginning Smartphone Web Development / Books 24x7 / ISBN: 9781430226208 / 2009

14. This is the same web as for online/desktop clients. Content servers are able to detect if a request is coming from a mobile device and act accordingly.