Interface Design Quotes

Readers usually ignore the typographic interface, gliding comfortably along literacy’s habitual groove. Sometimes, however, the interface should be allowed to fail. By making itself evident, typography can illuminate the construction and identity of a page, screen, place, or product.

Jobs's intensity was also evident in his ability to focus. He would set priorities, aim his laser attention on them, and filter out distractions. If something engaged him- the user interface for the original Macintosh, the design of the iPod and iPhone, getting music companies into the iTunes Store-he was relentless. But if he did not want to deal with something - a legal annoyance, a business issue, his cancer diagnosis, a family tug- he would resolutely ignore it. That focus allowed him to say no. He got Apple back on track by cutting all except a few core products. He made devices simpler by eliminating buttons, software simpler by eliminating features, and interfaces simpler by eliminating options. He attributed his ability to focus and his love of simplicity to his Zen training. It honed his appreciation for intuition, showed him how to filter out anything that was distracting or unnecessary, and nurtured in him an aesthetic based on minimalism.

Why can't you summon a command line and search your real-world home for 'Honda car keys,' and specify rooms in your house to search instead of folders or paths in your computer's home directory? It's a crippling design flaw in the real-world interface.

After all, as Edward Tufte once said, “Overload, clutter, and confusion are not attributes of information, they are failures of design.

User interface is the process of shifting from chaotic complexity to elegant simplicity.

An ugly system is one in which there are special interfaces for everything you want to do. Unix is the opposite. It gives you the building blocks that are sufficient for doing everything. That's what having a clean design is all about.

Effective gamification is a combination of game design, game dynamics, behavioral economics, motivational psychology, UX/UI (User Experience and User Interface), neurobiology, technology platforms, as well as ROI-driving business implementations.

Intuitive design happens when current knowledge is the same as the target knowledge.

As Susan Kare, designer of the original Mac interface, said, “You can’t really decide to paint a masterpiece. You just have to think hard, work hard, and try to make a painting that you care about. Then, if you’re lucky, your work will find an audience for whom it’s meaningful.

Methods containing hundreds of lines of code are fine if they have a simple signature and are easy to read. These methods are deep (lots of functionality, simple interface), which is good.

The software engineers who labored over the interface would have probably resorted to the standard lament: “RTFM”—“Read the (ahem) Manual.” For design thinkers, however, behaviors are never right or wrong, but they are always meaningful.

when designers use clean aesthetics to cover over a complex reality—to take something human, nuanced, and rife with potential for bias, and flatten it behind a seamless interface—they’re not really making it easier for you. They’re just hiding the flaws in their model, and hoping you won’t ask too many difficult questions.

The approach to digital culture I abhor would indeed turn all the world's books into one book, just as Kevin (Kelly) suggested. It might start to happen in the next decade or so. Google and other companies are scanning library books into the cloud in a massive Manhattan Project of cultural digitization. What happens next is what's important. If the books in the cloud are accessed via user interfaces that encourage mashups of fragments that obscure the context and authorship of each fragment, there will be only one book. This is what happens today with a lot of content; often you don't know where a quoted fragment from a news story came from, who wrote a comment, or who shot a video. A continuation of the present trend will make us like various medieval religious empires, or like North Korea, a society with a single book. The Bible can serve as a prototypical example. Like Wikipedia, the Bible's authorship was shared, largely anonymous, and cumulative, and the obscurity of the individual authors served to create an oracle-like ambience for the document as "the literal word of God." If we take a non-metaphysical view of the Bible, it serves as a link to our ancestors, a window. The ethereal, digital replacement technology for the printing press happens to have come of age in a time when the unfortunate ideology I'm criticizing dominates technological culture. Authorship - the very idea of the individual point of view - is not a priority of the new ideology. The digital flattening of expression into a global mush is not presently enforced from the top down, as it is in the case of a North Korean printing press. Instead, the design of software builds the ideology into those actions that are the easiest to perform on the software designs that are becoming ubiquitous. It is true that by using these tools, individuals can author books or blogs or whatever, but people are encouraged by the economics of free content, crowd dynamics, and lord aggregators to serve up fragments instead of considered whole expressions or arguments. The efforts of authors are appreciated in a manner that erases the boundaries between them. The one collective book will absolutely not be the same thing as the library of books by individuals it is bankrupting. Some believe it will be better; others, including me, believe it will be disastrously worse. As the famous line goes from Inherit the Wind: 'The Bible is a book... but it is not the only book' Any singular, exclusive book, even the collective one accumulating in the cloud, will become a cruel book if it is the only one available.

Usability, fundamentally, is a matter of bringing a bit of human rights into the world of computer-human interaction. It's a way to let our ideals shine through in our software, no matter how mundane the software is. You may think that you're stuck in a boring, drab IT department making mind-numbing inventory software that only five lonely people will ever use. But you have daily opportunities to show respect for humanity even with the most mundane software.

The paradox of impact is that while design shapes the world in profound ways, it is also being shaped by the world. Design as a process necessarily interfaces with many other systems to shape and redefine the world and our human experience within it. Designers and design in general is, however, uniquely situated to be critical mediators between the various entities, forces, and agendas that are constantly at work in developing the future that we collectively and individually want.

We must create more effective interfaces with innovations across the whole of society; rethink how policies are designed; change how intellectual property regimes are governed; and use R& D to distribute intelligence across academia, government, business and civil society. This means restoring public purpose in policies so that they are aimed at creating tangible benefits for citizens and setting goals that matter to people–driven by public-interest considerations rather than profit.

