17th November 2009
Here are some questions and answers about creating wireframes with Justinmind Prototyper.
When do we stop building the wireframe and start the real development of the project?
The answer is simple: when you won’t make any more structural changes. ...
11th November 2009
Think of your project as a unity. That is why big projects need to use the same font, sizes, colours, styles, etc. Hi-fi wireframes can use widgets and templates to maintain consistency. There are several advantages for projects:
1. The users will know...
09th November 2009
Some big projects done with Justinmind Prototyper involve more than one person. Sometimes big teams work together to create something, and thus collaboration-management is a very important feature of our wireframe authoring tool.
Keeping the same desig...
30th October 2009
Those that already create a prototype before investing too much time in any problem already know: there are several blind spots and mistakes designers do unwillingly. And those can be avoided by testing and validating the wireframe through several phases,...
30th October 2009
After finishing your project and presenting to the client, sometimes it’s needed to do usability tests with a prototype, to understand real users’ needs. So, you can export your hi-fi wireframe into HTML, or even test it remotely using Justinmind Serv...
23rd October 2009
Have you ever seen a wireframe with simulated data?
Justinmind Prototyper allows the creation of much more than simple, static wireframes. You can have fully functional prototypes, with events and action as astonishing as search, behaviour changes and ...
23rd October 2009
Normally, a project made with Justinmind Prototyper is going to be coded into a piece of software or a website later on. So, it’s important that your wireframe software to be capable of exporting in several formats.
Export your documentation to your ...
19th October 2009
It may sound contradictory, but going straight from wireframe to code is not the best way to finish your project early. Normally, clients make several changes when they see the actual design, with colours and real text. Many of those are structural change...
09th October 2009
After defining which pages are going to be created and what they’ll contain, we start the wireframing process. This means start drawing the objects that will be present on the pages, without much attention to detail.
Lo-fi and hi-fi wireframes
A few...
09th October 2009
Wireframes are good to show how the web will look like. Sitemaps are used to show the navigation structure.
But none of them show how a website works.
The main focus of a prototype is not the appearance of the website, but content, structure and fun...
02nd October 2009
There is a tendency nowadays of doing HTML prototypes for client presentation or to test projects. This is a more realistic approach to paper, but it’s very much more time consuming. Justinmind is a tool made to join together the functionality of a HTML...
28th September 2009
We suggest some basic designing steps to increase speed and facilitate the creation of your wireframe:
1 - Use some sort of grid. For example, 960 framework. This is very commonly used by developers, and give some sense of proportion to your project. I...
28th September 2009
Every project plan has some elements in common. Before starting to create the prototypes, drawing wireframes or hiring coders, it’s important to:
Define what you will do
Divide it in small tasks
Define who’ll do each part
Assign an amount of tim...
23rd September 2009
Have you ever created an early project plan, or a simple wireframe — maybe to get approval for the project — only to find it unworkable when you started tracking progress? With the right start, you can ensure that the plan you create at the beginning ...
23rd September 2009
Symptoms:
Communication problems between team members.
Lack of comprehension of project requirements.
Several changes, discrepancies between versions, modifications throughout the development phases.
Use it when:
Exploration of an end-to-en...
