designer and developer atlanta ga

It’s not common for someone to be a designer and a developer.Typically there is a designer and developer for each project. Two separate people with two separate roles.

A designer is someone who decides what a website will look like — color, fonts, layout—while a developer is someone who builds the website & makes it actually function. A designer creates mockups for a website and then the developer builds the interactive website based on those mockups.

I’ve always been a designer and developer, even before I knew what the distinction meant. When I graduated college, I thought people who “made websites” designed them and then built them. And at my first agency job that’s exactly what I did. I made the mockups for the website and then I built that website. It wasn’t until I went full-time freelancing that people started asking me if I was a designer or a developer. I felt like I had to choose between the two because almost everyone in the industry does.

I asked myself, would I rather design websites or build them? I slept on it and still couldn’t come up with a decision. I loved design and I loved to code, and I didn’t want that to change. Deciding to be a designer and developer made sense to me, and I think it also makes sense for many businesses that need help with a website.

Businesses typically either hire an agency that has in-house designers and developers or a business hires a freelance designer and a freelance developer to work together and create a website. However, hiring someone who’s a designer and developer provides benefits beyond only having to hire one person for the job.

1. Designing with Code in Mind

When I design mockups for a website, I know exactly how I will build it. Sometimes developers are handed the mockups to websites that were designed to look good but won’t, in reality, function well.

Factors such as page load times, flexibility of device-widths and cross-browser support are sometimes overlooked in design but need to be considered during development.

Then the developer has a challenging tightrope to walk. The developer wants to honor the mockups provided by the designer, but also knows some of the design decisions will affect the website’s performance.

The time it takes for a developer and designer to work through these issues of design vs. performance can eat up a lot of time.

When I design websites I’m thinking 10 steps ahead. I’m thinking about the unique challenges my design will create when I’m building the website.

Will a client be able to easily update this?
How will this feature look on Internet Explorer?
Will this page load quickly?
How will this absolute positioned SVG shape look when the device-width changes?

Many skilled designers these days learn enough about code and CMS frameworks to be able to make design decisions that look and function well. On some projects, I’m solely the developer and a project is always more enjoyable when I work with a designer that at least understands how a website comes together — from the website’s framework to it’s performance.