When we're designing an interface, the patterns that we pick are sent out into the world and our users spend time and money to interact with them. Some patterns are heavier than others to implement (and some are badly implemented), and that means our users wait longer and pay more (actual money, real Rands!) to use our products.
We'll look at a range of common patterns for web-based User Interfaces, and analyse what the time and money cost of them are, based on how they're likely to be implemented (in HTML, CSS, and JavaScript). We'll discuss how these patterns might contribute towards the overall Front-end performance of a web site or app, and how we can chat more with Front-end devs to get the best possible results for our users.c
Steve Barnett works as a code mentor at Project codeX (http://www.projectcodex.co/), and as a freelance Front-end developer and User Experience person. He’s a bit addicted to meetups: you can usually find him helping out with RailsBridge Cape Town (https://railsbridgecapetown.org/), Cape Town Front-End Developers (http://www.meetup.com/ctfeds/), or sitting in the audience at something vaguely techy. If he’s not there, he’s probably crouched in an awkward position in front of something funny-looking, taking pictures of it (https://www.flickr.com/photos/maximilianbarners/).
You can find him on Twitter as @maxbarners (https://twitter.com/maxbarners), on GitHub as SteveBarnett (https://github.com/SteveBarnett/), and on his own site Naga (http://naga.co.za/) (which really, really, needs a redesign) as, erm, himself.