This document is a presentation about design engineering given at the Swift Conf in Cologne, Germany. It discusses: 1. What design engineering is, which combines traditional design, design thinking, and computational design by encoding design decisions using computer code. 2. The philosophy of design engineering, which is that the human experience, not the code itself, should be the focus. Speeding up iteration cycles by reducing steps in the process is also important. 3. How to create a culture of rapid prototyping where design works directly with engineering to find people who build as part of the design process and remove unnecessary steps.

1. Swift Conf
Cologne, Germany

2. Hi, I’m David.
A bit about me.

7. ScienceWonderArt

11. One Medical iOS Rise iOS One Medical Android

13. Design
Engineering
With Swift & Xcode

14. Raise your hand if…

15. We'll go over
1. What Design Engineering is
2. Philosophy
3. Culture
4. Process & Execution Opportunities

16. This talk is for
people who…
- love prototyping
- collaborate and want to pair with designers
- who love hacking and playing around
- want to work closer with designers who like
working I code

17. What is Design Engineering?

18. Traditional
Design
Design
Thinking
Computational
Design

20. “When you can do both (design
and code), you can do things that
no one else can do. Technology
companies that innovate tend to
have these unique people.”
—John Maeda

21. Computational design is the application of computational
strategies to the design process. While designers
traditionally rely on intuition and experience to solve
design problems, computational design aims to
enhance that process by encoding design
decisions using a computer language. The goal isn’t
to document the final result necessarily, but rather the steps
required to create that result.
Computational design is the application of computational
strategies to the design process. While designers
traditionally rely on intuition and experience to solve
design problems, computational design aims to
enhance that process by encoding design
decisions using a computer language. The goal isn’t
to document the final result necessarily, but rather the steps
required to create that result.

24. Should Designers
Learn to Code?
Absolutely!

25. Philosophy

26. Code is not the ends to the means.
The human experience is.

27. Speed up the iteration cycles by
reducing the number of steps in
the process.

28. “The number one thing you can do to be productive is to reduce
the iteration cycle.”
—Izzy Fraimow

29. WireframeDefine Ideate Interface Design Handoff Engineer

30. Make great design decisions
with engineering constraints

32. Prototype to de-risk projects

33. Inspirato

40. Culture

41. Remove as many steps as
possible

42. Rapid Prototypers

44. Design works directly
with engineerings

45. Find people on your team who
build as part of the design process.

46. Process and Execution
Opportunities

47. Wireframing With Storyboards

50. Style Guides in Xcode

51. Playgrounds

53. Build Prototype Apps

55. Build in the real app

57. Experience Prototyping

62. • See constraints as something empowering, not
restrictive
• Use code to creatively solve design problems
and iterate with designers
• Build early, but quickly and get ready to throw it
away
• Be a champion for your designer on what is
possible
Conclusion

63. Questions?

64. Thank you.
davidhoang.com | twitter.com/davidhoang |
github.com/davidhoang | david@davidhoang.com
http://bit.ly/swiftconf-dh