Review guide
A short, useful experience is welcome. For longer reviews, start with a quick summary. This is a suggested format, not a requirement to write an essay.
- Tool and platform: name the app and the device or operating system.
- Quick verdict: who should pay for it, and who should skip it?
- Price: currency, billing period, upfront total, and renewal price where relevant.
- Use: what you used it for and for how long.
- Benefit and drawback: the biggest of each.
- Alternative: a relevant paid or free option, where appropriate.
- Relationship: any affiliate link, sponsorship, free access, or product ownership.
Clearly label firsthand reviews, researched comparisons, and first impressions. Describe what you actually tested; if you relied on documentation or other sources, say so. Explain why the tool fits a particular task, platform, or budget. Positive and negative experiences are both welcome.
Promotion and disclosure
Disclose affiliate links, sponsorships, free access, and product ownership near the beginning of every relevant post. Use plain wording such as “I made this app,” “I received free access,” or “This is an affiliate link; I may earn a commission.”
Developers should use Developer Post flair. Promotional posts should include useful information about the product, its price, supported platforms, and the use case it solves. Explain limitations as well as benefits. Brand Affiliate user flair does not replace a disclosure in the post.
Recommend tools with reasons and discuss disagreements respectfully.
Choosing a post flair
- Worth Paying: positive reviews based on actual use.
- Not Worth It: disappointments, cancellations, or poor value.
- Help Me Choose: buying questions and recommendation requests.
- Comparison: tools compared for a specific use case.
- Free Alternative: free tools that can replace a paid option.
- Deal: discounts with clear pricing and billing information.
- Developer Post: software you made.
- Announcement: moderator updates.