Editorial Guidelines

Editorial Guidelines

AndroidDocs publishes hands-on, independent reviews of Android development tools, mobile SaaS, and hosting platforms. This page documents the standards every review must meet before publication.

The Testing Floor

No tool is reviewed without at least 30 days of real project use. Synthetic benchmarks (“we ran 1,000 events through it”) don’t capture the friction that costs teams hours per week. Daniel ships every tool reviewed in either a personal project or a client engagement before writing.

Specific Metrics We Track

Latency (ms)
P50, P95, P99 round-trip times for SDK API calls.
Memory (MB)
APK size impact and runtime memory footprint.
API call volume
Calls per session, batching behavior, network overhead.
Setup time (hours)
Hours from “npm install” or Gradle dependency add to first working call.
Monthly cost ($)
Renewal pricing (not promo), with hidden cost flags.
Crash-free rate (%)
Production stability when the SDK is integrated.

Standards for Recommendations

A tool can be recommended on AndroidDocs only if:

  • It runs under at least 30 days of real project use without unrecoverable failure
  • Setup completes within the documented “quick start” time on a stock M-series Mac running Android Studio
  • Pricing is transparent — no surprise per-MAU jumps not disclosed at signup
  • The Android SDK has been updated within the last 6 months
  • The vendor responds to support tickets within their stated SLA during testing

Conflict of Interest Policy

Daniel does not accept payment, free hardware, or “sponsored content” arrangements in exchange for reviews. Affiliate commissions exist (see disclosure) but never influence ranking or coverage decisions. If a tool that pays no commission ranks higher than a tool that does, that’s the published order.

Corrections

Errors are corrected within 48 hours of notification. Material corrections (changing a recommendation, fixing a benchmark error) are noted at the bottom of the article with the date and what changed. Email corrections to daniel@androiddocs.com.

Sources We Cite

Reviews link to authoritative primary sources only — vendor documentation, official Android Developer reference, kotlinlang.org, Google Play Console release notes, and recognized Android community engineers. We never cite SEO content farms or AI-generated round-ups.

Annual Re-Test

Top-recommended tools are re-tested every 12 months. Pricing changes, breaking SDK updates, and acquisition events (vendors that get bought tend to degrade) are flagged in updates noted on the article.

Last updated: May 1, 2026