Home / Blog App Development

Reviewing a Prototype or Screen Designs Before the Build Starts: What to Check

By Gotka Technologies ·

A person using a phone and laptop together at a cafe
What is the difference between a wireframe, a mock-up and a clickable prototype?

A wireframe is a plain, mostly black-and-white layout showing where things sit on a screen, with no real colour or imagery. A mock-up adds visual design, such as colours, fonts and real or placeholder images, but is usually still a static picture. A clickable prototype links several screens together so you can tap or click through a chosen path, such as placing an order, without any of it being working software yet.

How should I review a prototype or screen designs before a build starts?

Walk your own real daily work through the screens rather than just looking at them. Pick two or three actual tasks you do today, with real examples, and follow each one screen by screen, asking whether the information you need is there, in the order you need it, and whether every button does what you expect, before you approve anything.

What is easy to miss when reviewing a prototype?

Reviewers usually check the main, happy-path screen and skip the rest. Commonly missed screens are error messages, empty states before any data exists, who is allowed to see or do what, the unusual case that happens only once or twice a month, how reports and exports look with a realistic amount of data, and how every screen behaves at phone width, not just on a wide monitor.

What should ‘approved’ mean when I sign off on a prototype?

Agree in writing, before you approve anything, that the approved screens become the project’s scope: what the system will do and roughly how it will look, not a final guarantee of every pixel. Keep a separate running list for anything you want added or changed after approval, so new requests are priced and scheduled deliberately instead of quietly expanding the original build.

Can a prototype tell me whether the finished system will actually work?

No. A clickable prototype only shows the screens and the paths you click through; it does not use real data, is not connected to any other system, and says nothing about how fast the finished build will run under real use. Those need separate checks, usually covered by acceptance testing once real software exists, not by reviewing screens.

How many rounds of prototype review should I agree to before the build starts?

There is no fixed rule, so agree a number with your developer before reviewing begins, commonly two or three rounds, each tied to a clear must-fix versus later list. Open-ended revisiting of the same screens is what usually causes delay, so settle how many rounds are included and what happens if you genuinely need one more.

What happens if I spot a problem after the build has already started?

Tell your developer straightaway rather than waiting for the next scheduled check-in, because a structural change found early in the build is far cheaper to fix than one found near the end. Expect it to be logged as a change rather than assumed to be free, and ask how it affects the agreed price and date before work on it continues.

WhatsApp
Get in touch

Send us a message

A real person from our team will get back to you.