Cohesive Design: Difference between revisions
Jump to navigation
Jump to search
(Created Page + Added Basic Sections/Info) |
(Minor Typo Fix) |
||
| Line 1: | Line 1: | ||
=Basics= | =Basics= | ||
*A Concept wherein all aspects of the designed thing "fit" / "flow" together | *A Concept wherein all aspects of the designed thing "fit" / "flow" together | ||
*An example would be why people choose the [[Adobe Software Suite]] | *An example would be why people choose the [[Adobe Software Suite]] | ||
**There is a very "clean work pipeline" | **There is a very "clean work pipeline" | ||
***All the files work together, and can easily be moved from one application to another | ***All the files work together, and can easily be moved from one application to another | ||
Revision as of 21:29, 3 March 2021
Basics
- A Concept wherein all aspects of the designed thing "fit" / "flow" together
- An example would be why people choose the Adobe Software Suite
- There is a very "clean work pipeline"
- All the files work together, and can easily be moved from one application to another
- There is a very "clean work pipeline"
- Another example is why some people use the Apple Ecosystem
- All the products (in the ecosystem) are compatible, and are often Foolproof (for instance the airpods pair automatically, unlike the slightly more complex pairing process needed for similar bluetooth in ear monitors)