Skip to content

Data Methodology

Jump to bottom
devradarapp edited this page Jan 6, 2026 · 1 revision

Data Methodology

How DevRadar gathers, verifies, and maintains compatibility data and tool information.

🎯 Our Mission

DevRadar helps developers make informed tech stack decisions. We believe transparency about our data sources and methodology builds trust and helps the community.

📊 Data Sources

Primary Sources

Source Type Usage
Official Documentation Primary Capabilities, requirements, best practices
GitHub Repositories Primary Issues, discussions, pull requests
Release Notes Primary Breaking changes, deprecations
Changelogs Primary Version-specific changes

Community Sources

Source Type Usage
Stack Overflow Secondary Real-world issues, solutions
Reddit (r/webdev, etc.) Secondary Community experiences
Discord Servers Secondary Official channel discussions
Developer Blogs Secondary Workarounds, patterns

Direct Testing

For critical compatibility rules, we verify behavior in isolated test environments.

🔍 Research Process

Step 1: Initial Research

When adding a new technology or compatibility rule:

  1. Search official documentation for integration notes
  2. Check GitHub issues for known problems
  3. Browse community forums for reported issues
  4. Identify version-specific requirements

Step 2: Compatibility Mapping

Document the compatibility status between technology pairs:

Status Categories:
- Compatible: Works without issues
- Partial: Works with limitations/workarounds
- Incompatible: Fundamental conflicts
- Deprecated: Previously worked, no longer supported

Step 3: Issue Documentation

For partial/incompatible pairs, we document:

  • Root Cause - Why the incompatibility exists
  • Affected Versions - Specific version ranges
  • Workarounds - Known solutions
  • Sources - Links to supporting documentation

Step 4: Periodic Updates

Technology ecosystems evolve rapidly. We re-research:

  • New compatibility issues in recent versions
  • Previously incompatible pairs that now work
  • Deprecated technologies and migration paths
  • New workarounds discovered by the community

📚 Data Categories

1. Frameworks

Focus areas:

  • Server Component support
  • Edge Runtime compatibility
  • Build tool requirements
  • Version upgrade paths

2. Databases

Focus areas:

  • ORM/ODM compatibility
  • Connection pooling
  • Edge Runtime support
  • Deployment considerations

3. Hosting Platforms

Focus areas:

  • Build process support
  • Environment variable handling
  • Edge function capabilities
  • Database connection limits

4. Authentication

Focus areas:

  • Framework integration
  • Server Component support
  • Edge Runtime compatibility
  • Session management

5. AI Coding Tools

Focus areas:

  • Supported frameworks
  • Deployment options
  • Pricing models
  • Limitations and constraints

✅ Quality Standards

Source Attribution

Compatibility rules cite sources when based on specific documentation or community reports.

Version Specificity

We note which versions are affected when compatibility varies across releases.

Example: "Next.js 15 + Prisma 6"
- Compatible: Yes
- Notes: Requires Server Action pattern
- Versions Tested: Next.js 15.0.x, Prisma 6.0.x

Workaround Verification

Suggested workarounds are tested before inclusion (when possible).

Regular Audits

We periodically review existing rules for continued accuracy.

⚠️ Limitations

Not Exhaustive

We cannot cover every possible technology combination. We prioritize:

  • Popular frameworks (Next.js, React, Vue, Svelte)
  • Major databases (PostgreSQL, MongoDB, Supabase, Firebase)
  • Common hosting platforms (Vercel, Netlify, Cloudflare)
  • Leading AI tools (Lovable, Bolt.new, Cursor, Claude Code)

Point-in-Time

Compatibility can change with new releases. We update regularly but cannot guarantee real-time accuracy.

General Guidance

Our rules reflect common scenarios. Your specific use case may have unique requirements.

Not a Substitute for Testing

DevRadar helps avoid obvious pitfalls, but thorough testing of your specific stack is always recommended.

🔄 Update Frequency

Content Type Update Frequency
Compatibility Rules As issues are discovered/reported
AI Tool Reviews Monthly or when major updates occur
Framework Updates Within 2 weeks of major releases
Community Reports As verified

🤝 Community Contributions

Found an inaccuracy? Have data to share?

Report Issues:

  • Incorrect compatibility status
  • New compatibility issues discovered
  • Workarounds not documented
  • Updated information

Submit a Report →

📜 Data License

Compatibility data and tool information are compiled from publicly available sources.

  • Facts (compatibility status) are not copyrightable
  • Original text (summaries, explanations) are MIT licensed
  • Sources are attributed where applicable

🔗 Related Resources

Transparency builds trust. If you have questions about our data, contact us.

Clone this wiki locally