How often do you prototype?

Question

Layouts and prototypes

Good afternoon!
Imagine that the design of the site of the company "N" is being agreed.
It is assumed that the project will have up to 20 sections (pages) of the site.
It is interesting to get the opinion of web designers with experience - do you always make prototypes (for example, in Axure) in order to coordinate it with the customer in advance?
The question is interesting because:
1. If the project has about 20 pages, then it will probably take a lot of time to create a prototype.
2. The prototype will be conditional. For example, content blocks are gray, Text is default, lorem ipsum, for example. After all, the customer can imagine the end result anyway in his own way and then it will be necessary to redo a lot.
I may not be imagining things right. But can you share your experience - how do you go through such processes?
Thank you.

Answer 1

Because I make websites on Bootstrap, then it makes no sense to make prototypes in
Azure

Answer 2

In my opinion, a prototype is a very important thing in the process of creating a product. Design is the first stage in the work. Often the customer cannot say what will be on the site page, for example, but he knows what task he must perform. Based on this, the first prototypes are created, which are necessarily corrected later. Such preparations will save you a lot of time and nerves in the future. You can quickly sketch in Balsamiq.
Also, it is necessary to distinguish between the concepts of PROTOTYPE, WIREFRAME and MOCAP. Here is a good article https://habrahabr.ru/post/170549/

Answer 3

Out of 20 pages, usually 5 are unique, the rest are copies, we approve unique ones and you're done.
Usually I make prototypes in AI, they are static.

Answer 4

What you described is called a wireframe (a conditional sketch with squares instead of pictures).
A prototype is essentially an interactive mockup. It looks and feels like the final product, but only all the functionality is emulated by a special program (like Axure)
If you are lucky and can find a client who agrees to pay the costs of creating all these things, then why not). In most cases, it's easier to agree on a static layout.

Answer 5

I almost always do it on a CSS framework like TB or Uikit. Something like this .

Answer 6

In such monsters as Axure, I did it only a couple of times, although I am not particularly friendly with UI / UX.
In general, for simple sites, for customers who don’t fumble, it’s very useful to show mockup, wireframe ... I did them in different programs, in the end it’s easiest to do on such a stack: paper + pencil , ruler . In general, the paper helped to explain to a very difficult client - the main blocks on the page.
Now I draw on paper more often!
Then, it’s probably dark to transfer to the CSS framework (someone immediately does it with them)

Answer 7

Differently.
It is better to really think over projects with great functionality in a prototype in order to understand and approve the functionality both for yourself and for the client.
Landing / microsite projects can be done right away - there will still be more talk about fonts / pictures, and not about blocks and functions.
Work by the hour and no one will have questions - whether they need to pay for the prototype or not.
Forget about the fix - this is the dumbest workflow in design and code.