How to check a health app before installing it, using only its own App Store page

This is a checklist for reading a symptom-tracking app's own App Store page before you install it — not a review of any specific app, and not medical advice. It's a way of reading a product page that any of these apps could be run against, ours included.

It's worth saying plainly who's writing this. We make one of these apps — MeteoHealth: Symptom Tracker — and a checklist from the team behind a product is an odd thing to trust at face value. The honest response isn't to claim a neutrality we don't have; it's to build the list so it can be pointed at our own page and used to pick something else, and then actually do that, out loud, wherever it applies. For several of the twelve questions below, the answer this checklist gives about our own app is a real weakness, stated without softening — the test this article has to pass to be worth reading.

Does it keep a record at all

Before anything else, a page has to answer a narrower question than "is this a health app": does it actually keep a record of how you feel over time, or does it just display an external number next to a note you type in once? Everything downstream — correlation, trend, pattern — depends on there being a record to work from. The description and screenshots usually show which: entries accumulating over days or weeks with dates attached, or a single live reading with a place to jot something next to it. A page that only shows the second is not describing a tracker, whatever the icon or category suggests.

A narrower question sits right behind the first: does the page claim to compute a connection between an external factor and those records, or does it just place the two side by side — a weather reading here, a symptom note there — and leave the connecting to you? Both are legitimate things for an app to do, but they're different products. The honest limit, though, applies to every app making this kind of claim, ours included: no page we've seen states, in the description, exactly how the correlation is computed — what method, what window of data, what threshold counts as a pattern. That's not a gap specific to us; it's a gap in what App Store descriptions disclose generally, and "correlation" written in a description is a claim, not a specification.

What you're actually allowed to record

Once you know the app keeps a record, the next question is what it lets into that record. Some apps offer a fixed list of symptoms or metrics chosen by the developer; others let you define your own trackers — a custom symptom, a custom scale, a factor the developer never anticipated. The description and screenshots usually show which: a fixed list reads as named categories with no way to add to them, while a customizable one usually says so directly, often with a word like "customize" or "your own."

Here's where this checklist points at us directly: MeteoHealth's symptom list is fixed. You log from a set list; you can't define a new symptom or metric of your own. For someone who wants to track something we didn't anticipate, this app is not the right tool, and no amount of correlation math on the back end changes that. If open-ended, self-defined tracking is what you need, this is the question where you should stop reading about us and keep reading about something else.

What the privacy card actually says

Every app's page carries an App Privacy card with one of four possible headings: Data Used to Track You, Data Linked to You, Data Not Linked to You, or Data Not Collected. These are Apple's own categories. "Data used to track you" is Apple's own definition: "Data used to track you refers to data from the app that is linked with your data collected from other companies' apps, websites, or offline properties, and used for ads or shared with a data broker." "Linked to you" is the other side of it: "Data that is listed as linked to you means that the data is collected in a way that is linked to your identity, such as to your account, your device, or your details."

Read the heading, then the categories under it. And read this literally, because it changes what the card means: it's filled in by the developer. Apple's own words: "This program creates an easy-to-understand system for all apps, where the information is self-reported by the developer," and, to developers directly, "You're responsible for keeping your responses accurate and up to date. If your practices change, update your responses in App Store Connect." A standard line sits under every card: "Privacy practices may vary, for example, based on the features you use or your age." The card may not be the only one an app ships, either — a free and a paid version can carry different declarations, and the declaration can differ by region, by Apple's own guidance. None of this means a declaration is false; it means it's a statement the developer makes and is responsible for, not an independent measurement.

Does it need an account

A page will sometimes say directly whether an account is required — in the description, or a screenshot of a sign-in step. Often, though, it doesn't say either way, and the more reliable place to check is the privacy policy, usually linked from the same page. If neither settles it, the honest thing to write down is "the page doesn't say" — that's a real answer, not a gap in your research.

Will it even run on your device

The Compatibility block states supported devices and the minimum OS version required for each — iPhone, iPad, Mac, Apple Watch, whatever the developer has built for. This is the least interesting-sounding question on this list and one of the most decisive in practice: it doesn't matter what else an app does well if it won't install.

Here's where the checklist points at us again. MeteoHealth requires iOS 17.0 and iPadOS 17.0 or later — a higher floor than some apps in this category require, and it means the app simply won't install on an older iPhone still running an earlier version of iOS. If your device is a few years old, check this block first, because nothing past it matters if the app won't run.

Is there an Android or web version

This is a case where the App Store page itself has nothing to say — the Compatibility block on an iOS listing describes Apple devices, not other platforms, and there's no field that answers "is there an Android app" or "is there a web version." The only way to check is the developer's own website, linked from the page under Developer Website — an extra click, not a glance.

Said plainly, since the page won't say it for us: MeteoHealth has no Android version and no web version. It's an Apple-platforms app — iPhone, iPad, Mac, Apple Watch — and nothing else. If your household runs a mix of Android and iPhone, or you want to check your history from a browser, that gap is real and this checklist won't make it go away.

How many interface languages, and is yours one of them

The Languages block lists every interface language the app ships in — the language of the buttons, menus, and screens, not the content you'll log. Check it against your own language specifically, not just the total count: a long list that doesn't include your language answers the question just as clearly as a short one.

