Dashboard > Fluid > ... > User Experience > User Experience Frankenstein
User Experience Frankenstein
Added by Daphne Ogle, last edited by Gary Thompson on Sep 27, 2007  (view change)
Labels: 
ux


Users think of Portals as one big product

Problem with existing products:

  • Products developed as individual portlets/tools
  • Many distinct users create content for there apps = inconsistent viewing experience
  • Integrating existing solution makes sense for efficiency but how does that effect the UX -- suddenly we have less control around the UX

Results to UX:

  • Workflow across tools/portlets is clunky at best; typically no possible
  • User has an inconsistent experience across the tools and portlets

Potential Solutions:

  • Components
  • Right API's - figuring out what these are is big!
  • Design patterns
  • Style guides
  • Dashboard/synoptic views 

Site running on a free Atlassian Confluence Open Source Project License granted to The FLUID Project. Evaluate Confluence today.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5 Build:#805 Apr 26, 2007) - Bug/feature request - Contact Administrators