Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Enabling Design for a Complex Reality

Florian Plank
November 07, 2014

Enabling Design for a Complex Reality

Responsive Design was the reaction of creators on the web to cope under the mobile revolution. Exponentially growing fragmentation in screen resolution and density, processing power and memory, input devices and bandwidth pushed classic design approaches to it’s limits.

With the rise of the ‘internet of things’, the second coming of Augmented Reality and the ‘ubiquitous browser’ we have reached an unseen level of UI complexity. — Strategic design for this new reality requires better tools than box models and Photoshop.

Prototypes to the rescue! — The web and the browser as platform have become truly ubiquitous and allow us to build prototypes for a large variety of web and non–web environments with a well understood, progressively developed and comparably simple technology stack in very small time frames. Design for complex circumstances becomes transparent, tangible and before all else — it becomes fast again.

This talk will explore our approach to design through prototyping, show why we believe that prototypes are the way to go and explain how we’re using a technology stack selected for change to our advantage.

Florian Plank

November 07, 2014
Tweet

More Decks by Florian Plank

Other Decks in Design

Transcript

  1. ”If good design tells the truth, poor design tells a

    lie, a lie usually related to the getting or abusing of power.” ! ROBERT GRUDIN
  2. ”We can only see a short distance ahead, but we

    can see plenty there that needs to be done.” ! ALAN TURING
  3. 1. Web technology (HTML, CSS, JavaScript) 2.Meta languages (Haml, Slim,

    Sass, CoffeeScript) 3.Development stack built on interpreted languages (Ruby, JavaScript) Speed
  4. 1. Deployed to publicly available servers with no dependencies on

    other systems 2.Accountability of the design 3.Accessible through modern and widely available browsers / no prerequisites 4. Higher availability of experts 5. Lower learning curve to build the skillset up Transparency
  5. 1. Different takes on features – support for branching and

    merging through SCM (Git) 2.Visual variations for e.g. map skinning, app skinning or condition-based permutations 3.Variations of UI features per device/client Variations
  6. 1. Multi-screen prototypes 2.Various input methods (touch, indirect, sensory) 3.Communication

    between devices (e.g. location sharing via a socket server) 4. Technology embeds Extending the browser
  7. 1. Tangible design process 2.Present design intent clearly or even

    bypass steps like wire framing 3.(Very) short iteration cycles 4. Enable user testing or validation early on 5. Possible to utilize web analytics to track user behaviour, detect potential pitfalls and identify opportunities from data with less resources Validation