GenericFrame is the best tool when you need to demonstrate your ideas in the early stages
of a project. Use it to create high-level visual prototypes
quickly and without writing a single line of code. Building a prototype is easy and simple
- add components (Text, Input, DataGrid...)
- organize the layout in containers for horizontal and vertical layouts, tile layout
- nesting containers
- style components (edit properties of the components like font, color, size, data)
- create multiple-view prototypes
- add links between views for navigation
- import / export projects & templates
A visual prototype coming along with your sales proposal will increase the understanding of the customer about the offering, thus increasing the chance to promote your idea
or even close the deal.
You can test your ideas
with users and find significant issues
, saving you time and money by verifying the value creation in the very beginning.
Once your idea has proven it is worth the effort, you may want to create a detailed prototype
(for example including all screens, all buttons and components, and navigation).
This way you will be able to:
- verify the requirements
- demonstrate proof-of-concept
- test and train the users
- test different scenarios and workflow
- extend the technical specification with a clickable prototype
- create more precise estimations
- communicate features, requirements and workflows much easier
Even the best idea may fail because of poor execution (lack of analysis of the details and communication problems). Communication of even a simple software system may result in a multiple and larger technical documents which are not easily understandable for non-developers. By using GenericFrame prototypes you are able to:
- Demonstrate (not explain) how detailed processes will be transformed into screens and whether all details are defined correctly. Often even the most professional and detailed specification is not enough for non-technical users to get the "big picture". The user level of understanding about the details remains low and incomplete. Users see a very detailed and well structured document and think: "It looks so professional, , it must be right". Thus, the best way to communicate the idea is by presenting a prototype. Even better let the users try for themselves - from the first step to the last one.
- Test and optimize the effect of UI design on customer satisfaction - sometimes new systems promise to solve problems, but bring a new type of complexity in users lives. It is best to make sure up front that the future system will not be too complex for the users. Encouraging involvement of users in early stage makes them co-creators and minimizes the risk of a negative attitude or refusal to adopt changes.
allows you to start the design process with the client right off, based on the high-level prototypes created during the initial (sales) phase and grab their attention from the start. It helps establish clear communication and sets the right expectations
Everyone who is involved in the project will actually be able to experience and see in action what the new system is and how it will perform.
Sometimes a static prototype is just not enough. Users need to see real data and working functions to be able to fully verify what they really want.
The challenge is that different users can handle different level of abstraction. A very experienced user would understand a high-level prototype showing just the concept and leaving a big room for interpretation.
Most users will need to see the buttons labels and screen flow. They will ask what exactly would happen if they click "Preview Offers". Some users (with basic computer skills) will need to see their real data on the screen, so they can associate the prototype with a real situation. They may complain that last weeks orders are not displayed and that it is "not working".
In such cases it is best to make a real working prototype, showing real data and simulating the real system.
The question is "won't it take the same time and investment to build a working prototype as building the whole system". The answer is NO - with GenericFrame you can build a working prototype faster with a very tiny budget
Creating a simulation (a dynamic prototype)
is much easier and less complex than with any other web-technology.
GenericFrame lets you complete an idea's full life cycle - from the first scratch to a dynamic prototype where needed.
Developers can use the prototypes from the previous two stages (or create new ones from scratch) to build a dynamic prototype or a web-based app within days using GenericFrame only.
Our system will integrate seamlessly at any stage of your project. You can easily connect GenericFrame to any popular backend - PHP, Java, Ajax, RonR, .Net. Add new functionality to build high fidelity prototypes and applications so you can start marketing your product even if you haven't built it yet.