I write them to improve my productivity as a programmer. Making the quality assurance department happy is just a side effect. Unit tests are highly localized. Each test class works within a single package. It tests the interfaces to other packages, but beyond that it assumes the rest just works. Functional tests are a different animal. They are written to ensure the software as a whole works. They provide quality assurance to the customer and don't care about programmer productivity. They should be developed by a different team, one who delights in finding bugs.

If you need to visualize the soul, think of it as a cross between a wolf howl, a photon, and a dribble of dark molasses. But what it really is, as near as I can tell, is a packet of information. It’s a program, a piece of hyperspatial software designed explicitly to interface with the Mystery. Not a mystery, mind you, the Mystery. The one that can never be solved. To one degree or another, everybody is connected to the Mystery, and everybody secretly yearns to expand the connection. That requires expanding the soul. These things can enlarge the soul: laughter, danger, imagination, meditation, wild nature, passion, compassion, psychedelics, beauty, iconoclasm, and driving around in the rain with the top down. These things can diminish it: fear, bitterness, blandness, trendiness, egotism, violence, corruption, ignorance, grasping, shining, and eating ketchup on cottage cheese. Data in our psychic program is often nonlinear, nonhierarchical, archaic, alive, and teeming with paradox. Simply booting up is a challenge, if not for no other reason than that most of us find acknowledging the unknowable and monitoring its intrusions upon the familiar and mundane more than a little embarrassing. But say you’ve inflated your soul to the size of a beach ball and it’s soaking into the Mystery like wine into a mattress. What have you accomplished? Well, long term, you may have prepared yourself for a successful metamorphosis, an almost inconceivable transformation to be precipitated by your death or by some great worldwide eschatological whoopjamboreehoo. You may have. No one can say for sure. More immediately, by waxing soulful you will have granted yourself the possibility of ecstatic participation in what the ancients considered a divinely animated universe. And on a day to day basis, folks, it doesn’t get any better than that.

Pham Nuwen spent years learning to program/explore. Programming went back to the beginning of time. It was a little like the midden out back of his father’s castle. Where the creek had worn that away, ten meters down, there were the crumpled hulks of machines—flying machines, the peasants said—from the great days of Canberra’s original colonial era. But the castle midden was clean and fresh compared to what lay within the Reprise’s local net. There were programs here that had been written five thousand years ago, before Humankind ever left Earth. The wonder of it—the horror of it, Sura said—was that unlike the useless wrecks of Canberra’s past, these programs still worked! And via a million million circuitous threads of inheritance, many of the oldest programs still ran in the bowels of the Qeng Ho system. Take the Traders’ method of timekeeping. The frame corrections were incredibly complex—and down at the very bottom of it was a little program that ran a counter. Second by second, the Qeng Ho counted from the instant that a human had first set foot on Old Earth’s moon. But if you looked at it still more closely. . .the starting instant was actually some hundred million seconds later, the 0-second of one of Humankind’s first computer operating systems. So behind all the top-level interfaces was layer under layer of support. Some of that software had been designed for wildly different situations. Every so often, the inconsistencies caused fatal accidents. Despite the romance of spaceflight, the most common accidents were simply caused by ancient, misused programs finally getting their revenge. “We should rewrite it all,” said Pham. “It’s been done,” said Sura, not looking up. She was preparing to go off-Watch, and had spent the last four days trying to root a problem out of the coldsleep automation. “It’s been tried,” corrected Bret, just back from the freezers. “But even the top levels of fleet system code are enormous. You and a thousand of your friends would have to work for a century or so to reproduce it.” Trinli grinned evilly. “And guess what—even if you did, by the time you finished, you’d have your own set of inconsistencies. And you still wouldn’t be consistent with all the applications that might be needed now and then.” Sura gave up on her debugging for the moment. “The word for all this is ‘mature programming environment.’ Basically, when hardware performance has been pushed to its final limit, and programmers have had several centuries to code, you reach a point where there is far more signicant code than can be rationalized. The best you can do is understand the overall layering, and know how to search for the oddball tool that may come in handy—take the situation I have here.” She waved at the dependency chart she had been working on. “We are low on working fluid for the coffins. Like a million other things, there was none for sale on dear old Canberra. Well, the obvious thing is to move the coffins near the aft hull, and cool by direct radiation. We don’t have the proper equipment to support this—so lately, I’ve been doing my share of archeology. It seems that five hundred years ago, a similar thing happened after an in-system war at Torma. They hacked together a temperature maintenance package that is precisely what we need.” “Almost precisely.

Something refused to come into focus in my thinking. Indistinctly, as though in a fog, shapes moved toward me and retreated just beyond cognition. But that getting a hold of things is the uncertainty. As the Tractatus says right at the beginning, “The world is everything that is the case.” It seemed as though the Mammy≈Divas® were just like Steve Jobs, trying to have reality bent to their own wills. Objectively, the iPhone was a muddle of mysticism and logic—breakable glass, non-ergonomic design, lousy battery life, lousy irreplaceable battery, lousy headphone jack, lousy virtual keyboard, lousy email, lousy memory, lousy lice, etc., etc, and an interface that you had to adapt to by pretending as an article of faith that no adaptation was required. The Mammy≈Divas® promised a seamless racial interface—eternal blackness ordered and majestic. They put a benign face on their lust for panoptic power. They promised to discipline and punish with pancakes.