从哪里开始智能手机Web开发? [英] Where to begin with Smartphone Web Development?

查看:148
本文介绍了从哪里开始智能手机Web开发?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

Ha all,

所以我一直在为我们的物业门户网站开发一个智能手机网站,我做的第一件事是看看他们在网上告诉什么但我发现很少。

So I've been taksed with developing a smartphone website for our property portal and first thing I did was see what lessons others had to tell online but I've found very little.

我不是建立一个应用程序,我正在建立一个网站,我在寻找做的,不关心到html,css,宽度/高度方法,javascript(是jquery在所有平台上玩得很好)和任何其他与这种平台相关的东西。

I'm not building an app, I'm building a website and I'm looking for do's and don't with regards to html, css, widths/heights approaches, javascript (is jquery going to play nice on all platforms?) and anything else that relvant to this kind of platform.

在其他人我非常喜欢 http://mobile.whistlerblackcomb.com/

尊敬的,
Denis

Regards, Denis

推荐答案

UPDATE

虽然下面的大部分文字仍然适用,但我现在会说 jQuery Mobile 提供了一个设计良好,可用的UI组件,同时还减轻了我过去使用WURFL的很多设备测试和检测问题。它仍然处于测试阶段,但似乎工作得很好。我建议检查一下。

While most of the text below still applies, I would now say that jQuery Mobile does a great job of providing a well-designed and usable set of UI components, while also alleviating a lot of the device testing and detection issues that I've used WURFL for in the past. It's still in beta, but seems to be working pretty well. I recommend checking it out.

开始时需要考虑的两个最重要的问题是:

The two most important issues to consider when getting started are:

1)设备检测

2)移动UI设计

我强烈建议您查看WURFL设备数据集:

For issue number 1, I strongly recommend looking at the WURFL device dataset:

http://wurfl.sourceforge.net/

使用此功能,您可以检索(部分)正在访问您网站的设备的功能,用户代理字符串。测试移动Web应用程序就像是来自地狱的浏览器测试 - 有很多不同的设备和浏览器组合,这是一个艰巨的任务。如果您可以专注于开发适用于功能相当的手机的一个或两个版本,请说:

Using this, you can retrieve (some) capabilities of devices that are accessing your site, using their User Agent string. Testing mobile web apps is kind of like browser testing from hell--there are so many different combinations of devices and browsers, that it's a difficult task. If you can focus on developing one or two versions for fairly capable phones, say:

1)最低300像素的宽度,带有声明的网络支持和触摸屏
2)与上述相同,但没有触摸屏

1) minimum 300px width with claimed "web" support and a touch screen 2) The same as above, but without a touch screen

您可以创建一个非常实用的网站,适用于大多数智能手机或应用手机 David Pogue 更准确地命名他们。对于实际测试,您可以尝试:

you can create a very usable site that will work for most "smartphones," or "app phones" as David Pogue has more accurately named them. For the actual testing, you can try:

1)列出所有的朋友和他们有什么样的手机
2)手机商店并使用这些手机测试您的网站

1) Making a list of all of your friends and what kind of phones they have 2) Going to a phone store and using those phones to test your site

,并且无论您做什么,当您收到不可避免的用户反馈关于损坏/他们设备上的内容较慢。

and, regardless of what you do, you'll have to be agile when you receive the inevitable user feedback about broken/slow content on their device.

关于UI设计,有几个问题。最简单的是漂亮的CSS。在这里,只要看看你喜欢的一些移动网站,并窃取他们的CSS。一旦你这样做,你基本上做规则的旧的网络开发,只是在一个小屏幕上。 ul将会变成漂亮的iPhone-y表等。

Regarding UI design, there are a couple of issues. The simplest one is nice looking CSS. Here, just look at some mobile sites you like and steal their CSS. Once you've done this, you're basically doing regular old web development, just on a small screen. ul's will become nice iPhone-y tables, etc.

更大的问题是移动网页的可用性。在很多方面,我们在移动网站开发的90年代的网络情况。我的意思是,我们工作没有成熟的设计模式。这使得移动Web开发真的很有趣,但它也意味着你必须准备好调整你的丑陋/破碎的UI,因为更好的想法发展。一个当前示例是您在很多移动网站上看到的全局导航/面包屑。有惊人的数量的人试图通过在移动应用程序中提供持久的导航工具(后退按钮)来模仿本机iPhone应用程序的行为。虽然这很漂亮,但它有一些问题:

The bigger problem is mobile web usability. In a lot of ways, we're in a 90s-web situation with mobile web development. What I mean is that we working without well-established design patterns. This makes doing mobile web development really fun, but it also means that you have to be ready to adjust your ugly/broken UI as better ideas evolve. One current example are the global nav/breadcrumbs you see on a lot of mobile sites. A surprising number of folks out there are trying to mimic the behavior of native iPhone apps by providing a persistent navigation tool (back button) within the mobile app. While this is kind of pretty, it has a few problems:

1)这是多余的,因为浏览器带有一个用户非常熟悉的后退按钮。这些全局导航存在于本机应用中的原因是它们没有免费的导航工具。

1) It is redundant, given that the browser comes with a back button that users are very familiar with. The reason these global navs exist in native apps is that they don't come with a free navigation tool.

2)网络是伟大的。您可以在其结构中的任何位置输入,离开和重新输入应用程序。假设用户通过您的应用程序采用线性路径,则会降低其网络性,使其相对于网络其他部分而言更加粗糙。

2) The web is great. You can enter, leave and re-enter "apps" at any point in their structure. By assuming that a user takes a linear path through your app, you are decreasing its webiness, making it a lot more crude relative to the rest of the web.

3)它打破。你可以在应用程序导航和浏览器导航指向相反方向的情况下(点击应用程序中的后退按钮通过应用历史记录向前移动),或者你假设一个带有javascript的后退按钮, t从应用程序的开始(电子邮件链接,书签)开始,或者你设置会话,这可能是一个很大的痛苦,只是为了复制你从浏览器获得的免费。

3) It breaks. Either you can get in a situation where the app nav and the browser nav point in opposite directions (hitting the back button in your app steps forward through the app history), or you fake a back button with javascript, which breaks if they don't start at the beginning of an app (emailed link, bookmark), or you set up sessions, which can be a big pain just to replicate what you get from the browser for free. Sessions are also vulnerable to brokenness (emailed links, bookmarks), and you're really not gaining much.

我想我的主要观点是:

1)不要忘记你在网上。网络很酷,浏览器很酷,可以使用。

1) Don't forget you're on the web. The web is cool, browsers are cool, make use of that.

2)不要害怕玩耍。这里没有很多完善的模式,所以你可能需要尝试一些自己的模式。

2) Don't be afraid to play around. There aren't many well-established patterns here, so you may have to try out some of your own.

这篇关于从哪里开始智能手机Web开发?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