Sometimes we are questioned about why someone should do a prototype of an app or a website instead of already building it. It sounds like working twice, doing a wireframe and then doing the real project, but in fact it may save you time. When you go directly to your prototype, all the changes will be done by all the team: designer, programmer, copywriter, business analysts, everyone involved. If you prototype before involving everyone deeply in the project, you can save your team a lot of time and energy.
Using Justinmind Prototyper, the information architect can create the website structure and annotate it, the user interface can create the wireframe, the designer can make it have a look and feel and the programmer can make all interactions, movements and data show. All of them could be able to do their part using Prototyper, without much fuss and work. It’s drag and drop, and by learning some basic commands and tricks, even a no-programmer can create some advanced navigation interactions.
Dividing the wireframe work
It’s easier to collaborate when everyone uses the same software and the same interface. By sharing files, no-one will be working on old files, will loose requirements or comments, and everyone may be able to do what they’re best doing.
Using concurrent licensing, a company can have literally several people working on the same project all over the world, sharing, collaborating and creating a great product.
Joining the work together
After everything’s done, the project will be a single file. It may be presented to the client, the boss, or tested with final users, just like it was a real one. The changes, modifications and requirements can be directly added by users, using Justinmind Viewer tool, Automatically Generated HTML orJustinmind OnDemand service, and the team will have all them available with some clicks. So, all modification can be registered.
That’s when you generate your documentation, with instructions to everyone involved about project requirements, steps to follow and everything required to make things really work. It’s much easier to draft and change something on a prototype and only code the final version.
Besides all this process, Justinmind Prototyper’s requirements management also controls versioning, helping business analysts to know which version and which changes correspond to which piece of software.