How do we achieve a balanced solution for mobile content and applications? The iPhone has really raised the bar for mobile web browsing, and most mobile devices will soon have high quality browsing even if the screen remains small. Similarly, the growth area in handhelds are so-called ‘converged‘ devices: smartphones or wireless-enabled PDAs. Consequently, I propose it will be a plausible approach to start thinking of web apps as a delivery vehicle for mLearning.
Web standards for screen size started at 640 x 480, and have ranged through 800 x 600, to 1024 x 768. The iPhone has established a significant enough market presence to drive a variety of sites to create a version that accommodates the iPhone‘s resolution of 480 x 320. Phones can go down to as low as 160 x 160, so that might be your lowest common denominator, but I believe a safe bet could be 320 x 240 which is fairly common on a variety of devices. The new 800 x 600?
The point being, that thinking about small web apps may be the cost-effective and logical approach to provide mobile access, content. 160 x 160 is the new 640 x 480, etc. Already there are blogging tools for phones/mobile devices, and wikis are just web pages, etc. Web 1.0 is likely to be a viable solution, and the convergence of Web 2.0 and mobile is a promising place to play. Anyone game?
Laura says
I remember designing for 640X480. Even at that time, I thought it was a good idea to keep the code clean and use as little real estate as possible as I could see the dominance of mobile on the horizon. Plus, it would make the transition much easier. When do you think the tipping point to mobile will occur? Or has it already?
Clark says
Laura, your question triggered sufficient quantity of response I made it a separate post! Thanks for the prompt.