How editors are selected
We prioritize recent products or tools with a specific current question: a platform launch, a pricing change, a PSD workflow or a connection to PhotoCraft. Age alone does not disqualify a tool; a long feature list alone does not qualify it. The collection is a shortlist, not an exhaustive software directory.
Media coverage and user questions can suggest interest, but they do not establish monthly search volume. We do not publish invented traffic estimates or treat GitHub stars as users or demand measurements.
Product claims and independent tests
A product page supports a vendor statement. A repository can document a license or a limitation. A hands-on result needs a particular version, system, file and procedure. We label source-checked information and do not describe it as a tested review.
“Unknown,” “not tested” and “unsupported” mean different things. We reserve “unsupported” for an explicit documented boundary or a scoped test result, and retain relevant context when a developer supplies their own test.
Link to the original publisher
Download links point to the official repository or product site. We do not mirror installers or claim that a package is signed, scanned or safe without evidence. Package names, architectures and release identifiers stay explicit.
Updates, corrections and commercial links
A checked date records when the relevant information was reviewed. It is not automatically refreshed to make an old page appear new. Send corrections with a source and page URL to [email protected]. Material changes should be reflected in both language versions.
The launch site has no paid placement or affiliate links. If commercial relationships are introduced, affected recommendations and outbound links must carry clear disclosure. Inclusion does not mean endorsement or a guarantee of performance.