For us directly: MeteoHealth ships in six interface languages — English, Russian, Spanish, Japanese, Simplified Chinese, and Arabic. That's fewer than some apps in this category carry, and if your own language isn't on that list, that's a real limitation for you, whatever the total looks like next to anyone else's.

How many ratings, not how many stars

A star rating on its own tells you almost nothing without the count behind it — 4.9 stars from twelve ratings and 4.9 stars from twenty thousand are not comparable claims, even though the number looks identical. The count sits right next to the star average, worth reading before the stars register at all. It can range from a few dozen to tens of thousands, and a small count isn't automatically dishonest — a new app has to start somewhere — but it does mean the average next to it hasn't been tested by many people yet. When a page has too few ratings to compute one, Apple's own line appears instead: "This app hasn't received enough ratings or reviews to display an overview."

Point that at us and the answer is deliberately not a number we quote here. MeteoHealth's first release was 2026-07-24 — that date doesn't move — so however long it has been since you're reading this, that's exactly how much track record the app has had time to build. Open our own page and read the count for yourself rather than taking a figure from an article: at the top end of this category, established trackers carry ratings in the tens of thousands, and whatever we show today is somewhere below that. A number printed in an article decays; the instruction to go and look does not, and this is a checklist about looking.

What's free, what's behind the paywall, and in what currency

The In-App Purchases block, read alongside the description, is where the free tier's actual limits and the paid tier's actual contents are stated as line items, not implied by the app's category. Read the price in the currency your own storefront shows: Apple generates prices across storefronts automatically from a base price the developer sets, across, in Apple's words, "174 storefronts and 43 currencies" — a price quoted for a different country's storefront isn't necessarily what you'll be shown.

Our own split, stated directly — and for the price, the same instruction as above: read it off the In-App Purchases block on our page, in your own currency, not off this sentence. The free tier keeps seven days of history, a 24-hour forecast, and ten scans a day. Pro adds full history, an extended seven-day forecast, unlimited scans, the detailed correlations, the Apple Watch app and widgets, and PDF and CSV export. Read that against what you actually need: several of the features that matter most for tracking a real pattern over time — the Watch app, the wider forecast, the detailed correlations, exporting anything at all — sit behind that paywall, not in the free tier.

How long since it was last updated

The What's New section, and the Version History behind it, show the date of the most recent update and the version number — but only for an app that has updated at least once. An app on its first version has no update history to show, and the page doesn't display a first-release date anywhere; that date, when it matters, has to come from somewhere other than the page itself.

For MeteoHealth, this is the second answer we're deliberately not freezing into a number. The app was released on 2026-07-24 with no update history behind it, for the obvious reason that there hadn't been one yet. What the What's New section says by the time you read this is the actual answer, and it's on our page, not in this paragraph. Either way the underlying point holds and isn't dressed up: how an app is maintained after release is something only elapsed time can demonstrate, and a release date this recent means there is less of that evidence than an older app can show.

Does it claim more than a tracker should

Last, and worth checking regardless of everything above: does the description claim the app can tell you an attack is coming before it starts, or that it resolves a condition outright, or otherwise claims outcomes that belong to a medical device or a clinical intervention, not a symptom tracker? A symptom-tracking app, whatever its correlation claims, is not that kind of device, and a page that reads like one deserves real skepticism, whichever app makes it. There's no symmetric version of this one pointing back at us: staying within that boundary isn't a feature or a point in an app's favor — it's the baseline any app in this category should meet, and there's nothing to congratulate here, ours included.

The map above lines up each of those questions with the exact block on the page where its answer lives — and the last row is deliberate: it names what the page doesn't answer at all, because a checklist that only shows where answers live would quietly imply the page answers everything, and it doesn't.

Where this checklist leads away from us

Running through this list against our own page, in one place rather than scattered above: the symptom list is fixed, not customizable. The minimum OS is iOS 17.0, higher than some alternatives require, so it won't install on an older iPhone that a lower-floor app still supports. There's no Android version and no web version at all. The interface ships in six languages, and if yours isn't one of them, that's a real gap, not a rounding error. The first release was 2026-07-24, and the rating count and update history that follow from a date that recent are on our page for you to read rather than quoted here — nothing in this article substitutes for a track record that only elapsed time can build. Several of the more substantial features — the Watch app, the full forecast window, the detailed correlations, PDF and CSV export — sit behind the Pro subscription, not the free tier. Anyone whose priority is open-ended tracking, a mixed-platform household, an older device, an interface in a language outside that list, or a product with a longer track record should, by this same checklist, end up choosing something other than MeteoHealth. That's what the list above actually says when it's pointed at us.

What to do with the answers

None of the twelve questions above requires installing anything — every one is answerable from the page itself, before a download. A few early answers (does it keep a record, will it run on your device, is your language supported) can save you from reading the rest of a page that was never going to fit what you need. Where the page stays silent — an account requirement, the exact correlation method, a first-release date — write down "not stated" rather than assuming an answer either way; that's the accurate result of the check, not a failure of it.

For a worked example of this same method applied across three apps at once, see our comparison of MeteoHealth against two established symptom trackers. And if the fixed symptom list above is where this checklist sent you looking elsewhere, the symptom journal feature page describes exactly what that list covers and doesn't.