A quality library means team members have the information they need at their fingertips. Choosing usable components that work smoothly for users becomes the developer’s path of least resistance.
It takes a push from the library creators, but once it’s completed, the value seems to be immediate: teams can start to discuss what works and what doesn’t in current designs, laying out a vision for future development.
What do teams put into their design pattern descriptions?
- Pattern Name
- Description
- Context of Use
- Where to Use it
- How it Works (with visual aid)
- Specifications
- Related Patterns
- Competitive Approaches
- Source Code (quite rare)
- Usability Research
- Discussion
Leave a Reply