Publication standards
Publication Policy
ProjectRadar is a practical indie discovery site for indie projects, apps, games, websites, AI tools, SaaS products, calculators, utilities, creator tools, education tools, downloadable programs, and useful side projects.
The goal is simple: help readers discover useful things and help builders get a fair, independent look. We care about clarity, usefulness, trust, and reader value more than hype.
Project notes are written to help readers understand the developer-provided description, what stands out, who it may help, and what I would check next.
Independent
Submissions and money do not buy conclusions, category position, or favorable coverage.
Human-checked
Research tools may organize notes, but public takes need human judgment.
Correction-friendly
Founders and readers can ask us to review factual issues or meaningful product updates.
Purpose
Our publication purpose
ProjectRadar exists to help readers discover useful projects without turning discovery into a pay-to-play list. Coverage focuses on usefulness, clarity, audience fit, trust cues, public context, and discoverability.
A good project note should help a reader decide whether a project is worth exploring. It should also give a builder a fair, limited view of what stands out and what could be clearer.
Note process
How project notes work
Project notes may use submitted information, developer-provided descriptions, public product pages, app listings, documentation, screenshots, demos, access, and the public context a reader would reasonably see before trying the project.
What we may consider
- Submitted project details
- Developer-provided descriptions
- Public product pages
- App store or directory listings
- Documentation and screenshots
- Demos, trials, test builds, or project access
- Public trust, clarity, SEO, and discoverability context
Questions we ask
- What does the project do?
- Who is it most useful for?
- Is the promise clear enough for a reader to understand quickly?
- What works well right now?
- Where could the project become more useful, trustworthy, or discoverable?
Tanner evaluates what the project says it does, who it appears to serve, how clearly it explains itself, what feels useful, and what a curious reader might check next. Notes should be useful to readers and fair to builders.
Read how project notes workFactual boundaries
What we do not invent
ProjectRadar does not make up claims to make a project sound bigger, safer, more popular, or more successful than the available evidence supports.
- Founder details
- Revenue
- Traffic
- Customer counts
- Testimonials
- Awards
- Leaderboard claims
- Performance claims
- Partnerships
- Security claims
- Search visibility claims
Submissions
Submissions and coverage
Anyone may submit a project. Submission helps us discover what builders are launching, but it does not guarantee coverage, publication, placement, backlink access, search visibility, traffic, customers, or positive coverage.
Projects may be listed, covered, queued, declined, or revisited later. Fit and reader value guide those decisions.
- Guaranteed writeup
- Guaranteed publication
- Guaranteed placement
- Guaranteed backlinks
- Search visibility outcomes
- Guaranteed traffic
- Guaranteed customers
- Guaranteed positive coverage
Temporary access
Temporary access stays private
Developers may provide temporary project access for paid products, apps, private betas, games, invite-only tools, SaaS products, downloadable programs, or utilities that cannot be fully evaluated from a public page.
Access is used only for project note evaluation. ProjectRadar does not publish private access details, promo codes, invite links, demo credentials, or test build links.
Discovery context
At-a-glance discovery context
ProjectRadar's Discovery Context is a soft read on a project's public-facing context. It may consider clarity, usefulness, audience fit, product readiness, trust cues, design and UX, discoverability, and public founder or project context.
Discovery Context is a reader-style summary, not a promise about what will happen after publication. It is not a user rating, certification, expert audit, guarantee, safety claim, quality claim, or paid placement.
- Not a user rating
- Not a certification
- Not a guarantee
- Not paid placement
- Not a partnership endorsement
- Not a search performance claim
Independence
Independence and paid placement
ProjectRadar editorial notes are not purchasable. Sponsored placement buys visibility only and does not change project notes, conclusions, category eligibility, or editorial picks.
- Discovery context labels
- Category position
- Hidden promotion
- Favorable coverage
- Search placement
- Undisclosed sponsored links
Sponsored links and paid visibility will be labeled. Sponsored links should use appropriate attributes where applicable, such as rel="sponsored" or rel="nofollow".
Learn how ProjectRadar earns trustCorrections
Corrections and updates
Founders and readers can request factual corrections. A useful correction request includes the project name, project note URL, and the specific issue to check.
ProjectRadar may update project notes when products materially change, launch important new functionality, fix previously noted issues, or become meaningfully clearer for readers.
Corrections do not guarantee changed opinions, context labels, or conclusions unless the underlying facts support that change.
Request a factual correctionFounder path
Submit the clearest public context you have.
ProjectRadar uses your project URL, submitted details, and any safe access notes to decide whether a useful public project note can be prepared.
Keep exploring