Date post: | 27-Jan-2015 |
Category: |
Technology |
Upload: | steven-hoober |
View: | 104 times |
Download: | 2 times |
1
The Trouble With All Those BoxesDesigning for ecosystems and people instead of screens and pages
@shoobe01 #mLearnCon
2
3
4
55
66
7
8
“I'm as interested in "channels" as a thing when designing ecosystems as I am in pages when reading a book.”
– Andrea Resmini
@resmini
99
10
11
12
13
“What we’re doing is trying to translocate information, and all the machine does is impair that process. Possibly infinitely. You have a choice over where it goes, and that’s it.”
– Martin Geddes
@hypervoice
1414
1515
16
1717
1818
19
• Design for Every Screen
• Mobile is More
• Design for Failure
20
• Design for Every Screen
• Mobile is More
• Design for Failure
21
Mobile First?
22
23
2424
25
26
27
28
29
30
Design for Every Screen
Blueprint
• Goals, objectives of the business • Legacy systems, business constraints• Put users on the paper• Task flow/Storyboard/ID/IA/…
Concept• Platform agonstic < - > Every
platform
31
• Design for Every Screen
• Mobile is More
• Design for Failure
3232
33
Wrong
3434
35
“…inequality is where the opportunities/challenges for design really are.”
– Andrea Resmini
@resmini
36
Every platform is a unique and special snowflake.
37
3838
3939
40
41
Mobile is More
Branch Design to Platforms
• Pick your platforms • Mark/strike interactions for each
platform• Design by widget/module• Embrace polymorphism• Design for re-use
42
• Design for Every Screen
• Mobile is More
• Design for Failure
4343
44
45
“when these subsystems are combined into larger systems, we enter the world of non-linear dynamics, complex interactions, chaotic behavior — and often, disastrous non-resilience...”
– Michael Mehaffy
tectics.com
46
47
4848
49
50
5151
52
Resilience Design Method:
1. Evaluate by widget
2. Determine user tolerance
3. Rate by severity
53
Design for Failure
Evaluate, avoid, fix
• Evaluate each component for pitfalls• Detrmine user tolerance• Rate severity, risk• Can you avoid the issue? • Can you mitigate the issue?
54
Philosophy, Not Process
55
Contact me for consulting, design, to
follow up on this deck, or just to talk:
Steven Hoober
+1 816 210 045
@shoobe01
shoobe01 on:
www.4ourth.com
56
57
Every platform is fragmented