Implementing new User Interfaces - Pros and Cons
Sunday, December 23rd, 2007Let me make it simple. There are 3 ways of implementing a new User Interface over an existing user interface.
1. Overnight Implementation- Replace the whole existing UI with the new UI
2. Phased Implementation- Replace the existing UI part -by-part over a period of time
3. Parallel Run - Offer both existing and new UI parallely. Let the users choose what they want.
Overnight Model:
This is somewhat similar to a suicide model, the users may welcome it or they will ignore it. If the latter happens, then you are out of business. But if they accept, then you need not worry about anything. You need to put less effort in maintenance and more effort in new features or enhancements. Use this model, only if you are in the Prototyping stage or your user base is very very less. Most mobile phone UI experience fit this model.
Phased Implementation:
This is the safest bet. Develop the features+UI and implement it stage by stage. The users will feel only subtle changes at a given time. Finally when the whole implementation is over, your user base will remain intact and it will be a smooth transition. The problem here is, radical changes are not possible and innovation is limited. Use this model if your software/product has a large user base and you don’t want to lose ur revenue. Desktop OSes are common example for this model.
Parallel Run Model:
Develop the new user interface and offer it as an option. Ex. Yahoo mail’s new UI model. At any time user’s should be able to switch to either UI. The advantage being, people can opt the model which they prefer. The con is, your effort will double. Whenever you introduce a feature, you should make sure it works perfectly in both UI. Using clever coding and optimized frameworks, you can manage this.
- Rajesh Sundaram