
Redesign of iTunes Store sign in screen by Nitin Garg. I enjoyed his commend: “It appears like they want me to forget my ID quite frequently!”
I have long wondered why those taking addresses require you to give your city and state. Whether it’s over the phone or through a web-form, why not just ask for the zip code, allow the computer to look up the city and state, and then simply confirm the result with the user?
I was pleased to experience such purchasing my new AppleTV a few minutes ago from apple.com.
One of the use cases that I’m most excited about is a ward choir director being able to create a play list of songs for an upcoming performance and then share that list with choir members who can then use the interactive player to learn their parts individually.
The music section on the Church website exists as a tool for music education and music consumption. It is designed to be a resource for individual members, those serving in music callings, and the general public. Training and information on the website will assist both new and experience musicians understand or refine fundamental principles and techniques. This section will also provide concise and inspirational information about music official policies, music in Church meetings, music in the home, and music in our personal lives. The current music section is one of the Church’s most-used online resources and contains a great deal of quality information. This content however, is difficult to navigate and consume and thus renders the tool more a novelty than an efficient resource and tool. The major goal of the redesign for 3.0 is that this tool be enhanced and refined into a powerful, interactive instrument, assisting in the discovery of music, development of talents, and strengthening of testimonies.

Here’s another teaser of some of the new stuff coming for lds.org. This screen is part of the music section.
“Love the idea of a signature designer—wouldn’t even have to invoice you.Snippet from a conversation in 37Signals Campfire app, mentioned on their blog.
He can just sign the check himself.”
“Edwin Land, inventor of the Polaroid camera, once said that his method of design was to start with a vision of what you want and then, one by one, remove the technical obstacles until you have it. I think that’s what Steve Jobs does. He starts with a vision rather than a list of features.”Fred Brooks, in interview by Wired’s Magazine’s Kevin Kelly about his new book The Design of Design
While there could be a better option, I don’t think a minus sign would have been an improvement. It is too close to the plus, with the only difference being the small nubbins on the top and bottom. The x, being rotated forty-five degrees, is distinctly different than the plus sign. That, in combination with the different bounding shape, provides ultimate contrast. Minus signs are also traditionally used for do-not-enter, don’t-do, or unavailable.
No, I haven’t done any testing to determine differences in individual monitor settings. I’d wager to be minimal however as most people don’t adjust their displays much (especially now with LCDs).

I have long appreciated the ability to copy layer styles by option + dragging them from one layer to another. For those like me that have also longed for the ability to copy layer styles to multiple layers, you are in luck—there is a way. Dragging the style is a shortcut for the copy/paste layer style option in the layer contextual menu and allows for the application of styles to multiple selected layers.

Working with a team of designers I’ve been getting this error a lot lately opening files in Photoshop. Digging through all the layers manually is a pain and on a few files I’ve not even been able to locate the offending text. Nic Johnson just made my day however pointing me towards the Replace All Missing Fonts feature under Type in the Layers menu.

The More Good Foundation, a non-profit organization promoting utilizing the internet to share the gospel, has launched a redesign of their website.
“Design, stripped to its essence, can be defined as the human capacity to make our environment in ways without precedent in nature, to serve our needs, and give us meaning in our lives.”Enjoyed this quote this morning by John Heskett in his book Toothpicks and Logos.
case study
LDS Interaction Framework
The Interaction Framework (IxF) is the result of a collaboration between members of the Interaction Design Team in Church’s Information and Communication Systems Department. The goal of IxF is to make development and prototyping faster, to ensure best practices in UI design and ultimately to save sacred tithing funds and make the user experience better for the folks who use our apps. We are excited to formally announce this project and introduce you to some of the work we’ve been involved in.
Simpler Interfaces, Smaller Scope
We intentionally left out some of the kinds of interactions that encourage apps to grow too big. Conventions like modals, drop-menus, and others often lead to intractably large and complex apps. Apps that would be better if they were smaller, and more manageable from a development perspective.

Best UI Practices
This seems obvious, but in reality, it takes a lot more determination than you might think. We simply won’t support every interaction out there. We pick the best way we know of to do something and forget the rest. Later, if we find a new interaction that’s better, we’ll flush the old one with antipathy and move forward.


