What's included

• Determining the scale of the project

  Before we jump into anything, I recommend that we have a discovery call to meet each other and chat about what you want. Then we can begin to determine the scale of your project and the requirements. Of course, the budget also plays a part in what will be possible for me to deliver, but there are workarounds for both of us to enter a good collaboration after deciding to work together.

• Pages, page templates and flows

  Depending on what your solution requires I will design each page, template or a specific flow based on one device view, but first, this depends on where your primary focus lies, is it on mobile and more like an app or generally for web and browsers? In my experience, the 'mobile-first approach' only makes sense if you are creating an application, anything to do with the web and browsers it would be much better to focus on the viewport of laptop devices as it is easier to scale down than up. I always work based on components. I use these to create your pand when it comes to When I design I focus on your content and creating reusable components. I do so both to save your valuable budget and time, but also to ensure recogni With my approach responsive design isn't forgotten it has just been moved to another stage in the design process – the component stage. I create components to save not valuable time, but also to reuse if necessary, I would suggest If your focus is mobile I c need I will deliver the design of the pages in laptop view. The responsive design will be established on the component level, meaning each component required to create the solution will have five responsive viewpoints – mobile, tablet, laptop, desktop, and large screens. The reason for doing it this way it to assure your developers won't skip important devices.