|Professional Services||Second Signal||Presentations||Andrew's Blog||Support|
I spent the day working on a classic Notes Client application. It wasn't anything overly complex -- just a few views and forms, some action buttons and agents. Fortunately for me, UI design wasn't a priority on this. Its a single use case tool for one site-admin person to use as a time saver for an otherwise onerous task.
One thing I did notice, however, was that the expectation we have of the way things look and work has changed pretty drastically. We've learned to ignore the "frame" and focus on the content area of the application instead. That brings new challenges to classic Notes applications. Action buttons, a really innovative addition when they were added, now seem out of place and tucked away as part of the framing application rather than the content. A simple view by itself is almost impossible to make look right in current context -- you almost have to embed it on a page even though that tends to loose screen real estate.
I curious as to how many of you UI focused people have run into this kind of cross-contamination of design paradigms. Have you changed the way you build classic applications as a result of the way people are used to seeing applications on the web work? Do you do it that way even though the classic client is vastly more functional?
Please wait while your document is saved.