This is a surprisingly good article. As a product designer of 10+ years (having worked at Facebook, Atlassian, and now Lyft), I would recommend anyone outside of the design field to read this.
It provides a much crisper picture of what modern designers workflow looks like than other resources.
Typically when these types of guidance are shared they're littered with more harmful advice than good. For example: "Look at what other apps are doing and copy it!" Except what another product is doing may not work for your product. The design of a final product isn't just the result of visual decisions, it's also driven by things like: business objectives, budgets, team size, time constraints, tech capabilities, target market size and demographics, etc.
So to have the article call attention to things like Dribbble being home to designs that are primarily "conceptual as opposed to the finished product when it comes to real applications" was refreshing.
Great read!
It provides a much crisper picture of what modern designers workflow looks like than other resources.
Typically when these types of guidance are shared they're littered with more harmful advice than good. For example: "Look at what other apps are doing and copy it!" Except what another product is doing may not work for your product. The design of a final product isn't just the result of visual decisions, it's also driven by things like: business objectives, budgets, team size, time constraints, tech capabilities, target market size and demographics, etc.
So to have the article call attention to things like Dribbble being home to designs that are primarily "conceptual as opposed to the finished product when it comes to real applications" was refreshing.
Great read!