Web designers are seen as the creative spirit of the web team. They are aesthetically-oriented, eccentric dreamers. But most of all, as soon as they start to question every little thing that doesn’t make their site look “perfect”, they can be very annoying for developers and programmers to work with.
Working as a web designer can be damn stressful.
They have to design for a medium that changes every day, which is not as reliable as a printed page, and that doesn’t look the same in all browsers.
With all these important aspects to consider, designers also have to come up with colors and graphics that match a company’s values and communicate them consistently. Once they have made all this effort to put all of these elements together on one webpage, their work, which they care about and love so much, goes to the hands of a web developer with the hope that she/he will care about it in the same way.
Sometimes this magic happens, and everybody is happy: developers and designers shake hands, satisfied with their work together.
Sometimes, however, design and development take two different roads, and this is when the balance gets broken and suddenly designers and developers discover themselves as two enemies.
We can get rid of the line between designers and developers if we just think about the fact that there are no beautiful websites without an enjoyable, engaging design and there are no accessible, user-friendly websites without great development.
In this presentation, starting from the point of view of a web designer (me), you will learn about a few things that cause disagreements between designers and developers and how to overcome them in order to create a peaceful, efficient and professional relationship.
3. The strength of the team is
each individual member.
The strength of each member
is the team.
Phil Jackson, American professional basketball coach and former player
27. This is the most creative part of the
project and everybody is bursting
with ideas for the new website.
The first priority is to determine
project objectives,requirements
and what will make it successful.
28. THE DESIGNER THE DEVELOPER
Understand the criteria for success
Conduct research
Understand brand vision
Be focused on effectiveness
but most of all....
Individuate the best coding solution
Suggest interactive features
Point out execution issues
Be focused on efficiency
but most of all....
30. Based on existing corporate colours
(if any), the designer will create a static
mock-up of the homepage,showing
exactly how the web page will look,
but without any functionality yet.
31. THE DEVELOPER THE DESIGNER
Identify limits of the design
Suggest alternative solutions
Share your expertise
but most of all....
Develop an adequate visual language
Think through the interactivity
Involve developers
but most of all....
33. The static concepts are taken and chopped
up into component parts ready for coding.
Using different languages,like HTML and
CSS,the web developer will render the
design into an interactive web page.
34. THE DESIGNER THE DEVELOPER
Check the design’s implementation
Accept compromises
Be available for changes
but most of all....
Develop the design details
Add interaction and functionality
Consult the designer
but most of all....
36. This stage involves running the template
through many different browsers,devices
and computer platforms and making sure
everything works,no matter from which
part of the website the visitor is coming from.
37. THE DEVELOPER
Solve technical and
functional issues
Report any necessary changes
to the designer
but most of all....
THE DESIGNER
Test design consistency
and general look and feel
Ask developer to refine
any design issues
but most of all....
39. In this final step the web team
must make sure that the site is
running as efficiently as possible
and that no functionality has been
compromised in the migration.
41. It is good to have
an end to journey toward;
but it is the journey
that matters, in the end.
Ernest Hemingway, American author and journalist.