In a medical app, an unclear screen is a risk, not an inconvenience

A medical app works in conditions where a mistake has consequences for the patient. A doctor uses it in a hurry, between appointments, and a patient often uses it for the first time and under stress. That is why the design starts with observing work in the surgery and talking to users, and we check every screen for errors, legibility and accessibility.

A UX audit of a medical app costs from PLN 4,500 net for one area of the product. An audit of a whole app or system starts at PLN 8,000 net, and the widest package at PLN 15,000 net. Work outside the packages is billed at PLN 250 net per hour. We give the price after a short conversation about scope.

An audit of an existing system takes from one to four weeks. A clickable prototype of a new app takes a few weeks, and a first version ready for use a few months. We set the schedule after the product workshop, once the scope, the integrations with the clinic's systems and the regulatory requirements the product must meet are known.

The result is a report with a list of problems ranked by their impact on staff work and patient safety. Each problem has a description and a recommended change. After the audit you know what to fix first and what can wait. We go through the report with the team responsible for the product so that the recommendations make it into the work plan.

Accessibility is a practical requirement and, in some cases, a legal one. The European Accessibility Act has applied since June 2025 and covers products and services aimed at consumers; whether it covers a specific medical app needs a legal assessment. The standard the regulations refer to is WCAG. Medical apps are used by older people and people with visual or motor limitations, so we check contrast, text size and screen reader support in every project.

Yes, we design apps on the assumption that they will exchange data with the systems the clinic already has. This covers electronic medical records, laboratory systems and payments. We set the scope of integrations at the start of the project, because it determines the architecture, the schedule and the cost. How the connection is made depends on the interfaces provided by the supplier of the given system.

We build mobile apps in Flutter, so a single codebase runs on iOS and Android. The web part, for example a reception or doctor dashboard, is developed separately and connected to the app. In the skin cancer diagnosis project, the mobile app and the web reception dashboard were built in the same technology.

Cooperation begins with a conversation about the product, the users and the regulatory constraints. For a working system the first step is a UX audit, and for a new product a product workshop. After that stage the team has the scope, the priorities and an estimate for further work. After launch we cover the product with technical maintenance under an SLA.