Developer/Designer Collaboration Tim Fisher Kate Pricer Technical Consultant Visual Designer CPoWeR Lead Architect CPoWeR Lead Designer November 5, 2011 1DevDay Detroit
Fisher-Price® Tim Fisher Kate Pricer@tfisher @pricer_designs
Traditional Methods • Direct Developer/Designer collabora@on does not have a signiﬁcant role in the development process. • Designers/Developers oCen in diﬀerent departments. • Designers rarely have the same aFachment to full product lifecycle.
Designer Takes the Lead • UI for a site/app developed by a designer in isola@on. • The result is passed to developers to implement. • Rarely looks/func@ons as intended • Misses out on technology opportuni@es
Developer Takes the Lead• Developer creates ini@al UI. • Asks the designer to make it look preFy, create fancy buFons, etc. • Designers not being used to full poten@al • Designer does not have equal aFachment to end product
How We Collaborate • Side-‐by-‐side collabora@on • Instant feedback/ﬁx cycles • Technology incorporated into design • Design incorporated into implementa@on • Individual work on coding/graphic with instant feedback • Achieves the best outcome for end product
Our Process Graphic DesignApp/Site Conception- features Really Cool Product- layout- flow Code Implementation
Challenging Tradition• Don’t be restricted • Produc@ve environment • Going against the grain