by Scott on June 28, 2007
Making of a Web App is Synap Software’s step-by-step look at designing and developing a web app. In this article I share one iteration of an evolution of web application design layouts for PlaybookIQ.
I set up a flickr photostream to show screenshots as they evolved. Read the rest of this blog entry first, and then go check it out.
Key points of visual design for web applications stated as expectations from people using your application:
- Proximity: items near each other are related to each other..
- Relative size: larger elements are more important.
- Relative position: elements to the top and left are more important. Elements to the bottom and right are subsets of ‘parent’ elements above and to the left of them.
- Consistency: consistent fonts and colors make an application feel more reliable and well constructed.
- Inconsistency: an occasional inconsistency should mean that something is important or needed to be called out for some reason (e.g. red text when all other is black).
- Persistent elements like ‘home’ or ‘search’ provide confidence to roam around knowing they can always get back to familiar territory.
- Sign posts: let people know where in the app they are.
- Alignment: an application in which elements line up neatly vertically and horizontally feels more professional, is more trustworthy, and easier to use.
- Whitespace is easily understood as way to separate elements that are not directly related, while a line, shading or other elements must be processed by people scanning a page.
- Context is critical. Metaphors like tabs, sign posts, and grouping help people understand what to expect at a given point in the app and helps people focus on one thing at a time.
- Choice is painful and slow. People simply want to get something done. People do not want to be asked to perform the work of making choices. Keep navigation and activity choices to a minimum.
Read more...
Posted in Make a Web App, Synap Software: Design Decisions, Making of a web app, Web Application Design
[6]
comments
by Scott on June 18, 2007
Making of a Web App is Synap Software’s step-by-step look at designing and developing a web app. In this article we get a little bit ahead of ourselves and talk about styleguides.
Early PlaybookIQ Styleguide decisions:
- Use of the International Style
- Tab-based navigation
- Persistent search box
Read more...
Posted in Making of a web app, Synap Software: Design Decisions, Make a Web App | 7 trackbacks
[0]
comments
by Scott on June 14, 2007
In this, the sixth entry in the Making of a Web App series, we take a look at choosing a name. There are two steps: pick criteria and then pick a name that meets those criteria. In this entry we look at the first step: what makes a good web application name. Key points:
- Descriptive names are a wasted opportunity to be different and memorable.
- Emotive names rock.
- The first choice of name probably will not work, because:
- you need the .com.
- A chance to verbally repeat the name to someone is ok.
Everyone will have their own criteria for what makes a good web app name, depending on industry, target audience, and personal preferences. Here are the criteria I used for Synap Software’s sales process app.
A good web application product name is:
- short
- available as a .com
- associative
- emotive
- unique
- not functionally descriptive
- memorable
- ok to repeat
- one that you like and like to say
Let’s look at each of these criteria in more detail.
Read more...
Posted in Synap Software: Design Decisions, Making of a web app, Web Application Design, Make a Web App | 9 trackbacks
[0]
comments
by Scott on May 31, 2007
I understand about indecision
But I don’t care if I get behind
People living in competition
All I want is to have my peace of mind
- “Peace of Mind”, Boston
Avoid Indecision, Grant Peace of Mind
If you are a software designer, your goal should be to have every page have one purpose. This way you minimize user indecision, you find that the application is easier to explain, and by going through the excercise of this constraint you gain more confidence that your design achieves the primary purpose of the app.
Read more...
Posted in Synap Software: Design Decisions, Programming | 10 trackbacks
[9]
comments
by Scott on April 07, 2007

The Emergency entrance to our hospital is different than the medical building entrance. As with all hospitals, there is a big red EMERGENCY sign with an arrow directing you past the medical building entrance to the emergency entrance.
What I noticed today (on a scheduled trip to the doctor’s office – not the emergency room!) was that if in your rush to the emergency room you miss the big red EMERGENCY sign and turn anyway into the medical building entrance, there is immediately another big red sign that again directs you to the emergency entrance from the entrance to the main parking lot. And if you somehow miss that one, around the next turn is yet another big red sign pointing the frantic driver to the Emergency entrance. They are everywhere on the campus and around the parking lot.
You Can Always Get There from Here, Quickly
There is a main, direct route to the Emergency room. But even if you get off that route, you can always easily find it – no matter where you are.
Well designed software is the same way.
Read more...
Posted in Synap Software: Design Decisions | no trackbacks
[0]
comments