I've worked on a couple of projects like this. Basically you have a classic cost/benefit analysis infront of you:
Cost of Changing frameworks VS benefit of improved User Experience. Some things to think about: 1. If you're competitively selling this app you can argue that paying the price now ensures success later. 2. If you don't have direct competition, then determine end user influence on adoption of software, and use this as leverage. 3. If you're not in a competitve environment and the end users have little influence on adoption, then you can focus on data entry/manipulation/accuracy of input with the poor screen UI VS an enhanced UI. If none of the above arguments work, (or anything else), and you end up with the sh*tty framework, I totally agree with Gloria's previous post that incremental positive changes can go very far in making an app better, (and remember "a little better" is a lot better then "a little worse" ;) Rich -- Joseph Rich Rogan President UX/UI Inc. http://www.jrrogan.com ________________________________________________________________ *Come to IxDA Interaction08 | Savannah* February 8-10, 2008 in Savannah, GA, USA Register today: http://interaction08.ixda.org/ ________________________________________________________________ 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
