Guidelines
- Fact-based descriptions
- Features and requirements are drawn solely from the developer’s official store listing.
- Plain language
- Technical terms are explained where needed, but hype and exaggeration are avoided.
- Transparent limitations
- We note what an app doesn’t do as clearly as what it does.
- User autonomy
- Information is presented to help you decide, not to persuade you to install.
Our method
We describe apps based on verified store details, avoiding speculation or unsupported claims.
Content is structured to help users understand functionality, permissions, and practical use cases.
We prioritize clarity over promotion, ensuring information is accurate and useful for decision-making.
