Too little checked to say Only 250 reviews read, too few to say.
From our automated analysis, 27 Oct 2026.
This analysis describes version 9.1.2 of the app, analyzed 2026-10-27 .
The store currently lists version 9.1.2, updated 2025-06-24.
Store screenshots supplied by the developer.
Designed to manage both Freshwater and Saltwater aquariums!
Available in 13 languages: Català, Dansk, Deutsch, English, Español, Français, Italiano, Polski, Português, Română, Русский, 中文(简体), 中文(香港).
Includes a very comprehensive livestock library of both Freshwater and Saltwater fish, coral, invertebrate and plant species with smart compatibility advice with your fish!
Features:…
From the developer’s store description.
For developers and the curious
The evidence, sources, measurements and versions behind every label above.
No review-based observation is published in this assessment. That does not establish that reviewers had no problems.
“Not assessed” means we could not measure it. It is never a zero and never a pass.
No package has been scanned for this app, so nothing is published about what it ships. That is an absence of evidence, not a finding.
Supporting measurements: not a complete list of possible harms or positives. Measurement vocabulary 1.4 · how these are measured
This analysis describes version 9.1.2 of the app, analyzed 2026-10-27 .
The store currently lists version 9.1.2, updated 2025-06-24.
Each store’s release notes, as the developer wrote them. They are the developer’s words, not ours.
This app has been updated by Apple to prepare for watchOS 27 compatibility. No new features are included. - Fixed rendering issue on large datasets in the Analytics view. - Added support for Nitrate and Phosphate data from Apex Trident NP. - Performance improvement. - Bug fixes.
Appworthy
aquarimateAssessed 2026-10-27 from 250 user reviews and the store listing. We have not scanned the app's package, so nothing on this page was read from inside the app itself.
What the stores publish. Store ratings are the stores’ numbers, not Appworthy’s, and are never averaged across stores.
From the store listing. Billing terms are read from each purchase’s name — the stores don’t publish them — so treat them as a strong hint, not a disclosure.
These are really on sale; we just can’t tell from the name whether they recur.
This assessment is produced automatically. Two independent signals are read — user reviews and the store listing — 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.
Write to [email protected], or use the form. Name the finding, the app version and the evidence that needs correcting. Factual corrections are free and never depend on buying anything.