Performance
Let’s be honest. As technologists, we’re pretty spoiled when it comes to bandwidth. We’ve probably blocked from our minds the painful memories of a 56 k modem. The problem is that even on high bandwidth connections, slow application performance can kill the user experience, no matter how pretty it is. We have and will continue to make speed a top priority in the IxF.


Forward Thinking
We’re looking to the future by supporting emerging standards like mobile/touch access and ARIA for accessibility, etc. We’re also heavily leaning on the latest advances in CSS3 and HTML5 as it makes sense to do so.

Two Styles, A Thousand Flavors
Naturally, we can bend this framework do to whatever we need for various projects, but out of the box, we will only support two fundamental approaches to UI design. We call them “Web Style” and “Desktop Style”

Web Style
Web style is what we’re used to for most apps and makes an appearance in mobile devices like the iPhone. It often means drilling into a page, accomplishing some action and then going back out again. It’s more hierarchical and simplifies apps by giving you only one thing on a screen at a time. It’s a great approach if your app is small or if it will be used by many people who are continuously new to the app.
Desktop Style
Desktop Style allows for a lot more on a page at a time, while keeping it organized and clear. Outlook is an example of this. It uses multiple panes/panels and can show a lot of data at a time.
Desktop style is great for users who don’t mind a little more complexity in return for speed. It also helps maintain context by keeping the user on one screen as much as possible. That said, it also works great for some simple apps as well, like a calendar or address book.
Master/Detail is your Friend
So one of the most helpful things you can provide to a user is context. Master/Detail is a handy pattern for providing this because it’s an “instructive” interface. It allows the user to see a set of data, click on one and see its details while keeping the dataset on the screen. It helps keep the user from being disoriented in any way.
We like this pattern so much, we’ve added significant support for it in the IxF with three patterns we support for data sets: Tables, Lists and the Finder component. All three of these provide hooks for working within the Panel component.
Some of the hooks we added are keyboard (arrow) navigation and built in fetching of data via AJAX to the detail panel of a layout.

Conclusion
We’re excited about the momentum we have behind this project and the success we have already seen internally as it is being implemented. We are also eager for the family of applications that will be arriving soon through new development and re-signing and the usability and research and development benefits it will provide. We intend to keep you posted on our work.

Here’s a glimpse of us at work. We meet each morning for a design review, printing out our work from the day before, and run it through the gauntlet. The team works together to ensure consistency and feeds off of each other’s ideas. The whole is indeed greater than the sum of any parts would could produce on our own. Once designs are flushed out and approved, they are moved out into the hallway for reference for us and for content and development teams after hand-off.
To the side of our meeting space, we have a row of desks with low dividers that allow of instantaneous and effective collaboration. Our developers and content teams are immediately down the hall and across the cubicle wall. Physical proximity, tactile, analog conversations and design explorations, and being surrounded by our product is crucial for a project of this scale.
![]()
Good article by Neven Morgan about designing icons and the various sizes required for iOS. I was especially interested in what he mentioned about resolution independence and how it’s not possible to have a single source file for an icon.

