Becoming a Certified Developer
The certified mark shows developers who passed our review and keep their standard: the five criteria, what the mark gives you and how it is lost.
Overview
Certification is not bought and not requested on a form. It is earned: developers who meet the criteria are reviewed, and the mark is granted by the team.
You cannot switch it on yourself. The profile dialog edits your name, tagline and links; the mark and whether the profile is published are the team's decision.
The mark is not permanent. It is reviewed periodically and can be removed when the standards are no longer met.
Prerequisites
Structure
The mark appears on three screens and means the same thing on all of them.
| Where | What changes |
|---|---|
| Developer directory | Your card carries the mark and certified developers sort to the top of the list |
| Your public profile | The mark sits next to your name; visitors can open it to read the criteria |
| Product pages | It appears in the byline, beside the developer name |
The directory sorts by certification first, then by the rating the products earned, then by how many are published. The mark lifts you above developers with a similar rating.
Walkthrough
Meet the criteria
- Get three products live. The first usually takes longest; the next ones move faster through the same path.
- Watch the reviews. The average is computed from all your published products, not from the best one.
- Test your products on each new WISECP release and ship a new version when one is needed.
Be ready for the review
- Fill in the support and contact addresses on your profile. The response criterion runs through them.
- Keep your product documentation current. Products with missing setup steps generate questions.
- The code and security review is run by the team. There is no separate form to fill in.
Keep the mark
- Reviews repeat periodically, and the mark can be removed when the criteria are no longer met.
- Retiring a product lowers your published count and may put you under the three-product threshold.
- If the mark is removed, your profile and products stay live; only the mark and the sorting priority go.
Reference
Example
The five criteria are read one by one; meeting four of them is not enough.
Published products : 4 -> met (three or more)
Average rating : 4.3 -> met (4.0 or higher)
Compatibility : v5 ready -> met
Response time : ~2 days -> not met (24 hours)
Code review : pending -> run by the teamThis profile clears the numbers but misses the response criterion. The mark is not granted until the missing one is addressed.
Pitfalls
The rating comes from every published product. Leaving an older, poorly rated one unmaintained pulls your newer products down with it.
Each review asks whether the criteria still hold. Retired products and unanswered questions can take it back.
Every new product and every new release from a certified developer still goes through review.
Related Articles
Thanks for your feedback!
Our support team is here around the clock for anything you can't find above.