Afternoon, I'm developing a UI for a tool we have. I've built a wireframe version that is kind of dynamic, where you drag and drop things into a central area where you are configuring something. When you have your configuration built, you send it off, you can even schedule it or save it for later.
This is part of an existing piece of software. Currently they do some other things that are similar using wizards. They want to do this in a wizard as well. While the processes are similar, they are not the same. I feel like the dynamic version I have wireframed is more intuitive than a procedural wizard. But I'm open to looking at both, I want to do what is best for the user. So the big question is when is it appropriate to use a wizard in an interface? If anyone has any good resources on that, I'd appreciate it. I did find this article which is good: http://blog.componentoriented.com/2007/10/wizard_ui_dysfunction/ But I'd like to do some further research. I want to say I heard somewhere that a wizard is essentially a lazy way to design, but I cannot locate (or verify if it is true.) Welcome any thoughts. Thanks! Tom -- Marooned - A Space Opera in the Wrong Key! http://www.maroonedcomic.com ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
