From my very own experience, I reckon that you can categorise the site design process into two sections: the look method that doesn't utilize a wireframe software
, as well as the one that does. Being previously for sides of this fence, I've a knowledge of how those two processes work and although designing with no wireframe works, I'd personally ought to vote in preference of them.
Wireframing, the growth of a "visual blueprint", doesn't have to be overly complicated. At the most basic level, I've come across wireframes which might be are simply compilation of post-it notes together with the interface (UI) elements utilized them. They're then placed onto a sheet of paper to exhibit the structural layout. Match it up to wireframes produced through design software and you might go to a more refined wireframe from the latter, but no matter how you intend to make your structural model, the result is always the identical. In other words, it shows yourself, your client or some other party where things will likely be located on the page.
This is sometimes a live saver if you're creating a website for the client. Going back to my times of due to being on "side A" of the fence, when to become a website for any client Irrrve never used to perform any wireframing process previously. The complete process consisted of: gathering requirements, spec'ing your website, creating the graphical UI and after that building the website when the design had been agreed. The main flaw I came across with this process would be the potential for the customer looking to affect the main layout quite considerably. I'd have no problem when they simply want to tweak things here and there e.g. colours, make text larger, then add more images every now and then, result in the video a lttle bit bigger (the most common stuff); nonetheless it would have been a ton more painful should they then need to move to produce about on the page that directly affected the "page template". Jumping onto "side B" with the fence and producing the wired layout for the site ensures that layout might be agreed beforehand knowing that when the UI design is presented, you could possibly then only have to update the typical stuff.
The need to Spell against each other for Clients
Even when presenting a wireframe into a client though, I've had occasions where they would be reluctant to sign this part off on the grounds who's looks very "blocky" and "plain". "Yes it does" will be my immediate reply to this as these blocks determines where we are going to put things on your lovely page in order that when you get back to me at a later date once you've reviewed the graphical design, you simply can't then notify me why's the navigation up here and not over there? Keep in mind that, I have had clients such as this before so even if making a wireframe, there can be times when you'll still have to spell out that this is only to obtain the layout correct to start with, then we'll apply the pretty tiny bit with it afterwards.
A collection of Design Software
There's no need to necessarily know the right path around Adobe software in order to produce some decent wireframes. I use an online tool, Cacoo, to produce mine. This online software permits you to drag and drop pre-created elements to your page. This will save lots of time during the process.?
Like with everything web related, everyone will have their own opinion on this topic, but my own preference is to apply a wireframe each time I'm designing a web site. Be it for any client or for my very own site, it does not matter as it implies that the UI design is increased because you're effectively working from the template.
If you find yourself working on a job for any client, then looking to have Joe Bloggs sign over wires before you start for the UI is a part of this design method that I'd personally call fundamental to making certain you maintain good budget and time management on a project.