Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trialEdmund Punongbayan
12,117 PointsWireframe VS actual mockup
Is it really important to have a wireframe? I mean you can just work directly on the mockup ( with text, colors, images) and that saves time right? and clients are expecting a "design" already. I need your thoughts on these.
4 Answers
Bryce Santos
11,157 PointsDoing a wireframe first is good because it's done a lot faster than spending a lot of time on a high fidelity mock up. Imagine if you spent all this time on a mockup with a layout, colors picked out, and images, and the client ends up not liking it because of the layout.
Here's a good informational link: https://www.justinmind.com/blog/wireframes-and-mockups-whats-the-best-option/
Jonatas Maia
4,386 PointsI use to do sketches, for wireframming. Then I start to buil a more hi-fi mockup. It is faster and the client and teammates can see what you're thinking quickly.
rachelweaver
15,876 PointsGoing by my own experience I like to start with a wireframe it's faster and you can make several in a short period of time. Wireframes are a blueprint and can give you an idea of where to start when you build your mockup. Wireframes can even be drawn out pretty quickly during the initial consultation with a client. A wireframe is more or less the "skeleton" of a website or product, it shows the basic structure. A mockup is the "muscle" and a more accurate representation of what you will be building. It will provide a color palette, text, visual elements like images, and just overall a more clear picture.
Going further a prototype will demonstrate interactivity, and functionality.
Here is a good resource: https://designmodo.com/wireframing-prototyping-mockuping/
Edmund Punongbayan
12,117 PointsI guess it really depends on your process with the client. I've always been on the process of meeting the client just to discuss proposal and signing of contract. For mockups, theyre just waiting for a final design. Thanks guys for your inputs.
rachelweaver
15,876 PointsYeah it really depends. I get an initial idea during the first meeting because I work in a very small town with mostly small businesses. The contract and wireframes are discussed after I send over a client questionair, just to see if we are a good "fit" or to get a general idea of what I will be working for. Again it depends on your client workflow, process, and overall needs.
Edmund Punongbayan
12,117 PointsEdmund Punongbayan
12,117 PointsI got that point. just that clients expect a high fidelity mockup from the start. thanks bro.