Complete Market Research Guide for Digital Health Apps

Teams building health and wellness apps make many of their biggest decisions with little evidence. Which feature to build next, how much to put behind a paywall, how long the free trial should be and how much personal data to ask for at sign-up are often settled in a meeting, based on what a competitor seems to be doing. The consequences appear later, in uninstalls, cancelled subscriptions and one-star reviews that are hard to read as a whole.

This category has one feature that sets it apart. People use a meditation, sleep, nutrition, cycle tracking or care app for something personal, and they hand it information they would not share with most products. When they write a review, they often describe more than a bug or a price. They write about whether they trust the app with their data, whether its tracking or guidance feels accurate to them, and whether it fits into their life. Those are the signals that matter most in this category, and app store reviews are full of them.

This guide shows how a team behind a digital health, wellness or care app can turn that feedback into real market research about its own app, its competitors and the market it serves. It is about product and market research, not about the medical value of any app.

Key Research Questions

Research starts with the questions it has to answer. For a digital health app, they fall into three groups: questions about your own app, questions about the apps users compare you with, and questions about how needs in your category are changing.

Your App

The first questions follow the user. Why did they download the app, and what did they hope it would help them with? Where does the experience break: at sign-up, when the app asks for personal information, at the first paywall, when a reminder arrives at the wrong moment or when the data does not sync? Which features do users mention when they explain a five-star review, and which when they explain a one-star review?

The second set is about trust. Do users say they feel comfortable with what the app asks for and how it uses their information? Do they describe the tracking, logging or guidance as reliable in their own use? In this category, a doubt about trust can outweigh any feature, so it deserves its own place in the research.

Your Competitors

Your competitors are the apps users try before you, alongside you or after you, and sometimes they are not apps at all: a notebook, a wearable's built-in tracking, a video on YouTube or a conversation with a professional. What do users of competing apps praise that yours never mention? What do they complain about that you already handle well? Their reviews are as public as yours and just as detailed.

The Digital Health Market

The third group is about demand. Which needs are users describing that no app meets well? Are users moving from all-in-one apps to focused ones, or the other way around? How do they feel about subscriptions in this category, and what makes a paid plan feel worth it to them? These questions are hard to answer from download and revenue figures alone, because those show what users did, while the reasons sit in what they write.

Sources of Evidence

Evidence about a digital health app comes from several places, and none of them has to come first. You can analyze reviews without running a survey, and you can study competitors before you have interviewed a single user. The strongest research combines what your own users tell you, what users of every app in your category write in public, and what you learn by asking.

Your Own User Feedback

Support tickets, in-app feedback, answers to onboarding and cancellation surveys and messages sent to your team are the most direct feedback an app has. Cancellation reasons are especially useful, because they are written at the moment a user decides to leave. Collected in one spreadsheet with columns for the date, the plan, the platform and the app version, they become the start of a customer feedback analysis practice.

App Reviews and Public Discussions

App Store and Google Play reviews are the main public source for any app, and they cover your app and every competitor in the same detail. Reviews often name the version, the device and the feature involved, which makes them useful for product decisions. Trustpilot adds reviews of the company behind the app, which often focus on billing, cancellations and customer support.

Reddit communities and comments under YouTube videos add longer conversations: users comparing apps, describing what they switched from and asking each other what works. These are often the clearest record of what people expect from an app in your category.

Surveys and Interviews

Traditional methods still have a place. A short survey at the end of a trial can ask what the user hoped to achieve and what stopped them from subscribing. A conversation with a long-term subscriber, or with someone who cancelled, shows how they decided and what would change their mind. Notes from these conversations are qualitative research, and they need the same structured analysis as reviews to become more than a set of impressions.

Researching Digital Health Apps with Kimola

Kimola is an AI platform that turns customer feedback into enterprise-grade market research. For a digital health app, that means taking reviews of your app and of the apps you compete with, together with your own support tickets and survey answers, and turning them into a structured study of why users come, where trust breaks and what keeps them subscribed. The steps below follow the order a researcher would work in, and you can start with a free account, without a credit card.

User reviews in this category can include personal health information. The purpose of the analysis is to study patterns across many users, not to examine any individual, and it is worth keeping that principle in how you store, share and discuss the results.

Building the Dataset

After signing up, go to the Create your report area on the Home screen and paste the link to your app's page on the App Store or Google Play, or search for the app by name. With the Add Multiple option you can paste several links, one per line, and Kimola collects the reviews from all of them into a single dataset. A practical first report includes your app on both stores and three or four apps users compare you with. The same works for Trustpilot pages. The support article on creating a report by adding links walks through each screen.

