Researching the industry comes first, ensuring that I know how your competitors are operating, and then trying to identify how you can do it better. It'll then be important to identify your potential market. If you're aiming for an older market, then a fun, playful site may not be appropriate. Eqully, if you're a quirky brand, you probably don't want something that resembles a corporate layout.
From there, it's then important to plan how your site will function, considering the user journey and how they'll most likely interact with your site. This will tend to change between devices as well, for example, a desktop site will rely on mouse clicks to get to links, however, a mobile site will rely on finger touches or swipes.
I keep up to date with UX design and what does and doesn't work, so any decisions made are backed up with evidence.
Once the research and planning is complete, the website design can be begin.
Development starts as soon as the design stage has been signed off. Every site is built from the ground up. I don't believe in refactoring a pre-bought theme for your website, when they offer generic templates and severely lack optimisation, due to containing an abundance of features, most of which go unused.
Each site is integrated with Wordpress, which in this instance is used as a content management system, to allow you to update almost every aspect of your site.
Lastly, the responsive element of the site is developed, optimising how your site works on mobile and tablet. Google now treat this as a ranking requirement, not option.
Throughout development a degree of testing occurs across browsers and devices to ensure that any bugs are caught at an early stage. By doing this, very rarely do you get to the end of development and find something is fundamentally broken. However, a degree of end-user testing is always recommended, with real data and real people to try and emulate what your customer base will see. Feedback from this allows for ironing out any issues that were unforeseen during early development stages.
A very good testing tool once live is called A/B testing. This is essentially the deployment of two almost identical websites, that contain the most subtle of changes. This could be a smaller/larger font, different coloured calls to action or different text for the content. A/B testing allows you to compared the analytics and see which version of your site works better.
Deployment can be looked upon in two parts. The first is getting the site onto the most suitable hosting platform. Every site has different requirements and as such, will require different levels of resources to function properly. A site that displays some text and images with a few thousand views a month will most likely work under a regular hosting environment. On the other hand, an eCommerce site that has thousands of visitors a day may require a more robust, dedicate platform to deal with the traffic and bandwidth requirements of a bigger, more active site.
Once hosting has been decided upon, a test domain will be created for your site that will be representative of where the site will be once it's live. This allows any clients to properly test their website, and gives full access to the cms to add any extra content in preparation for launch.
It's also an opportunity for me to optimise the site fully for the hosting environment, keeping file sizes low and visit times quick.
Once everything is looking good, the second part of deployment kicks in and the site will seamlessly go live, and the real job of getting people to your site begins!
There's a very simple difference between good web design and bad web design, and it's usually very easy to differentiate. A good design works, a bad design doesn't.
Before a pen goes to stylus, setting out how a blueprint of how your site will work is important. This could be as simple as providing all the content for specific pages, knowing the site map structure and deciding what links will be in your navigation.
Equally, it could be more detailed by looking at how your site may function differently between a touch screen and mouse and ensuring that your users are catered for differently on each platform. However in-depth your planning may be, any time spent at this stage undoubtedly saves time later on in the project
Well planned web design, more often than not, tends to be a design that also works.
As mentioned, part of the planning stage is providing content. The importance of providing content before any physical design takes place cannot be stressed enough.
Without the content, it's impossible to tell whether a design would be appropriate for your needs and from experience, content always ends up getting pigeon-holed in to the site, and you end up fitting the content around the design. If the content for one page is 300 words, that's going to look radically different to a page that has 3000 words.
Being prepared with the right content ultimately saves you time, and more importantly, money, as there's no dragged out costs to refactor a design that hasn't been suitable for the Lorem Ipsum text in a design.
Always design around the content, not the other way around.
By using your content as the basis for the design, you can guarantee you'll create a unique identity on the web, as no one else will have the same content and as such, no two designs should look alike. Follow this simple practice, and you're sure to stand out in a crowd.
Fifteen years ago, design considerations were considerably simpler than they are now. Most people worked on a PC, running Internet Explorer (or at a stretch, Firefox) and most desktops or laptops worked off roughly the same resolution. The parameters in which a website needed to be adjusted for were relatively slim.
Fast-forward to present day and it couldn't be any more different.
You have multiple operating system platforms. There's a plethora of browsers, each of which have different versions that do/don't support modern web technologies. There's now a huge array of mobile devices that are all touch based.
All these things have to be catered for when designing and building a site, and a lot of the time supporting one, breaks another. This is all just part of the challenge!
Developing websites can be incredibly fulfilling. Taking a flat, motionless design and making it dynamic, interactive and most importantly work, is a great feeling. On the other side of this though, is the hours and hours of unnoticed work that go into making the front end experience for the user as seamless as possible.
Whether it's optimising images, reducing load times, speeding up a process or augmenting for high-resolution screens, these are all details that don't tend to be noticed when they're good, but stand out like a sore thumb when they're poor. That's why I spend a lot of time making every site as close to perfect as possible across desktop, tablet and mobile.
A common requirement with modern business requires the ability to allow multiple systems to communicate with one another. This could be something simple such as pulling a feed from another site and displaying it on your page, or it could be the use of an API (Application Program Interface) to extend functionality of your website by combining features of another application. An example of this being the use of the Right Move API to integrate with Wordpress, so that properties are synchronised between the two portals. APIs are commonly used in eCommerce systems as well.
In the second quarter of 2015 alone, ecommerce was estimated to be worth $84 billion. It's an industry that's growing at an amazing rate, and if you have a business that sells products, but not online, then it's not difficult to argue that you're missing out on a huge chunk of the market.
Having said that, simply having an online store means very little without sales. That's where I hope to come in and help you develop the perfect online store for your customers. A lot of people get into the trap of developing for what they like, but I like to make it more scientific than that, by looking at purely in terms of facts and figures. What do consumers like? How do they interact with elements of a store? How is the experience different from mobile to tablet to desktop? Everything I do, I do for a reason and it's backed up by results.
As part of website optimisation, support for all the major browsers (and versions) is incredibly important. For example, Internet Explorer prior to version 10 is lacking in support for some major features, such as animations (which you'll see if you compare this site between IE9 and say, Google Chrome).
Where the issue arises, is supporting a feature for modern browsers, can actually break a site altogether on an older browser. It's therefore necessary to create fallbacks for these browsers by specifically targeting them. When you have multiple browsers and versions, this is no small task, but none the less it's something that I undertake with every project I take on.
Legacy browsers are also supported with some features to ensure that the still functions on a basic level to get your message across, although with a browser such as Internet Explorer 8 (which has been abandoned by Microsoft) there will be integrated messages to inform a user to upgrade their browser, with a link as to how they should do it. A user won't be left in the dark as to why their site isn't working, and they'll be educated on the reasons for moving over to a browser that supports modern styles and functionality.
Of course, the browser checklist wouldn't be complete without considering mobile browsers for the likes of iOS and Android. These are designed around the fact they'll work on touch screen devices, so functionality changes again from the desktop versions. Using media queries and javascript, any compatibility issues are dealt with.
Performance and usability also goes beyond providing a better user experience. As of April 2015, Google are now ranking website performance and having a responsive website as key parameters as to where your site is ranked on their search engine.
These could literally be the difference between being on the first page or the second. Being the 10th result (i.e. still on page one) compared to the 11th (top of page two) equates to double the amount of click through traffic.
The first page of Google equates to 94% of clicks, the second page equates to 6%.Keywords are still important, but they're no longer the only parameter that matters.
It's surprising how many sites I come across that have no optimisation setup at all. Investing a bit of time to reduce image sizes, condense and compress files and organise the site structure to load faster, can go a really long way, and not just on the SEO front.
Typically, when a user lands on a website, you have between 10 and 20 seconds to engage them before they leave. When you consider this time also includes loading times, it becomes even more crucial to have your site served as quickly as possible. If your site takes 10 seconds to load, you could be losing customers straight off the bat! Through various different techniques and custom scripts, i've developed a way to ensure that your site will load quickly and efficiently, giving you as large a window of opportunity as possible.
The last part of the puzzle is to use analytics to measure everything that your site is doing, from number of visitors, to what pages they're viewing, where they've visiting from and what devices they're using to view the site. Using these analytics, you can then figure out what you're doing well and where you're not quite as successful, you can improve upon those areas. It's undoubtedly the best way to measure success.