Content

How does creating an app with us work in practice?

Our Process

Process is not just a fancy word

The very finest digital services are built with agile attitude, one version at a time and with systematic testing.

This is why a well-functioning process can make all the difference in the world. It separates excellent apps from failed ones and successful budget estimates from disasters.

There are many ever-changing factors that define how software projects progress. For this reason it is smart to divide it into more manageable parts – this increases flexibility, leaves room for changes after testing and makes it far more easy to estimate how much work is required.

Our process is built around the idea that a mobile project can typically be divided into six sections: vision and goals, specifying the features, the design, implementation, testing and release & development.

Throughout the project, you can take part in this process depending on your own wishes and possibilities. We have enough experience to work independently, but we are also really good at listening and co-operating. In some cases, we’ve also done work at the customer’s own premises.

Vision and goals

What is it?

The first phase is the most important one, because it sets the stage for the whole project. The vision and goals phase seeks to answer the most basic questions, on basis of which the goals and value proposition are defined.

Features

What does it do?

The next step is to decide the operational structure of the application. This definition can be done on several different levels and its aim is to make sure that everyone knows exactly what it is that we’re building.

Design

How does it look and feel like?

In this phase, the functionalities are drawn into a wireframe model and later on into an interactive prototype. The idea at this stage is to better understand the service as a whole.

Implementation

How does it work?

Even though there are often many choices that have to be made during the implementation phase, the basic structure of the service should be at this point ready. In this phase we also make decisions related to the maintenance, extensibility and reliability.

Testing and polishing

Why is it good?

The app will be tested and polished throughout the implementation process—but this final testing phase often makes or breaks the service. This is why at this stage the product needs to be reviewed as many times as it takes to match our quality standards, both technically speaking and experience-wise.

Release and Development

What next?

After a successful release it is time for the application to begin its own life. It is highly important to follow the user response closely — it is only in this phase that we truly get an idea how the service works in its natural habitat. Using this information it is also easier to make decisions about the further development of the application.