Delivering the designs the way your developers like it

Our aim is to build a friendship with your developers

The handoff process is the key to your product looking the way we designed it.

01 Understanding development requirements before design

The first step is to ensure that the design and development teams have had an opportunity to communicate the requirements and specifications of the build before we start picking that fancy drop shadow effect. We need to understand what development needs from us and what the parameters are so that we start on the right foot, this could be agreeing on grids, screens sizes and responsive behaviour.

02 Confirm designs fully before handoff

No one likes to re-do their homework, so when we are designing your UI it is the key time to ensure that everything is to your liking, the more detail here the better. We are big advocates for agreeing on completing content like copy during low-fi wireframes before UI starts so we can reduce the number of minor adjustments is made before we ship out your designs, this will help to reduce costs.

03 Design systems for the win

Creating a design system is key for a seamless transition. You can refer to the Design System page via the link below for more detail on how we do this but in summary, it's where we ensure all the individual elements are collated and annotated for ease of reference and future-proofing.

View handover file

04 More than a link

The development process of your designs is something that won't happen over time so it's really important for us that the development team is comfortable with what we have delivered before they get started. More importantly during the build, we ensure that time for us to review and be available for questions. So we facture this into your project from the get go.

Watch a short explanatory video

All of our projects have handoff, but here's a couple to look at

Noa & Parker

Native App, Product Redesign

Pearson Clinical

E-commerce Website, UI Refresh