0% found this document useful (0 votes)
3 views59 pages

Design and Development Best Practices

The document discusses the importance of design and development working together. It notes that design should consider performance, usability, and how things actually function in reality based on data. Development needs to understand design principles like consistency and avoiding special cases without reason. The document advocates for collaboration between designers and developers through techniques like checking each other's work and using common standards and guidelines to ensure successful products.

Uploaded by

Adan López
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
3 views59 pages

Design and Development Best Practices

The document discusses the importance of design and development working together. It notes that design should consider performance, usability, and how things actually function in reality based on data. Development needs to understand design principles like consistency and avoiding special cases without reason. The document advocates for collaboration between designers and developers through techniques like checking each other's work and using common standards and guidelines to ensure successful products.

Uploaded by

Adan López
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Design + Development

Gregory Raiz
Title
+
Presented by:
Features
Usability
Performance
Technology
Design
Features
Usability
Performance
Technology
Design
Design
Aesthetic Usability Effect
Aesthetic Usability Effect

How things look


It’s design!
Functional, Usable, Beautiful
2000 XP
Better design leads to ♥
Raizlabs
Creative Solutions
Better design leads to ♥
Design + Usability

Development
Something’s not right.
Slick Slow
Great Clunky
Smooth Janky
Awesome Buggy
Useful Confusing
Helpful Complex
Design Development
Slow
Clunky
Janky
Buggy
Confusing
Complex
Slow

Performance is a feature
Sub-Second
1 Second
3-5 Seconds
5+ Seconds
30 Seconds +
Clunky

Pixels and animations 



between the screens
Janky

Design for both the 



happy paths & thorny paths
Buggy

Quality is inversely related 



to the number features
Confusing

State and modality



are hard to design and predict
Complex

Compositions may not work if they 



weren’t designed with real data.
Complex

Die Zusammensetzungen können nicht funktionieren,


wenn sie nicht mit realen Daten entwickelt wurden.
Slick
Great
Smooth
Awesome
Useful
Helpful
Inconsistent
Non-standard
Special-Case
Gratuitous
API Limited
Platform Limited
Performance Constrained
Inconsistent

Things that look the same 



should act the same
Nothing
Profile
Menu
Non-Standard

Things that look system or stock



should act like they are system.
Special Case

Items should only behave 



differently if they are truly special
Gratuitous

Being fancy for no good reason


API or Platform

We can only display the data


or do what is possible
Performance Constraints

If we do this, things get slow.


Communication and Balance
Common Language

HIG (Human Interface Guidelines)


API Diffs
Designer Designs Developer Codes
Developer Checks It Designer Checks It
Traditional Waterfall Process
Users Only Experience Shipped Products
I don’t care what your spec says…
CODE WINS
Loading Indicators
Performance
Empty States
Error Conditions
First Run Experience
Etc. Etc.
Agile isn’t just for
developers

13
Agile isn’t just for
developers

3 3
7
Design + Development

Thank you.

@graiz

You might also like