Just stumbled across designer and photographer Steph Goralnick. Excellent work. The energy in her photography is amazing.
case study
Playing catch-up on the web
It continues to perplex me how so many basic interaction conventions did not make it onto the web. With each browser revision, we’re slowly improving experiences online, but so much of it is simply catch-up and not new innovation. Sure, it was born as a method for structuring and sharing documents, but once we started building things with it that involved interaction, why didn’t we at least start with what we knew thus far? Simple patterns designed decades earlier are slowly starting to show up on the internet but so many are still not even technologically possible.
It’s unfortunate because it limits the internet’s potential. By requiring experienced users to learn new behaviors, requiring users to deal with a sub-set of features, or lowering standards and expectations by providing new users with a sub-par experience, we are doing them a great disservice.
Avoid pagination
Nowhere else but on the web do we paginate through data. I can imagine why this convention was utilized: bandwidth will always be an issue for applications that do not store data locally. Perhaps that can be improved with caching and pre-fetching anticipated content. Whether the data is there or not however, why can’t we pretend that it is? Consider the continuous-scroll (such as Bing’s image search) or load-more (such as Twitter) conventions. Data, especially tabular data, is a list. You’re reading down columns. Paginating left-to-right makes little sense, especially when you start sorting the columns. Even if you have to break the data into chunks and paginate, a vertical metaphor makes much more sense than horizontal. Avoid pagination, but if you must employ it, make it top, bottom, up, and down, like a window showing you a portion of a long list.
Filter instead of search
While it doesn’t work for massive data sets such as the entire web, stop making users search for content. Imagine a photo gallery application that launches with a blank screen and nothing but a search bar. It seems ridiculous, but why then do we approach most data sets in the same fashion? An application has been launched for a specific purpose. Assume the most common task and present it to the user. If the entire dataset is not local, load the first sub-set. Instead of requiring the user to search blindly to find what they want, let them filter down the data set. In many instances this can be done with javascript in the browser (client side or even through a remote call) and can be substantially faster than searching and then wading through results.
Master/detail and edit mode
Another convention that has plagued web applications since their inception is edit mode. It’s amazing how much time this small workflow has wasted. Browse, select, load, edit, save… browse, select, load, edit, save… again and again. Why refresh the page? What if you’re not sure which record you want? It can be much more simple to allow the user to arrow up and down through a list with details or with content appearing to the side! Second, if the application is for working with data, the fields should be editable, or provide an option to toggle in and out of edit and view mode on an application-level. Most desktop software doesn’t have view mode. Why does the web? Apple’s new iPad, which implemented the master/detail convention as a standard through it’s interface, is gratefully inspiring the use of this convention now in many applications.
Keyboard navigation
Make sure that users can navigate your application quickly and efficiently. Start by ensuring that your tab order is set and that you can effectively move between all form elements. Arrowing up and down through lists and data tables is crucial. Help your user out by allowing them to jump to the top and bottom of lists with page up and down. Allow them to expand and collapse details with the left and right arrows. Select items with the space bar. Other advanced keyboard shortcuts can include jumping between columns, toggling panels, and moving in and out of modes. There are a few javascript libraries and scripts that make implementing these a snap. Ensure that you are careful to manage focus, however, so you don’t conflict with typing. Some shortcuts can be as simple as single letter keys (as with Gmail) but most should require a modifier. I recommend both control and option/alt together for cross-browser compliance.
Control input and avoid validation
Lastly, I would like to discuss input. This area is improving greatly, especially with some of the new input types coming with HTML 5, but it still amazes me how many forms contain bare input fields. Users hate filling out forms, but they hate error notices worse. Why not anticipate their mistakes? Why not correct them inline as they work? If the field is for a credit card, why accept any character besides integers? If a code has to be in a specific format, then provide a hint and mask the input as it is keyed in. Auto-fill delimiters and spaces so the user doesn’t have to type them. Use Ajaxax to immediately validate fields that must be unique instead of after the user has filled out and submitted the entire form. Provide feedback inline, next to the problem. Size fields so that they indicate the amount of text that should be entered and limit them with the maxlength attribute.
Conclusion
Looking back, we have come a long way. Today’s web is a much better experience than it was a decade ago when we first started laying out pages and submitting forms. Giving credit where it is due, the masters of the web have done amazing, creative things with the tools available to them. But we must continue to challenge the archaic metaphors that were born out of technological limitations or the lack of interaction as a text-formatting medium grew into a software platform. We’ve solved most of these interaction issues long ago. We’ve been using them for decades on the desktop. It’s time to stop playing catch-up and to start building software right. We should be building on what we know and then making it better. Your application will be more intuitive and familiar. Your users will thank you.

This is a preview of the front page of the news and events section coming in the new lds.org. It will be up on the beta site in the next few weeks. It will provide an aggregate of articles and new content being published on the site and by official Church news services.
All available church music will be cataloged in a database, tagged and indexed for efficient searching and retrieval. Where permissible by copyright and resources, each song shall be accompanied by a Finale score file, sheet music (PDF), the sound track (MP3), the sound track with vocals (MP3), a MIDI file, and guitar tab (PDF).
The library will provide a gallery to browse books, collections, and playlists. A global search will allow users to query the database for songs against title, topics, scriptures, artist, lyricist, meter, and tune name. Search results will be a dynamic, unnamed playlist. Selected songs may be played in batch or added to playlists (new or existing). Playlists may be sort, shuffled, and narrowed through dynamic source lists. Individual songs may be played, downloaded (sheet music and audio file), and loaded individually for additional features (such as the interactive player) directly from any playlist. Individual songs will include an interactive sheet music player (as available), pagination (through current playlist), sharing and download options, meta information, related video performance and training resources, lyrics, and a historical summary.
posted by wade on Thursday, Aug 26, 2010