blocks|key|4082242|text|WAP+2.0+=+XHTML移动配置文件。我猜你说的WAP指的是WAP+1.0和WML。现在几乎所有的移动浏览器都支持XHTML+(或一些近亲)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4082243|有关移动开发的最佳实践，请参阅dotMobi+Mobile+Web+Developer's+Guide。|offset|length|4082244|我建议你使用像WURFL这样的东西来自动检测移动浏览器，并用无线CSS为它们提供XHTML+MP。我用这种方式为一个应用程序构建了一个移动前端，它在许多移动浏览器(移动ie、opera、openwave等)上都能很好地工作。|4082245|entityMap|0|LINK|mutability|MUTABLE|url|http://www.networksolutions.com/learning-center/mobi-guide.pdf^0|0|F|10|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

WAP 2.0 = XHTML Mobile Profile. I'm assuming by WAP you mean WAP 1.0 and WML. Pretty much all mobile browsers these days support XHTML MP (or some close cousin).

For best practices on mobile development, refer to the <a href="http://www.networksolutions.com/learning-center/mobi-guide.pdf" rel="noreferrer">dotMobi Mobile Web Developer's Guide</a>.

I suggest you use something like WURFL to auto-detect mobile browsers, and serve them XHTML MP with Wireless CSS. I've built a mobile front-end for an application in this way, and it works well across lots of mobile browsers (mobile ie, opera, openwave, ...).

blocks|key|13866|text|您应该使用标准的XHTML+1.0+Strict或XHTML+Mobile配置文件。WAP很快就要死了(如果它还没有死的话)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|13867|http://en.wikipedia.org/wiki/XHTML_Mobile_Profile|offset|length|13868|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1D|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

You shoud use standard XHTML 1.0 Strict or XHTML Mobile Profile. WAP is going to die very, very soon (if it hasn´t already).

<a href="http://en.wikipedia.org/wiki/XHTML_Mobile_Profile" rel="nofollow noreferrer">http://en.wikipedia.org/wiki/XHTML_Mobile_Profile</a>

blocks|key|3235639|text|精简了HTML。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3235640|在我看来，WAP网站普遍都很丑陋，而且随着移动浏览器变得越来越强大，Ajax应用程序变得越来越有可能(而且可以很好地与人们有限的带宽/数据计划一起工作。|3235641|但是，如果你需要支持地球上的每一个移动设备，你可能不得不使用WAP。|3235642|您的目标设备是什么？一切，现代风格的手机，只有智能手机……？|3235643|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Slimmed down HTML. 

WAP sites are universally ugly, in my view, and with mobile browsers becoming more capable, Ajax applications are increasingly possible (and can work well with the limited bandwidth/data plans that people may have.

But if you need to support every mobile device on the planet, you may have to do something with WAP anyway.

What are your target devices? Everything, modern-ish phones, smartphones only....?

blocks|key|4082213|text|在开发了一些移动应用程序之后，我想说大多数客户端都支持HTML。当然，为这些客户提供精简版的HTML是安全的，这样就可以为您的应用程序设计通用的应用程序。然而，仍然有相当数量的客户端只接受WML作为其内容类型，因此HTML不能满足所有用户。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4082214|如果您阅读HTTP_ACCEPT标头，就可以确定客户端能够理解的内容。根据我的经验，尽可能使用HTML，必要时使用WML会更安全。|4082215|底线是，如果您不愿意支持站点的两个版本，请使用精简的HTML+(最好是XHTML)。如果除了HTML之外，你还能支持WAP，那么对于那些不理解HTML的客户来说，这是一个很好的退路。|4082216|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Having developed a few mobile applications I would say that the majority of clients support HTML. It is of course safe to serve these clients a slimmed down version of HTML in order to design your application for the common denominator. However, there is still a significant number of clients which only accept WML as their content type and thus HTML cannot satisfy all your users.

If you read the HTTP_ACCEPT header you can determine what the client is able to understand. In my experience it is safer to serve HTML whenever you can and fall back on WML when you have to.

The bottom line is that if you are reluctant to supporting two versions of your site, use slimmed down HTML (preferably XHTML). If you can support WAP in addition to HTML it makes a nice fallback for the clients which do not understand HTML.

blocks|key|4082287|text|请记住，WAP有其自身的优势，这是普通的HTTP网站在手机上浏览时所不具备的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4082288|主要的一个是你可以访问WAP计费，在那里你可以从可能没有信用卡的客户那里收取少量的钱。|4082289|此外，您还可以使用MSISDN+(移动电话号码)来唯一地识别和跟踪您的WAP站点的访问者。|4082290|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Do remember that WAP has strengths of it's own that normal HTTP sites browsed from mobile handsets do not posess.

A major one is that you can get access to WAP billing, where you can charge small amounts of money from customers that may not have credit cards available. 

Also you can use the MSISDN (mobile phone number) to uniquely identify and track visitors to you WAP site.

If you had some social networking applications and you wanted your users to interact with them using a mobile device would you use WAP or a slimmed down version of your regular website with HTML?

My train of thought is that WAP is dead or at least starting to bleed to death because of all the mobile web browsers available (Iphone, Opera Mini). Is this a good assumption?

Also, what kind of audience considerations should you take into account when choosing what kind of mobile access you wanted to develop?

I'm ot sure about my target devices. I'm pretty sure my users will be more "modern" so we can assume Windows Mobile, iPhone, and Blackberry devices.

WAP Site vs. Traditional HTML for a Mobile Website

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

如果你有一些社交网络应用程序，你想让你的用户使用移动设备与它们互动，你会使用WAP或带有HTML的常规网站的精简版本吗？我的想法是，由于所有可用的移动网络浏览器(Iphone，Opera Mini)，WAP已经死亡，或者至少开始失血过多而死亡。这是一个好的假设吗？另外，在选择您想要开发的移动访问时，您应该考虑哪种受众？我不确定我的目标设备。我非常确定我的用户将更加“现代”，因此我们可以假设Wind

问移动网站的WAP站点与传统HTML的比较
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问移动网站的WAP站点与传统HTML的比较EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问移动网站的WAP站点与传统HTML的比较
EN