I am continually amazed at how many large scale B2C apps get this design pattern wrong. This template should help most. This applies to many large, well funded, well staffed consumer websites as well as enterprise application companies. You need to think of the entities in your domain, for taskrabbit it would be (taskers[people], tasks[projects]) for example. If there is any need for group of people, actions, objects, products, media files, than getting this correct is essential. If this solution is not inspiration enough; please contact us here: Contact
You are here: Home > UI design pattern for allowing per-user source-target mapping rule edits
UI design pattern for allowing per-user source-target mapping rule edits
Leave a Reply Click here to cancel reply.
You must be logged in to post a comment.
- Why Market Research? June 27, 2012
- Skyfollow Consulting Group: Beyond the Clouds June 29, 2012
- Social Media Chaos from tools, content, and brands explosion July 3, 2012
- Why Competitive Intelligence? July 3, 2012
- New Categories for New Products for Capturing Mindshare July 21, 2012
- The Data Driven Wheel of Growth January 24, 2017
- Your CRM data tells an incredible story that should reveal your future success (or demise) November 21, 2016
- CRM Reveal Solution Engagement October 21, 2016
- UI design pattern for allowing per-user source-target mapping rule edits July 1, 2014
- From Insight to Innovation: The CMO’s Role using the Digital Customer Journey May 27, 2014
advertising alignment analysis analytics apps behavior big data boundaries brand branding CMO CRM customer dashboard decisions design pattern diagram differentiation featured formula gaps identity marketing marketing channels measurement media messaging mindset relational return on investment roi schemes segmentation segmenting strategy targeting target marketing template transactional UI user interface UX value creation visualization visual proof
No comments yet.