Much of the tension in product development and interface design comes from trying to balance the obvious, the easy, and the possible. Figuring out which things go in which bucket is critical to fully understanding how to make something useful. Shouldn’t everything be obvious? Unless you’re making a product that just does one thing – like a paperclip, for example – everything won’t be obvious. You have to make tough calls about what needs to be obvious, what should be easy, and what should be possible. The more things something (a product, a feature, a screen,...

I've come to avoid using the word "Simplicity" or its variants ("Simple," &c.) It means too many different things to different people.For example, my original land-line phone was simple:It's simple by eliminating extraneous use cases. It only handles one user scenario, the one that was the most common when it was invented. If we think of the number of affordances and the number of uses, this kind of simplicity lowers the number of affordances by lowering the number of uses. I call this kind of simplicity "Economical Design."There's another kind of simple, a kind of band-aid simple. You sta...

If you are a good developer and you’ve worked in bad organizations, you often have ideas to improve the process.  The famous Joel Test is a collection of 12 such ideas.  Some of these ideas have universal acceptance within the software industry (say, using source control), while others might be slightly more controversial (TDD).  But for any particular methodology, whether it is universally accepted or only “mostly” accepted, there are a multitude of organizations which don’t employ them.  There are many, many shops that do big bang testi...

We've been experimenting with app prices for quite some time and again and again we've noticed a funny effect:No matter what price we choose, we always make the same revenue.I attached two charts to illustrate that. I recently lowered the price of the iPad app (http://bit.ly/92xWv1) from 5 to 1 Dollars. At first the sales spike, then they even out to previous levels. Meaning: By cutting the price by factor 5, I am selling exactly 5 x more apps. Then we lowered the price of iA Writer for Mac (http://bit.ly/jfsHdZ) from 10 to 5 Dollars. And the exact same thing happened. There was a short i...

In preparation for a recent team offsite, I spent some time thinking about what I hold dear as a software developer. One idea I kept coming back to is the notion of balance. I see balance manifesting itself several ways in the work of a successful developer, some of which follow.Speed Versus QualityThe most obvious example is the balance of development speed and quality. When building software, it’s never a good idea to write code as fast as possible without any attention toward maintainability, just as it’s never a good idea to spend such an inordinate amount of time designing a...

Inspired by a talk I gave yesterday at the BOS conference. This is long, feel free to skip!My first real job was leading a team that created five massive computer games for the Commodore 64. The games were so big they needed four floppy disks each, and the project was so complex (and the hardware systems so sketchy) that on more than one occasion, smoke started coming out of the drives.Success was a product that didn't crash, start a fire or lead to a nervous breakdown.Writing software used to be hard, sort of like erecting a building used to be hundreds of years ago. When you set ou...

Over the past few years there has been an evolutionary shift in the world of software development.  Not very long ago, the dominant Software Development Life Cycle (SDLC) methodology was the Waterfall Method with very specific phases that separated the construction phase from phases like design and test. The software development industry, still very new, was striving to find a repeatable, predictable process for developing software.  The best model for this seemed to be the physical sciences, like civil engineering and architecture. Artifacts like detailed requirements, design docume...

Several days ago, one of our customers submitted a sample (SHA1: fbe71968d4c5399c2906b56d9feadf19a35beb97, detected as TrojanDropper:Win32/Vundo.L). This trojan hijacks  the hosts “vk.com” and “vkontakte.ru” (both social networking sites in Russia)and redirects them to 92.38.209.252, but achieves this in an unusual way. A common  method used to hijack a website and redirect it to a site of the attacker’s choice is to add an entry in the Windows hosts file located in the %SystemRoot%\system32\drivers\etc directory. However, when we open this file on an ...