This is a post about my first year at Humaan, the up and downs, some of the challenges and the things I’ve learnt along the way. It’s a personal post of sorts, I wanted to share a different perspective of working in this great industry and perhaps touch on subjects I believe we don’t talk about enough.
Throughout the lifespan of a project we believe there are two fundamental goals needed to be successful:
A quality outcome that achieves the objectives set out and a happy client. One does not necessarily guarantee the other.
There are a handful of things you can do to keep your client happy throughout the process and these are not just designing a mind blowing website.
Who reads them anyway, right?
Visit http://getterms.io to generate your own policy which you can customise and use on any website where appropriate.
We’re working on a little side project here at Humaan, and I thought it would be the perfect opportunity to try out some new-ish frameworks and build tools. For a while now, React and webpack have been all the rage, and I wanted to learn more about them. In this article we’re going to look at setting up webpack with React, along with getting it working with Sass and hot module loaders.
I see an abundance of articles about how designers can make developers lives easier but never the reverse. Why?— Yesenia Perez-Cruz (@yeseniaa) July 18, 2015
Usually, when these sorts of questions are posed on Twitter, there is an overwhelming variety of answers. While the answers varied, the majority who tackled the question proposed that the reason behind the lack of articles was due to the nature of the design/development process being sequential — work moves forwards not backwards. Pointing out that the process from a designer to developer is a linear process does a great job of answering Yesenia’s question… if the question was asked 10 years ago.
Today, I believe the answer is a little more complicated than this. According to the replies, some people, albeit the minority, also agree. These days, the web design process isn’t as linear as it used to be. Roles overlap and an openness to iterate frequently means that deliverables move forwards, backwards, diagonally and sideways during the life cycle of a project. In order to keep up with this, a team must communicate early and continue to communicate often. Essentially, the people in a team team need to work cohesively throughout the duration of the project instead of siloing themselves in their assigned roles.
Here at Humaan we find prototyping to be a valuable asset to our everyday skillset, particularly in larger or more unique projects where concepts or ideas need validating, or when certain design elements can be better explained to our clients during a design presentation. It can provide something tangible for the client to play with and get a feel for while they mull over the design mockups being presented. It’s also useful for immediate user testing and gathering feedback before committing to a large development project.
This article gets pretty techy! If that doesn’t sound like your bag, here’s a quick summary: the HTTP network protocol has existed since the early days of the web, and it’s about to be succeeded by HTTP/2 which will make communications between servers and browsers more efficient. It also means we need to change the way we optimise our websites to take advantage of the technology, so we don’t work against it.
The dawn of HTTP/2 is upon us. Since 1999, we’ve been using the Hypertext Transfer Protocol version 1.1 which isn’t particularly efficient. After many years of debating, HTTP/2 (aka HTTP version 2) has been standardised, approved, and is now on its way to a browser near you. Before we see what HTTP/2 brings to the table, we should have a look at how it came to be.
This is the first post in a series we’re calling ‘client side’, a run of posts dealing with the client agency relationship and how to get the most out of a digital project
First up we’re looking at one of the most fundamental but often overlooked aspects of a successful project: the project brief.