A modern workflow for the multi-device web
Analysis of the process that led UI Farm to their workflow for delivering modern web solutions, using a sustainable and performant Responsive Web Design.
Technical review by Kara McCain
By applying a sustainable and future-proof use of Responsive Web Design, UI Farm achieved performant, multi-device websites within an agile environment.
An always increasing percentage of global internet traffic is coming from mobile devices.
A Traditional Workflow
Before the Multi-Device Web
What Could Be Improved
Web agencies used to keep the roles of the designer and the developer strictly separate. Sometimes, none or little knowledge was shared among these roles. This dynamic produced static design files from the designers, with developers fighting over the feasibility of every detail.
Static image files generates negative loops:
- The client must review every design change.
- The designer must apply the change, and re-submit the files for approval.
If the project is a responsive website, the process is going to be repeated for each content view, whether it’s small screens, tablets, desktop o large TVs. The whole process of handling this negative loop is:
- time consuming
- producing assets that are not ideal in a multi-device web
- forcing the developers to adapt a static design to a different media (the browser)
Not the real media
The developers’ implementation of static image files creates web pages that have a different look & feel from the static designs. This is a fatal flaw, due to the different nature of the media.
In fact, the natural media for a web page is the browser.
Welcome to a world where you have neither “standard” devices nor resolutions. Read more about the multi-device web.
Responsive Web Design
In a multi-device web, Responsive design focuses on running a website on every device.
The designer now needs to think about:
- Device specific behaviour
- Look & feel on different devices
- User interaction
UI Farm think it is too hard to achieve this within an old-fashioned workflow, where:
- Roles are separate
- Designers produce static image files
- Efficient Agile methodologies are hard to implement
An Agile New Workflow
UI Farm uses Atlassian’s JIRA for project management. Throughout the duration of the project, we will divide the design and development tasks into 2-week segments.
The client gets access to view the progress of a task’s timeline and interact with UI Farm, for an open and quicker collaboration on the designs and website development. This is achieved through Atlassian’s Confluence, which can be used to collaborate on documents such as specifications and requirements within projects and tasks.
Git is used for the code repository and version control. Every commit includes a detailed comment, and it’s linked to a specific project task on JIRA: this ensures full traceability and easy rollback in case something needs to be changed. This also allows the developers to review each others’ code, and suggest improvements.
At UI Farm the role of UX designer and UI developer are:
- with less separation between roles
The designer and developer work together to create a fully responsive HTML/CSS prototype that provides multiple benefits.
Design Sustainably With Agile iterations
Evolve and remove time-consuming bottlenecks, by turning indefinite loops into time-defined agile iterations, avoiding expensive, non-interactive mockups by designing sustainable reusable prototypes.
The New Sprint-Based Workflow
Sprint 1: UX Analysis
After agreeing the functional requirements and specifications for the site, the UX designers will undertake sketching of the page templates.
Sprint 2 & 3: Wireframe
Based on the UX analysis and sketches, designers and developers start creating the wireframes, directly in the browser.
- The client can see the wireframes via a live URL
- The wireframe is a real HTML/CSS responsive prototype
- The prototype runs on any device, on any browser
- By keeping a separate URL for each version, the client can see the progress
Even at this early stage, the client can see how the site will interact with the user and how the flow of the product works.
Sprint 4 & 5: Skin
Traditionally, the next step would be for the visual designer to create static designs for each page, in applications like Adobe Photoshop.
At UI Farm we don’t use such tools to design responsive websites as they can’t reflect the fluid, non-static nature of the multi-device web.
We then engage the visual designers when we need graphical elements for a design pattern, using tools like Sketch.
One huge advantage with UI Farm’s agile new workflow is the possibility to add user testing sessions into each Agile sprint.
Clients can do usability tests starting from the wireframe version, as it is a real web product already, responsive and running on all devices. It doesn’t take a long time to reach this phase, and this is why UI Farm’s new workflow is making the usability tests doable even for low budgeted projects.
It is also very easy to apply changes for subsequent rounds of tests, and even possible to apply changes between a usability test and the next one. Finally, A/B tests can be easily arranged, before or after the project is live. Clients can test the usability of the very same HTML product, and watch it evolve through subsequent tests and improvements from the feedback. The tested product throughout all of the different phases, is the one that eventually makes it to production.
Even More Advantages
- Client changes are a lot quicker than changing static image files
- Having the designers and developers working closely, it’s easy for them to identify potential design pitfalls up-front
This stage is a true collaborative effort until the client is happy with the end result.
Sprint 6: Quality Assurance
UI Farm adheres strictly to industry web coding standards.
- Valid HTML and CSS, verified by W3C
- Conform to ARIA Accessibility rules
- Complying with all priority 1, 2, and 3 guidelines of the W3C Web Content Accessibility Guidelines (WCAG)
- Ensuring that a contrast ratio of 4.5:1 and higher (ideally 7:1) exists between background and foreground items
As stated by Brad Frost in his post Prioritizing Performance In Responsive Design, citing a research by Guy Podjarny:
86% of responsive sites send about the same hefty payload to small screens as they do to large screens.
In other words, mobile users are downloading desktop-sized sites.
UI Farm look at performance as a major feature implemented by default, and not treated as an afterthought. During the Quality Assurance Agile sprint, UI Farm run several benchmarks, implementing all of the performance improvements, to serve the best experience to all the different devices.
Starting from the first design phase, UI Farm run a series of tools, like sitespeed.io, to make sure the pages are working at their best on all the devices.
All the results are documented on Confluence.
DRY, or Don’t Repeat Yourself
We perform functional, interface, usability, compatibility, accessibility and performance testing on all pages against our defined browser list.
- All functional tests will be tested against the requirements agreed by both parties at the start of the project
- All testing documentation will be made available on Confluence
As we are now designing directly into the browser, the final HTML/CSS/JS responsive site is already available. No further front-end development is needed.
Using the ultra-efficient Ruby’s Capistrano, we quickly deploy websites through SSH and Git, keeping any staging and production releases properly separate. In case something needs to be reverted, Capistrano’s multi-releases feature makes a roll-back to a previous version as easy as possible.
A Case Study: UniCredit Responsive Landing Pages
UniCredit, a leading European bank, hired UI Farm to re-design and develop their Online Acquisition landing pages, currently desktop-only. UniCredit required a strong eye on accessibility, usability, and a clean and modern design, optimised for great performance on all modern devices.
After the UX analysis, the client agreed with UI Farm to perform an optimisation of the content, prioritising it for a responsive re-design and the best performance.
First Iteration: Responsive Wireframe In The Browser
The wireframe kept its own staging URL throughout the development of the successive iterations, so the client could go back to check the progress of each phase.
Second Iteration: Skin
Once the client was happy with the content-structured wireframe, UI Farm applied the first skin. Since the codebase is the same as the wireframe’s, the designers and the developers just continued to work, improving and adding depth, colours and images and always following the company’s brand guidelines. At this stage, the larger screens viewports gained some more specific details, while during the first iteration it was still showing the “mobile-first” approach.
During this iteration, discussions with the client ensured that all of the potential design and performance improvements were applied to the pages. The discussion kept going in parallel with the active development, so that it was possible to experiment with some of the ideas directly on the site, test the results, discard what wasn’t working, or keep the rest for the next iteration.
Third Iteration: Improvements From The Feedback
The third iteration included:
- modern full-screen imagery
- custom typography
- functionality for touch enabled devices
- a sticky header that changes whether the main call to actions are visible or not
- social networks integration
- many more performance improvements, such as conditional loading.
This is the final codebase iteration, meaning the same pages had undertaken several phases, going from a greyscale wireframe to a full-fledged web product while maintaining the same repository and a consistent look & feel. The client was free to perform full-scaled usability tests over different stages of the same website, without worrying about the non-real feel of static mockups and prototypes.
A final word for the great efficiency and sustainability of having a product that’s evolving without changing its nature: there are no static JPEGs to be churned into HTML/CSS pages by two different teams. Everyone can relate to the money-saving argument.
UniCredit performed A/B tests on the new landing pages, which proved successful for all mobile devices against the former desktop-only version.
UI Farm’s innovative workflow and unique skills has given us a very clear insight into our customers’ behaviour and preferences, which has considerably boosted our account application conversions.
Thanks to UI Farm’s approach, we have been able to significantly improve the experience delivered to our customers and prospects, and make changes that may have seemed minor to us but have resulted in significant conversion lifts. UI Farm has truly changed our approach to Interaction Design. Gabriele Rosati, Head of Interaction Design at UniCredit
UI Farm strongly believes that the new era of multi-device web should massively gain from technologies like responsive web design, and a more sustainable workflow as outlined. To achieve this, new methods and a more focussed effort on features previously considered minor, need to be used. Or invented. Or both.
This post was originally published on Medium.