The Workflow

The 4P flow

When you buy a product with modifications or want to collaborate with us to develop a new idea, we set up a workflow that guides you and us step by step through the development process, ensuring we continuously match your needs as we progress.

Proof-of-principle
After we have a general idea of your vision, requirements and the environment, we will develop a proof-of-principle (pop). The pop gives everyone a good sense of how the app should function and how the layout should be arranged. And most of all, the idea starts to become reality! Most of the app is still non-functional. This stage roughly takes 20 to 40 hours.

Proof-of-concept
The proof-of-concept (poc) stage results in an app that has the core functionality mostly worked out. Using feedback from the pop we can flexibly steer the project in any new direction. The finished poc can already be used for limited testing. The app will still lack in graphics and secondary functionality. This stage roughly takes 20-40 hours.

Prototype
The prototype is a fully functional stand-alone application, with graphics implemented as well. The prototype can be used for full user testing, and should give the idea that it is ready to be used. Bugs may still be apparent and functionality may be not exactly as desired. This stage roughly takes 40-60 hours.

Product
The finished product is a 100% functional, well-tested application that functions stand-alone, and additionally may communicate with a server. It is ready to be deployed and implemented on-site.

 


 

Re-usability

Parts of the source code is re-used to build other apps for similar problems in different fields, thus creating a knowledge-base of educational support tools that become cheaper and faster to build, as well as becoming inter-operable: applications can communicate with each other to create new possibilities for more advanced and extended tools.

This means that the client can not become the full owner of the application: part of the app is depending on shared code. However, we believe that is a small sacrifice compared to the benefits shared knowledge gives:

  • Development costs can be lowered
  • Apps are designed more specifically with the educational field
  • An open gate for further innovation