收集客戶的要求,這些客戶認為她已經清楚了一切


2

我已經接受了為客戶建立網站的任務。她要求"必須擴展到移動設備"。甚至還不行,但我假設她瀏覽該網站的屏幕尺寸比我的屏幕尺寸小一點,並且她不滿意,因為該頁面為她顯示"錯誤"。例如,水平導航欄佔用了兩行,而文本並未按照她想要的方式沖洗;但是所有這些都可以在我的計算機上使用。

如何避免或解決此類問題?是否不可能用特定的目標平台開發網站?

例如,我使用24英寸顯示器但我朋友的筆記本電腦為13.3英寸,並且網站崩潰了,那麼它的編碼要求是什麼?

是否有任何文章鏈接可以向非技術人員解釋說"使網站在所有設備上都顯示相同"並非微不足道?另外,您如何向客戶表達這樣的問題:說"顯示相同"是沒有意義的,因為在大屏幕上的導航欄上有10個鏈接是有用的,但是將10個鏈接擠入智能手機屏幕是愚蠢的。

更新:回顧這一點,如果我們至少親自見過一次,那將真的很有幫助,因為根據我的經驗,僅通過電子郵件很難完成UX設計要求。

1

go for responsive website design. Responsive design will solve the problem that you are facing. GOOGLE responsive and you will get many articles. Read them and learn the trick.


4

Firstly, and unfortunately for you, I don't think the client has unreasonable expectations. What failed is the conversation between you and the client that voices those expectations. Most likely the client didn't know what they needed to ask for, which is where your expertise is supposed to come in (as the provider of development services).

I might be wrong but it sounds to me like you may have built the website either from scratch or using some sort of simple template which may have been ok in 1999, but is not fit for purpose given the thousands of different display sizes and densities available today. Most modern web development platforms (frameworks) provide tools and examples to build upon which adapt to the display size. Wordpress with a decent theme is also a great option to get you 80% of the way there with minimal effort.

Even so - just 'making the site responsive' is not a solution in its own right, it's just one of the many tools you can use to provide a solution. See for example '9 basic principles of responsive web design' for a reasonably non-technical visualisation of some of the problems encountered.

You and your client need to have a conversation about what actually happens on smaller or bigger screens. You need to explain the problems and allay her expectations of things looking the 'same but differently sized', and present ideas of what may happen instead. To back that up, of course you need to be confident of being able to provide these solutions, which is why a framework on which to build is likely your best bet.

The client doesn't know what to ask for and you are not a mind reader, so the best advice I can give is: keep the client involved, and keep a conversation going. It helps to avoid unwanted and untimely surprises for both you and the client.


3

Your situation is one most designers/developers have gone through once (at least some kind of disagreement with a client). So don’t worry! This is a typical example of what’s so important about good communication between you and your client. Not just to get clear what your client wants, but let them be aware of where their wishes come from and what other/better solutions can solve the problems they are facing. Having the requirements clear and written down in a contract can prevent you from disagreement on the final product.

These days you can expect from your client that they want to see the thing that they invested in to show it (off) on their phone or tablet. It is possible that you have good arguments not to have it scalable for these devices. But just saying that it's stupid is not very convincing, better have it substantiated with results from experiences or research (your own or from renowned sources).

How to solve this conflict? This really depends on what's on paper and how well you can get along with your client. But respect the situation and your client. Try not to be the one who is right, but to work towards a solution.

How to prevent this in the future? I think you have a lot to learn in web design/development. When you say...

squishing 10 links into a smartphone screen is stupid

...you should learn about information architecture or responsive design. EDIT: Because of one of your comments I now have a good sense of what you want to know:

"what questions do I ask the client and how specific must the answers be?"

In your situation first thing I would like to know is if it is relevant to spent another x hours to make it mobile friendly. So ask your client who will use the site, why, how often, where etc. or do some research yourself. Try to get a picture of the audience and what the websites purpose is to them. If it's just an informative site, you might want to find out what the most important information is to find quickly on a mobile device. If your client will benefit from people finding this information while on their way, you have a good stance in advising her to invest a bit more in a mobile version.

Good Luck!


1

I hate to sound patronising when I respond on StackExchange, but I have to say - you sound too inexperienced to be in this kind of situation with a client. You're asking questions that web developers should know (i.e. the basics of responsiveness). You're including "incorrectly" in a quote as though it's not the case. The fact is, it is incorrect, and yes you should be targetting as many platforms as possible, and testing it on as many resolutions and devices as possible. Is it a ball ache? Of course it is, we web developers now have to respond to arbitrary amount of screen sizes and choose from a plethora of media query and grid solutions, as well as taking into account technical capabilities of the devices in some cases, but it's now entirely necessary, and her expectations are pretty standard.

Going forward, how do you prevent this kind of situation? Learn how to develop responsive sites from the offset. And (most importantly), FORMALISE WHAT YOU AGREE ON! Whether it's a tech spec, or a contract of some sort, there should be a clear understanding (on paper) of what both parties are aware of. Cover your own back.