For Reddit threads and YouTube comments, Kimola's browser extension, Airset Generator, collects the feedback from a page and sends it to your account as an Airset, which you can turn into a report. Your own feedback can be uploaded as an .xls, .xlsx, .csv or .tsv file. If the file has columns such as plan, platform, app version or date, Kimola reads them, and you can filter and compare the results by those values.

By default, Kimola finds the themes in the data itself. If you prefer a classifier built for app feedback, the Advanced option lets you choose the Mobile App Feedback Classifier, one of Kimola's pretrained models.

Choosing Dimensions

Dimensions are the research questions Kimola asks of every piece of feedback. You choose them when you create the report or add them later, and the guide to Dimensions explains each one. For a digital health app, five are especially useful.

Motivations asks why users chose the app, such as sleeping better, building a habit, tracking a cycle or getting easier access to care. Pain Points asks what goes wrong, which in this category often covers sync problems, paywalls that appear too early, reminders that feel intrusive, accuracy of tracking as users perceive it and concerns about data. Unmet Needs shows what users wanted and did not find, which is where new features and positioning ideas often come from.

Underlying Causes asks why a problem happens, from the user's point of view. A complaint about a reminder may come from a schedule the app never asked about, and a complaint about value may come from a trial that ended before the user saw any benefit. Personas groups users by who they are and what they need, which shows whether a beginner, a long-term user and someone managing a specific routine describe the same app differently.

Reading the Report

The Overview shows the main themes in the feedback and how sentiment is distributed. Kimola finds those themes in the data itself instead of sorting comments into a fixed list of categories, so a review about the app can be tagged with something as specific as step counts that stop syncing after an update or a bedtime reminder that cannot be turned off.

Each review can mention several themes, and each theme gets its own sentiment. A user who loves the content but is uneasy about a request to share contacts contributes a positive mention of the content and a negative mention of data permissions. A single star rating would hide that the product and the trust it inspires are being judged separately.

The Performance screen ranks themes with a Satisfaction Score and a Dissatisfaction Score. These scores account for how many reviews mention a theme as well as the percentage, so a theme backed by five reviews does not outrank one backed by fifty. This protects against the most common mistake in small-scale research, which is reacting to a handful of loud reviews.

Signals

Signals are findings that have passed a statistical test. Kimola crosses every theme and Dimension with the columns in your dataset, such as app, store, star rating or date, and checks whether a topic is discussed more often or more negatively in one group than in the others (Differences) or more often recently than before (Trends). Only significant results become Signals, and they are ranked so the most important ones come first. The explanation of how Signals are tested covers the method in more detail.

For an app, the date column is especially revealing. A Trends Signal might show that complaints about billing grew after a pricing change, or that concerns about data permissions rose after a new sign-up flow. The store column can show that a topic is discussed more negatively on Google Play than on the App Store, which often points to a platform-specific problem. Signals need enough feedback and at least some selected Dimensions. When the data does not contain a pattern strong enough to report, the report shows none, which is an honest result.

Compare

Compare puts segments of a report side by side: different apps, different stores, or one-star and five-star reviews. Up to five can be compared at once, without using extra queries. In a report built with Add Multiple, the most valuable use is placing your app next to the apps users compare you with and seeing the volume of feedback, the sentiment, the themes you share and the themes that appear for only one app. If users of a competitor keep praising how clearly it explains what it does with their data and yours never mention it, that is a gap worth closing.

Action Plans

Action Plans turn the findings into steps. You start by choosing or creating a Profile that describes your app, what it does and who it serves, then select a perspective: Our own offering, A rival or Our market. These match the three groups of questions at the beginning of this guide. A sensible first plan uses Our own offering with the Product Development goal. Once your report includes competing apps, a plan with the Competitive Strategy goal focuses on how to position your app against them, and a plan with the Customer Experience goal focuses on onboarding, support and trust.

Kimola builds hypotheses from the report, tests each one against the feedback and drops the actions the evidence does not support. Each remaining action comes with a confidence level and explains why it matters, who it is for, when and where to act, the risk involved and how to see that it worked, along with the evidence behind it. A plan contains up to 12 actions. Plans work best when the report already has Signals, as the support article on how actions are built explains.

