Topics

Modernise existing apps

We update apps for new operating systems and store requirements. We assess which features and technical components can be reused and which need replacing.

Typical triggers

The framework is no longer maintained. The store requires a new target version, and nobody can build the application reliably. The original provider has left. A new feature does not fit the architecture. Documentation no longer keeps pace with the application.

Examine functionality and technical structure

We analyse the existing application's features, workflows, data model, technical foundation and dependencies. We have developed our own AI-assisted analysis method, which also examines program structure and data processing. The investigation uses the documents and components available and permitted for each engagement.

The result is an organised knowledge base. Confirmed findings, inferences and open questions remain distinct. Together, we use this foundation to decide which parts remain viable and where a new solution is needed.

Adapt selectively or rebuild

A rebuild may make sense when the technical foundation is no longer viable or major changes are already needed. In other cases, targeted changes are sufficient.

We consider effort, operations, dependencies and future requirements together. A small short-term intervention may complicate later changes; a complete rebuild may create unnecessary work. Analysing the existing system makes this comparison possible.

A real-world example

We rebuilt Takeda's ID+ patient app in six weeks. Without a replacement, the existing app would have been removed from the store. The work produced a technical foundation for further applications for the same client.

Documentation is maintained too: screen records for each version are generated automatically. Specialist review and approval remain with the client.

The result of modernisation

A sustainable technical foundation and clarity about functions and dependencies. The accompanying documentation makes future development decisions easier. Maintainability and the possibility of changing providers later are considered in implementation, documentation and usage rights.

The first step

Describe the application and what lies ahead. We will clarify what can already be assessed and the scope needed to review the existing system.

Read more