WAP网站与移动网站的传统HTML [英] WAP Site vs. Traditional HTML for a Mobile Website

问题描述

如果您有一些社交网络应用程序，并且您希望用户使用移动设备与他们进行交互，那么您会使用WAP还是使用HTML的瘦身版常规网站？

我的思路是，由于所有可用的移动网络浏览器（Iphone，Opera Mini），WAP已经死亡或至少开始流血致人死亡。这是一个很好的假设吗？

另外，在选择想要开发哪种移动接入方式时，您应该考虑哪些受众群体考虑因素？ b
$ b

我确信我的目标设备。我很肯定我的用户会更现代，因此我们可以承担Windows Mobile，iPhone和Blackberry设备。

解决方案

WAP 2.0 = XHTML Mobile Profile。我假设你是指WAP 1.0和WML。现在，几乎所有的移动浏览器都支持XHTML MP（或一些近亲）。

有关移动开发的最佳实践，请参阅 dotMobi移动网络开发者指南。

我建议您可以使用WURFL等自动检测移动浏览器，并使用无线CSS为XHTML MP提供服务。我以这种方式为应用程序构建了一个移动前端，并且它在很多移动浏览器（手机，即opera，openwave，...）中运行良好。

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 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 dotMobi Mobile Web Developer's Guide.

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, ...).

这篇关于WAP网站与移动网站的传统HTML的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！