UI design pattern for allowing per-user source-target mapping rule edits

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

Source target mapping rule UI

, , ,

No comments yet.

Leave a Reply