Any research on best practices for legacy and redesigned app in a single UI

22 Apr 2009 - 3:34am
5 years ago
2 replies
623 reads
sudhindra
2004

Hi all,
We have recently revamped a major part of a financial application. But when
it goes live, parts of the legacy system would still be used. Does anybody
know of best practices about how to provide the UI? A single nav framework
with parts new and parts old? Or keep it separate as a new window in itself?
Also, it would be great if some one can point to any research/empirical data
on this... Thanks in advance for your help.

Best Regards,
Sudhindra V. | User Experience Architect
http://elegexp.blogspot.com
#perfection of art is concealment of art#

Comments

22 Apr 2009 - 8:52am
Jeff Geurts
2009

We have a similar problem for a complex web application. The approach
we have taken is to ensure that legacy tools are migrated whole,
rather than piecemeal, and we keep the global navigation consistent
in all cases, which we hope provides a familiar framework for users.

Local navigation is trickier, since it needs to be migrated with the
tool pages. We tried to avoid radical changes to local navigation,
while still providing small improvements, especially to usability.

The end result is fairly seemless; although seasoned or observant
users can easily spot the legacy tools, there are no jumps between
legacy and non-legacy pages WITHIN a given tool, so the transitions
are not jarring.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=41411

22 Apr 2009 - 10:45am
Preston McCauley
2009

This is not so much research as it is best practices I attempt to follow:

I really try to give a U.I. face lift to anything that is an older part of a legacy application. I know that sometimes time constraints and resources play a big factor in getting this to happen. This is especially true in massive applications where you may only be touching a small portion of the code.

Generally, it's going to depend upon your users and the expectation of the new functionality.

For example by opening a modal / pop-up etc and displaying older functions it may look inconsistent but in many cases does allow for the initial integration yo offer the most function and save time for the user?

If it does I will overlook consistency until I have some free moments to address the issues.

I'm actually facing this problem right now and while I would love to give an entire overhaul to a legacy application there is no time. I simply am re-skinning and attempting match color schemes.

It's going to boil down to:

Cost
Time
Value of the New Features Integration
Will the new version replace an older version
Consistent Experience

The the truth is you have to pick and choose and weigh your options. That being said really focus on the primary functions that are being integrated and try and figure out what "really" needs to change to enhance, or maintain the user experience.

food for thought.

Syndicate content Get the feed