So, yes…it’s the same Web. However, when developing for the mobile web we are
targeting very, very different devices. The most obvious difference is the screen size,
and yes, that will be our first problem. But there are many other not-so-obvious dif-
ferences. One issue is that the contexts in which we use our mobile devices are often
extremely different from where and how we use our comfortable desktops or even our
laptops and netbooks.
Don’t get me wrong—this doesn’t mean that, as developers, we need to create two,
three, or dozens of versions duplicating our work. This is where jQuery Mobile comes
to the rescue.
You don’t need to do anything special when designing for the mobile web
Almost every smartphone on the market today—for example, the iPhone and Android-
based devices—can read and display full desktop websites. Yes, this is true. Users want
the same experience on the mobile web as they have on their desktops. Yes, this is also
true. Some statistics even indicate that users tend to choose web versions over mobile
versions when using a smartphone. However, is this because we really love zooming in
and out, scrolling and crawling around for the information we want, or is it because
the mobile versions are really awful and don’t offer the right user experience? I’ve seen
a lot of mobile sites consisting of nothing but a logo and a couple of text links. My
smartphone wants more!
One website should work for all devices (desktop, mobile, TV, etc.)
As we will see, there are techniques that allow us to create only one file but still provide
different experiences on a variety of devices, including desktop, mobile, TV, and game
consoles. This vision is called “One Web.” Today, there are a lot of mobile devices with
very low connection speeds and limited resources—non-smartphones—that, in theory,
can read and parse any file, but will not provide the best user experience and will have
compatibility and performance problems if we deliver the same document we would
for the desktop. Therefore, One Web remains a goal for the future. A little additional
work is still required to provide the right user experience for each mobile device, but
there are techniques that can be applied to reduce the work required and avoid code
and data duplication.
Just create an HTML file with a width of 240 pixels, and you have a mobile website
This is the other fast-food way to think about the mobile web. Today, there are more
than 3,000 mobile devices on the market, with almost 50 different browsers (actually,
more than 500 different browsers if we separate them by version number). Creating
one HTML file as your mobile website will be a very unsuccessful project. In addition,
doing so contributes to the belief that the mobile web is not useful.
2 | Chapter 1: The Mobile Platform
剩余269页未读，继续阅读
yinkaisheng-nj
- 粉丝: 762
- 资源: 6231
我的内容管理
展开
最新资源
- 岩石滑动与断层冲击地压：声发射特征分析
- 新时代煤炭工业八大战略新取向剖析
- 开采强度对华亭矿区冲击地压危险性的影响分析
- 新安煤矿探采对比：影响安全生产的关键因素与技术支撑
- 210MW循环流化床锅炉引风机变频改造优化与节能效果
- 浅埋煤层开采沉陷预测：方法应用与影响分析
- 优化巷道过陷落柱支护方案：数值模拟与现场试验
- 坚硬顶板定向断裂爆破技术：安全高效采煤新方案
- 北航2019算法课作业解析：投资策略与凸子多边形优化
- 断层破碎带垮冒下堆积体边界抗力分布关键影响因素
- 哈拉沟选煤厂优化末煤系统提高效率与处理能力
- 瓦斯涌出影响下采动煤体蠕变失稳研究
- 提升煤矿装载效率的可控箕斗定量装载设备设计
- 水分调控下烟煤瓦斯吸附特性对比研究
- 重介质悬浮液密度控制硬件设计与选型探讨
- 坚硬顶板巷道支护参数设计：现场测试与数值分析
资源上传下载、课程学习等过程中有任何疑问或建议，欢迎提出宝贵意见哦~我们会及时处理！
点击此处反馈
