What do you find most appealing about robots?

What about us happens.

Apps for storage systems, for sampling logs on construction sites or to support workflows - smartphones and tablets offer many advantages not only in the private sector, but also within companies.

No matter what requirements are placed on the app development, our mobile team rises to the challenge. We are not technically tied to one platform, but rather attach great importance to remaining independent in order to be able to offer our customers the best possible solution.

But how does such an app actually come about and what do you have to watch out for in order for the process to succeed?

A short interview with our Head of Mobile Thomas Künneth gives us a deeper insight:

Can you describe the rough development process of an app from the customer inquiry to the finished product in a few steps?

There is no generally applicable process, the development processes are as diverse as our customers. Some customers come to us with a vague idea and we then work out the range of functions and the appearance together. Some already have very specific requirements for the finished product.

In any case, the requirements analysis is important. Every project begins with her. It is discussed with the customer which functions he would like for his app. Of course, misunderstandings are possible here, so good, open and continuous communication is the key to successful cooperation. Incidentally, the requirements analysis does not end with the start of implementation, because requirements can of course change in the course of the project. Chiselling them in stone at the beginning only ensures that the customer is disappointed in the end because they don't get what they imagined.

Ideally, the customer has an approximate idea of ​​the finished app and still gives the development team creative freedom so that we can advise and develop an ideal product together. Then the work is a lot of fun!

Communication with the customer is therefore crucial. And how does the communication work in your team?

That depends on the size and type of the customer project. In general, we maintain a regular exchange, which is not formally regulated for smaller projects. If the customer wants to actively participate, we rely on the "usual suspects" in agile projects such as daily, planning and review, of course in addition to the spontaneous exchange already mentioned.

Close cooperation and frequent discussions are important so that team members can keep each other on track. If you have a board in front of your head, your colleagues can recognize it more easily than you can and offer help quickly.

What do you think is the most important thing for a successful app development process?

Good communication both with the customer and within the team are the be-all and end-all. It is also important to regularly examine and evaluate the status quo, and make adjustments if necessary. For this reason, we present our customers with a version of the app approximately every two weeks. This means that he has the opportunity at an early stage and regularly to address things that he believes have not been implemented correctly so that we can make appropriate adjustments.

Mistakes and misunderstandings are human and occur. Accept it, take your lesson from it, and move on. Every mistake has the potential to learn something new and develop further.

Here is a little insight into various apps from our mobile team:

Would you like to find out more about our mobile team?

Then click here!