Web Designer vs. Web Developer

Even though the title may suggest some flair of controversy among the two, in actual reality they are the two creative blood-brothers of a Website that contains a set of related web pages served from a single web domain. However, it might be a better idea to identify their respective roles in creating an effective website.

Who is a Web Designer?

Simply speaking, a Web Designer is one who designs Web pages. However, a Web Designer is more attuned to the look and feel of a website than how it will work, often using WYSIWYG editors, instead of getting into HTML straightaway. Moreover, expert Web Designers know very well how to utilize the principles of design (that include Balance, Contrast, Rhythm, Emphasis, etc) to create a Website that looks magnificent.  However, a Web Designer needs to have the following skills to become successful:

  •  First hand knowledge of Hyper Text Markup language (HTML)
  • Cascading Style Sheets (Simple mechanism for adding style that include use of appropriate font, color, spacing, etc)
  • Project management
  • Ability to apply aesthetic sense

Who is a Web Developer?

A Web Developer is one who programs web pages. A web developer is more focused on the way a website functions instead of how it looks. A Web Developer would routinely use HTML text editors while working with databases and programming languages as well as HTML. Also, an expert Web Developer knows how to program CGI (Common Gateway Interface) and scripts like PHP. The person generally understands how web forms work and so can keep a site running perfectly. A Web Developer needs to have the following skills:

  • HTML
  • CSS
  • JavaScript and Ajax
  • PHP, ASP, Java, PERL, or C++
  • MySQL Database
  • Project management

Conclusion

Technically speaking, Web Designers deal with ‘non-functional requirements’. They usually focus on the look and feel of the interface – the colors selected, where text should appear as also if a menu needs to be displayed fully.  Web Developers on the other hand deal with ‘functional requirements’, writing functional code that includes processing the data provided by the client, getting the menu work as also whether it should appear or disappear, piloting entries in databases, etc.However, the dividing line between the two is rather thin, even though you can judge where the developer lacks his ability when the pages are found static and heavy. Poorly performing designer, to be precise, will be betrayed through poor aesthetic presentation.