IT牛人博客聚合

Your app has too many settings, too many things to tweak. API endpoints? Colors of the rainbow? 100 different fonts and font sizes? Temperature in Kelvin? Switch the app to use Esperanto?

Kill the settings, kill them all.

Your Vision Is Your Software

You're the developer, build what you want. Your app should be an e

查看全文: http://www.udpwork.com/item/1729.html

Digital Post, my newspaper app for the iPad, uses a number of custom user interface elements to build out the full user experience. One of these custom components is a horizontal topic selector that you can swipe and also tap to select individual topics.

Original Concept

Facebook for iPhone was one of the first apps

查看全文: http://www.udpwork.com/item/1635.html

This site was first designed in early 2008, it was time to give it a fresh look.

Design

I went through a lot of revisions to this design, I think the header is on its 10th fully-polished and implemented version. The goal with this design was to present a more cohesive look and have a more traditional layout enabling

查看全文: http://www.udpwork.com/item/1596.html

NoSQL 生态系统

By Jonathan Ellis,系统架构师, Translated by Jametong

空前的数据量正在驱动商业寻找传统关系型数据库的替代方案,它已经为我们服务30多年了(今年5月份ACM刚刚给关系型数据庆祝40岁生日).总体来讲,这些替代方案就是目前知名的“NoSQL数据库.”

关系型数据库的基本问题是无法处理许多现代的工作负载.有三个具体的问题领域:向外扩展(Scale out)类似于Digg(3TB的绿色徽章数据)或Facebook(50T的收件箱搜索数据)或Ebay(总共2PB的数据)的数据集,单机性能限制以及僵化的概要设计.

商业上(包含Rackspace Cloud公司)需要寻找新的

查看全文: http://www.udpwork.com/item/1590.html

Apple's differentiator has been quality for a long time; beautiful industrial design coupled with an elegant user experience. Independent developers building Mac OS X apps know how high Apple's standards are because to build a really great app for the Mac it should act and feel as if Apple made it. Some developers go a

查看全文: http://www.udpwork.com/item/1141.html

During the search about Python singleton pattern, I discovered [ActiveState recipe 66531].

In this Borg Pattern, instances’ internal dictionary points to the same place, so all instances share the same state. Also, [Alex Martelli], the author of this recipe, has a interesting comment: Borg Pattern != Singleton

查看全文: http://www.udpwork.com/item/1099.html

There are three ways to get this job done.

1 Module Implementation

The easiest implementation is to use a module scope variable. Module is persistent and shared by all references through its life time, no matter how it is renamed or modified.

See this [stackoverflow post on Python singleton]. Xen Xend makes use of

查看全文: http://www.udpwork.com/item/1100.html

The underlying secret to beautiful user interface design is realism: making 2D objects on your screen appear to sit in 3D space with volume, surface properties and undulations that might appear in real life. These faux 3D objects have highlights and shadows just like objects on your desk might have, and they have textu

查看全文: http://www.udpwork.com/item/1143.html

Beak was an experiment, a way for me to do something new and be proud of it. It was my first application for the Mac and my first time using Cocoa. I never took C in college, I had to learn the Cocoa APIs, Objective-C, and C all at the same time. It was, and still is, a great adventure, and the adventure is just gettin

查看全文: http://www.udpwork.com/item/1144.html

这是工作间隙给弊厂做的一套海报。

为什么用“改变”作为关键词呢？是因为弊厂最近搬进了“百度大厦”，领导们认为这是一次“改变”，所以号召大家以此为题做做文章。

请鉴赏：

查看全文: http://www.udpwork.com/item/422.html

Design by Chris Messina

One of the largest remaining questions about the Apple slate device (aka, the iTablet, Mac touch, or my favorite, the iPod maxi) is its operating system. Why? Because the iPhone's main selling point is the App Store and last I checked, apps listed in the App Store only run on the iPhone OS. So

查看全文: http://www.udpwork.com/item/1145.html

Update: Changed the blog entry title to reduce confusion.

The iPhone is one big constraint — no keyboard, small screen, few buttons — so designing applications for the iPhone is an exercise in building smart, simple software. Bloated apps on the iPhone? You won't find many. Most applications pick one featu

查看全文: http://www.udpwork.com/item/1146.html

This morning a good conversation broke out in Twitter, which is not the best medium for real-time conversation, but hey we take what we get. It was concerning this article where Lukas Mathis said that for people who design user experiences, knowing how to code is detrimental to your ability to produce quality, user-cen

查看全文: http://www.udpwork.com/item/1147.html

这是为了跟keso的《继续跟白鸦抬杠：真正的需求》抬杠。虽然他所说的其实根本和我的观点没有冲突，是很好的补充。

事实上keso说“看看自己能做什么菜”，一定是基于“需求”而产生的。

任何一个产品价值的基础在于“有没有用？”，而不是怎么用。没有需求，或者需求搞错了，做什么菜都白搭，这是基础。就算福特没有“内燃机”这盘菜，只要他能确定“更快”的“更好的交通工具”，并从中发现其对用户的价值。他依然可以搞出另 外某种工具，需求会满足，期望可能有所降低，但产品依然会有价值。

但，如果不去了解真正的需求，只一味的盯住“内燃机”这件事，搞出来什么不靠谱的东西，天知道。这样的错误，乔布斯在搞“牛顿”的时候就犯过一次。很多纯技术研究者依然在犯&

查看全文: http://www.udpwork.com/item/280.html

这是《Design IT.》系列的第8篇，因为年前大家对于“装不装用户”和“创业，管哪个事最重要”讨论的比较热烈，所以跳到前面来写。

先来看一个老掉牙的故事：福特说，我在设计汽车之前，到处去问人们“需要一个什么样的更好的交通工具？”，几乎所有人的答案都是 ── 一匹“更快的马”。

“更好的交通工具”代表用户的“需求”；“更快的”是用户对于解决这个“需求”的“期望值”；“马”是用户对于解决这个“需求”的自假设“功能”。

一个初级的设计者，被用户牵着鼻子走。听到“更快的马”以后，会马上去设计一匹“马”。这个时候，无论在“马”上如何做创新，思路已经框死，结果很难突破。最终只能出来平庸的设计，很难长久很容易被模仿和超越，实现不了多大的

查看全文: http://www.udpwork.com/item/281.html

以前一直很喜欢 UCWEB，从 3.x 版本我就开始使用它，中间换了三台手机(SE K700C, Treo 650, SE M600i) 。不论是数字键盘，还是全键盘，还是触摸屏，UCWEB 都工作得比较令我满意。07 年时候因为 Treo 650 用 java 的 ucweb 容易死机，我还特意将手机换成了 M600i 。这个手机是个准全键盘，数字键左右两边按下会当不同的字母处理， UCWEB 6.2 以前的版本对这种准全键盘的也能响应，不需要切换到数字模式就可以按前进后退，用起来也还算舒服。

前不久在 ucweb 上看到了 6.3 beta ，赶紧下来使用，结果发现所有键盘快捷键都不好用了，需要费劲切换至数字键模式才成，而索爱

查看全文: http://www.udpwork.com/item/6164.html