[IxDA Discuss] Product suite design - single interface design or multiple?

[Esteban Barahona]

Have you considered using a common-widget that is shared among the
applications and is extended on-the-fly with each current app? Each app can
have a similar style, armony among similar apps but an identical/verbatim
copy is not recomended (I guess... I'm just starting)

What's the difference between B2B and B2C? I have read this concepts but not
what each character means...

I have thought about this too... searching for a general solution for suites
of apps.

2007/1/15, Wilson, Russell <Russell.Wilson at netqos.com>:
>
> I am faced with a problem that I'm sure many on the list
> have encountered.
>
> We have a suite of products (4 total) and a portal meant to
> act as a starting point for the products.  Each product has
> unique functionality and is used (and sold) standalone or
> in conjunction with other products.  Our products are B2B -
> enterprise applications.
>
> The issue (that keeps me up at night) is whether to apply
> one single interface design across all the products or give
> each product its own design.  Two sides have formed on this
> issue within the company and it's up to me to make the final
> call.
>
> Those for one single design argue consistency, ease of training
> and learnability (important to our customers by the way),
> and seamless integration with the portal.  Those for multiple
> design argue that a product should not be made to fit a design
> for the sake of the design, which could never lead to an optimal
> solution for the user, and so on.
>
> I am leaning towards multiple designs but I can see the value in
> a single design also.
>
> Any thoughts?





-- 
http://www.zensui.org