Analyzed automatically. Assessed 2026-10-05 from 966 user reviews, the store listing and its privacy label. We have not scanned the app's package, so nothing on this page was read from inside the app itself.
App Store
This analysis describes version 6.38.3 of the app, analyzed 2026-10-05 . The app may have changed since.
The store currently lists version 6.38.3, updated 2026-09-29.
Google Play
This analysis describes version 6.38.1 of the app, analyzed 2026-10-04 . The app may have changed since.
The store currently lists version 6.38.1, updated 2026-09-27.
What the analysis found
Positive evidence 1
Things this app does right, published at the same strengths as the catch list.
One source only — shown, not confirmed 1
A single kind of evidence. We publish these because withholding them would be the bigger distortion, and we do not treat any of them as a finding we stand behind.
What reviewers said
Verbatim excerpts from public store reviews, shown as corroborating user reports. They are not Appworthy audit evidence, and a quotation is not proof of the finding it sits under.
Paywall blocks the basics
Absurd to have features that we have used for 6 years moved behind a paywall. App typically works pretty well. Occasional difficulty in making initial connection to the Rest products, but doesn't tend to impede use. Loss of features over…
I'm glad that we have something like our MyRest+ but too many features are locked behind a paywall that doesn't make the cost worth it and I truly doubt understand how it always takes SO long to connect. the app constantly restarts itself…
buggy and money grabbing. Don't buy their newer products as they gatekeep normal features with subscriptions. We used to buy one for every new family but now you have to pay for stuff that used to be free. if you are alright with a…
What this app sells
How the automated analysis works
This assessment is produced automatically. Three independent signals are read — user reviews, the store listing and the store privacy disclosure — and each candidate finding is filed under the sources that support it.
No charge stands on one kind of evidence — with one published exception. A finding is either a measured fact that anyone can reproduce (an ad SDK is in the package; every subscription bills weekly; the privacy label omits a tracker we can see), or it is an interpretation — and an interpretation needs independent sources to agree before it reaches the catch list. The exception is a harm only users can see: a charge may publish from reviews alone, as “Reported by N users”, once enough reviewers raise it to clear that charge’s own published bar. That agreement rule is what replaced the human reviewer, not a model’s confidence.
There is no overall score, on purpose. A 0–99 number was published here until 2026-09-15. It was withdrawn because it discriminated too weakly to be the instrument — 44.7% of every pair of apps tied — and because a single number is a verdict where a count is an observation. What publishes instead is a row of measurements, each of which says what was counted and, where we could not look, says that instead.
Findings under One source only are real reports we do not stand behind as findings. They are shown because withholding them entirely would hide a genuine complaint, and labelled because publishing them as charges would be an accusation off a single source.
Several measurements above say “Not assessed” because no artefact we hold can answer them. A human review is what resolves those — and it can remove a favourable band as easily as add one.
Hands-on inspections are not yet open.