About Daniel Park

Daniel Park is the Android developer behind AndroidDocs. Furthermore, with 11 years of production Android development and a former Google Play developer relations contracting role, Daniel reviews mobile dev tools, Kotlin libraries, Jetpack Compose patterns, and hosting platforms after at least 30 days of real project use. Moreover, every review documents specific metrics — build time, crash-free rate, monthly cost, latency, and setup hours — because vague recommendations cost teams real engineering hours. In addition, Daniel maintains alignment with developer.android.com release notes and tracks kotlinlang.org API changes to keep guidance current. However, AndroidDocs never accepts paid placements; therefore commissions never affect rankings. Based in San Francisco, CA, Daniel has shipped 25+ apps across fintech, productivity, and utility verticals — and writes about the tools that survived production load.

About Daniel Park

DP
Daniel Park
Android Engineer · San Francisco, CA
11 yrs Android
Ex-Google Play DevRel
25+ Apps Shipped
Kotlin · Compose

Background

Eleven years ago I shipped my first Android app — a barcode scanner running on a Nexus 4. Since then I’ve built and shipped 25+ apps across fintech, productivity, and utility verticals, ranging from a 50,000-MAU expense tracker to internal tools used by a Series-C startup’s field operations team. From 2021 to 2023 I worked as a Google Play developer relations contractor, helping indie teams ship Play Console releases, navigate Play Integrity API rollouts, and resolve policy escalations. I’m based in San Francisco, CA.

What AndroidDocs Covers

AndroidDocs is the site I wish existed when I was choosing tools as an indie developer. It covers honest reviews of:

  • Android Studio tooling — emulators, profilers, plugins, and the JetBrains stack
  • Kotlin and Jetpack Compose — what’s production-ready, what’s still evolving
  • Firebase and alternatives — Supabase, Appwrite, PocketBase, AWS Amplify
  • Mobile SaaS — RevenueCat, Adapty, Sentry, Bugsnag, Mixpanel, Amplitude
  • CI/CD pipelines — Bitrise, Codemagic, Appcircle, GitHub Actions for Android
  • Hosting for app landing pages — Kinsta, SiteGround, WP Engine, Cloudways
  • Security and testing — Espresso, Appium, MobSF, OWASP ZAP, Frida

My Testing Methodology

I never recommend a tool I haven’t shipped with. Every review on AndroidDocs follows the same protocol:

30+ days
minimum hands-on use in a real project before publishing.
Specific metrics
build time, crash-free rate, latency in ms, MB consumed, $/month.
Failure documented
every tool has a breaking point — I write what I hit.

Why I Review Tools

Tooling decisions compound. A bad CI choice burns 12 minutes per build × 8 builds per day × your whole team. The wrong analytics SDK adds 1.4 MB to your APK and double-counts events. Picking the wrong crash reporter means you ship with broken Pixel 6a coverage for two months before noticing. AndroidDocs exists because most “best of” lists rank by affiliate commission, not by what survives production. I’d rather lose the click than recommend something I’d regret in a sprint review.

Credentials

  • 11 years of production Android development
  • Former Google Play developer relations contractor (2021–2023)
  • 25+ shipped apps across fintech, productivity, and utility
  • Kotlin Multiplatform Mobile early adopter (since 1.4 alpha)
  • Jetpack Compose user since the 1.0 release in 2021

Contact

Email: daniel@androiddocs.com — I read every email and respond within 48 hours. Tool pitches that come without a public test build will be ignored. If you’re an Android developer with a tool you’d like reviewed, I evaluate ~3 reader-suggested tools per quarter.