Kimola also publishes research made on the platform, with its methodology. The studies of meditation apps and period tracking apps, both built from App Store and Google Play reviews, show what this kind of research looks like in the category.

From Findings to Decisions

Research is only useful if it changes a decision. For a digital health app the decisions are concrete, and each one connects to a specific part of the report.

Feature Priorities

Roadmaps fill up quickly, and reviews help decide what goes first. When Pain Points shows that complaints concentrate on one area, such as syncing or logging, and Signals show those complaints growing, fixing it may matter more than any new feature. Unmet Needs shows what users are asking for, and Compare shows whether competitors already offer it.

Trust and Privacy

Trust is a product decision in this category. When Pain Points and Underlying Causes show that users are uneasy about what the app asks for at sign-up, or unclear about how their information is used, the response may be a change in the order of permissions, clearer explanations in the app or fewer requests altogether. Compare shows how users describe trust in competing apps, which is often a useful benchmark.

Subscriptions and Trials

Subscription complaints usually have a specific cause. When reviews concentrate on surprise charges, the issue is how the trial ends. When they concentrate on value, the issue may be that users do not reach the useful part of the app before the trial ends. Underlying Causes helps separate the two, and Trustpilot reviews often show how cancellations and refunds are experienced.

Personalization

Users in this category expect an app to adapt to them, and they say so when it does not. Personas shows which groups feel the app fits them and which do not, and Pain Points shows where generic content or fixed schedules frustrate users. If one group consistently describes the app as not made for them, that is either a segment to serve better or a positioning choice to make deliberately.

User Retention

Users who leave often explain why, in reviews and in cancellation answers. Comparing your own cancellation reasons with public reviews from dissatisfied users shows which reasons repeat. When the same Pain Point appears in both, it is a strong candidate for a real cause of churn. Motivations from long-term users shows what keeps them, which tells you what to protect when you change the product.

Ongoing Research

A single report gives you a snapshot, and an app changes with every release. Repeating the research after major updates, pricing changes or redesigned onboarding shows whether the change moved the themes it was meant to move.

On paid plans, Feeds keep the research running continuously. A Feed collects public mentions from social media, news sites, blogs, forums, YouTube and review sites, based on the keywords and links you define. Alerts email your team when something important happens, and Mailings send a regular summary. Over time, Trends Signals show which topics are rising and which are fading.

Digital Health Companies and Providers

Larger digital health companies and care providers face the same questions across several apps, services and markets. On the Enterprise plan, each source of feedback, such as an app, a support channel or a patient survey, can become a Space, a continuously growing source of feedback classified with the same Funnel, which is a shared set of custom models and Dimensions. Because every source is analyzed the same way, results stay comparable over time and between products. Spaces also calculate an NPS from what users write, on a scale from -100 to 100. It is derived from the positive and negative share of written feedback, so it is not the same as a Net Promoter Score from a 0 to 10 survey.

When a finding needs action, Tasks assign it to the right team with the underlying feedback attached as evidence, and Tasks can be sent to Jira. After a Task is closed, Kimola measures feedback on the same topic again two and four weeks later, so a change can be checked against what users say afterwards. Executive summary screens give leadership a single view of what users are saying across the organization. For organizations that need to keep feedback and analysis inside their own infrastructure, Kimola On-Premises runs in the organization's own environment without sending data to external AI services. Enterprise accounts are set up together with a dedicated Account Manager, and you can request a demo to discuss your setup.

Frequently Asked Questions

A few practical questions come up when a digital health team starts researching with customer feedback for the first time.

Should App Store and Google Play reviews be analyzed together?

Usually yes. One report with both gives you a larger dataset, and the store column lets Signals and Compare show whether users on each platform describe the app differently.

Can reviews tell us whether our app works?

Reviews show how users describe their experience, including whether they feel the app helps them. They are evidence about perception, satisfaction and needs, and they are not a substitute for clinical evidence about outcomes.

How many reviews do I need before the findings mean anything?

There is no fixed threshold, and the ranking on the Performance screen is designed to protect you from small samples by weighing how many reviews support each theme. Adding a few competing apps to the same report is the easiest way to reach a dataset large enough for Signals.

Getting Started

Your users, and the users of every app in your category, have already written down much of what you need to know about trust, value and the features that matter. Create a free Kimola account, add your app and a few competitors to a single report, and see which themes users talk about most. The market research guides for fitness centers and kid apps apply the same approach to neighboring fields, and the market research guide for small businesses covers the method for any industry.