[apple] Web designers: you need a Retina MacBook Pro

易卡螺丝君 2012-07-13
只发贴 不说话
不过真的 全世界果黑思路都差不多
东扯西扯是最拿手的 ie6都能扯出来
英语不好的 自备机翻

引用
Earlier today, I tweeted:

If you’re a web designer, you really, really need to get a Retina MacBook Pro so you can see how bad your site looks on it and fix it.

I quickly got a lot of negative responses from people pointing out that Retina MacBook Pros are a small portion of the market, and other platforms are more worthwhile to test for, represented best by Stuart Frisby’s response:

There are still more IE6 users than Retina MBP users. Should I get a dell running Windows ME too?

Or Niranjan’s:

this is like trying to redo the site for IE5! Not enough users. Once it is more than 1%, will consider.

Jeremy Meyers takes it in a slightly different direction:

um no. we should not get to the point where we are designing sites around one unique piece of hardware. please.

Certainly, many other platforms are bigger than the Retina MacBook Pro market today. Here’s the difference:

How much bigger will the IE5 or IE6 market be in a year?

How much bigger will the high-DPI market be in a year?

Even though it’s a small market today (although don’t forget about the iPad 3), it’s inevitably going to increase substantially in the near future. Don’t you want to get ahead of that? Do you want your site to be ready the first time someone views it on a Retina screen, or are you OK with it looking like garbage for a few years until you happen to buy high-DPI hardware?

If you don’t frequently see your site on a high-DPI screen, you may not realize quite how bad it looks when any graphical assets show at 1X. This is the first problem you need to address.

You can do that without buying a Retina MacBook Pro, such as by testing on an iPad 3, simulating the iPad 3 with the iOS Simulator from Xcode, or enabling HiDPI mode on a large-screened Mac.1

If you do any of these alternate methods, you’ll probably be able to figure out which images need 2X versions. That’s a great first step that will get you much of the way there.

But if you can go further, you should. This is what I was talking about when I said that web designers need Retina MacBook Pros:

Without having and using a real high-DPI computer, all you can do is add high-resolution images for the design you already have. You’ll miss the nuance of what looks good and what works well on a Retina Mac, because you won’t really be using one. Even an iPad 3 isn’t the same.

It’s like designing iOS apps using only the Simulator without ever testing on a device. No respectable developer would ever ship an app that wasn’t extensively tested on real devices, because on the device, you learn that some of your choices just don’t look right or work well.

I’ve been using a Retina MacBook Pro for one week, only as a secondary computer,2 and I’ve already changed my font, redesigned my narrow layout’s header, and conditionally replaced an image with text. I’ve noticed that fonts, especially, respond extremely differently on the Retina screen: many of my old, non-Retina choices simply didn’t look good, and many fonts and metrics that were previously poor for screen use can be used nicely on Retina screens.

And I’m not even a web designer by trade — I just accidentally design my sites sometimes out of necessity.

Once you use real high-DPI hardware, you’ll see that there’s a lot more potential for design changes than just doubling your images.

Windows-using web designers, if such people still exist: I’m sure there’s something you can do to enable high-DPI mode on Windows. ↩

It’s possible to configure a Retina MacBook Pro up to nearly $4000, but the base model is a very good deal at $2200. It has 90% of the CPU performance of the highest configuration, same GPU, 8 GB of RAM, and a 256 GB SSD.

Since it’s my secondary computer, I didn’t need to max out everything, so I just walked into an Apple Store — no shipping delay — and bought the base model. Once Amazon gets them in first-party stock, they’ll be even cheaper.


http://www.marco.org/2012/07/05/web-designers-need-retina
boywukong 2012-08-27
这个问题我来说说作者的原义吧:

1.作者背景:
一个网站设计的从业人员
I just accidentally design my sites sometimes out of necessity(我只是偶然对网站做一些必要之外的设计)

2.作者谈论的问题:
当前网站要不要兼容高分辨率设备,有一些消极因素,下面我摘一段语义完整的话:

I quickly got a lot of negative responses from people pointing out that Retina MacBook Pros are a small portion of the market, and other platforms are more worthwhile to test for, represented best by Stuart Frisby’s response:
There are still more IE6 users than Retina MBP users. Should I get a dell running Windows ME too? Or Niranjan’s:this is like trying to redo the site for IE5! Not enough users. Once it is more than 1%, will consider.Jeremy Meyers takes it in a slightly different direction:um no. we should not get to the point where we are designing sites around one unique piece of hardware. please.Certainly, many other platforms are bigger than the Retina MacBook Pro market today. Here’s the difference:How much bigger will the IE5 or IE6 market be in a year?How much bigger will the high-DPI market be in a year?

(我发现现在有很多负面回应指出MacBookPro是一小部分市场,相比其他平台更值得去测试,最有代表性的如Stuart Frisby的回应:比起视网膜MacBookPro用户,还有更多的IE6用户,难道我应该也拿一个dell电脑装上Windows ME(去测试)么?或者如Niranjan所说:这就像试图重做IE5网站!没有足够的用户.一旦超过1%,会考虑的.Jeremy Meyers给出了一个稍微不同的(思考)方向:嗯不,我们不应该去围绕着一个独特的硬体设计网站.谢谢.当然,许多其它的平台是比视网膜的MacBook Pro目前市场上大.这里的区别是:IE5或IE6将来一年里会有多大市场的增长?高DPI的市场将来一年里会有多大市场的增长?)

也有一些积极因素,比如:虽然今天IPad3是个小市场,它不可避免的在不久将来有可能会大幅增加,你想你的网站被第一次用视网膜屏的人误认为看起来想垃圾好多年一样,而不是碰巧买了高DPI设备(才看起来是垃圾一样).
boywukong 2012-08-27
总的来说这是在做为一个设计师或者架构师的角度去考虑要不要为MBP兼容显示,还是为MBP另外开发一套网站的问题,跟果粉果黑没多大关系,跟IE6也没关系,人家只是说视网膜MBP用户访问还没有IE6访问的用户多而已.
我觉得人家分析的很中肯,并精准的指出给高清设备做兼容并不是简单的将图象分辨率加倍那么简单(还要有新做高分辨率字体,样式的变形等等,这是我猜的).
counters15 2012-08-27
高分辨率是大势所趋,大家都想要细腻的画面,越接近真实越好啊。只是现在受限于神马网络、硬件而已
dieslrae 2012-08-27
我只是关心玩游戏什么样的显卡能喂饱这个屏幕
counters15 2012-08-27
650M已经可以用D3喂饱这个屏幕了
dieslrae 2012-08-27
counters15 写道
650M已经可以用D3喂饱这个屏幕了

这得看什么游戏吧
counters15 2012-08-27
不是crysis2、地铁2033这种,kepler核心还能应付
卡夫卡 2012-08-27
强烈要求螺丝君晒MBPR,让我等吊丝仰望一哈
dieslrae 2012-08-27
卡夫卡 写道
强烈要求螺丝君晒MBPR,让我等吊丝仰望一哈

Global site tag (gtag.js) - Google Analytics