Review Methodology
A GraphiSphere rating is an editorial assessment. It summarises our view of a product’s strengths and weaknesses for the people it is aimed at. It is not a user rating, and it is not a measure of how many people use a product.
Last updated: October 8, 2026
What a rating is and is not
Each review carries a GraphiSphere rating out of 10, with one decimal place, and four sub-scores for features, ease of use, performance and value. These are the judgement of our editorial team, based on the evidence described on this page and in each review’s evaluation basis. Ratings are not averages of reader feedback, they are not derived from search or sales data, and they are not influenced by whether a product has an affiliate programme.
The categories we assess
Every review is structured around the same categories, so that products can be compared on a consistent basis. Not every category carries equal weight for every product. A tool built for print production is judged more on colour and file handling. A tool built for collaboration is judged more on teamwork. The review explains which categories matter most.
Evaluation categories
| Category | What we look at |
|---|---|
| Features | The depth and quality of the tools a product offers for its core jobs |
| Ease of use | How quickly a new user can produce useful work, and how well the interface scales |
| Performance | Responsiveness on large files, documented system requirements and stability |
| Workflow | How well the product fits real production steps, handoffs and file sequences |
| Learning curve | The time needed to reach competence, and the quality of available learning resources |
| Compatibility | File formats, integrations and how well work survives exchange with other tools |
| Value | The cost of the product against what it does, including subscription structure and free options |
| Reliability | The product’s documented stability, update history and support provisions |
| Target audience | Who the product suits, and who should look elsewhere |
How the rating is built
The four sub-scores are assessed separately. The overall rating reflects those scores and the editorial judgement of the product’s role. We weigh the categories according to what the product is for, and we explain the reasoning in the review. A product can have a strong feature set and a modest overall rating if it is hard to learn or costly for its audience.
What the bands mean
- 9.0 and above: exceptional in its category, with few meaningful weaknesses for its intended audience.
- 8.0 to 8.9: strong and dependable, with clear strengths and some trade-offs worth knowing.
- 7.0 to 7.9: good for specific users, with limitations that matter for others.
- Below 7.0: useful in narrow circumstances, with significant gaps for most buyers.
We do not give every product a high score. A rating should help a reader decide, and that requires honest differences between products.
Evidence and evaluation basis
The evidence behind a review is stated in its evaluation basis. Typical sources include the product’s official documentation and feature pages, public release notes, published pricing and plan information, terms of service and independent reporting. Where a review includes hands-on use, we say what was used, for how long and on what hardware. Where it does not, we say that too. We do not claim that a product was tested for a specific number of days or weeks unless that testing took place.
Target audience
Every review finishes with a clear view of who the product suits. We think this matters more than a single number. A professional editor may be the wrong choice for a beginner who makes a few short clips a month, and the reverse is also true. Our verdicts are written to be used, not just read.
Updating ratings
Software changes. When a product changes substantially, including its features, pricing structure, distribution or ownership, we review whether our assessment still holds. A changed rating or verdict is reflected in the updated date on the article, and we note the reason for the change where it matters to readers.
What this methodology does not do
- It does not rank every product in a category, because most categories contain products suited to different people.
- It does not guarantee that a tool will suit your work. Test with your own files and your own process.
- It does not replace official pricing, terms or technical specifications, which change and should be checked at source.