SmolAnalytics.kt (the agent adds this) · open source (MIT) · ask in plain English

Add analytics to your Android app Android.

Android analytics usually means an SDK plus a lifecycle observer plus a track call on every screen. smolanalytics instead has your coding agent open a PR that wires it in for you. The client is one small dependency-free file (HttpURLConnection, no OkHttp, no androidx) with an offline-safe persisted queue, sessions and device context. Then you ask your numbers in plain English from your editor.

SmolAnalytics.kt (the agent adds this)
import com.smolanalytics.SmolAnalytics

// once, in Application.onCreate()
SmolAnalytics.initialize(this, "WRITE_KEY", "https://YOUR-INSTANCE")

SmolAnalytics.track("signup", mapOf("plan" to "pro"))
SmolAnalytics.screen("Checkout")
SmolAnalytics.identify("user-123") // on login

Connect your repo and the agent wires this up for you. It's open source (github.com/Arjun0606/smolanalytics), zero dependencies, and the write key is public (send-only) so it's safe to ship. Add the INTERNET permission.

how do I add analytics to android?

Android analytics usually means an SDK plus a lifecycle observer plus a track call on every screen. smolanalytics instead has your coding agent open a PR that wires it in for you. The client is one small dependency-free file (HttpURLConnection, no OkHttp, no androidx) with an offline-safe persisted queue, sessions and device context. Then you ask your numbers in plain English from your editor.

On mobile there is no autocapture, so you track the moments that matter explicitly: app_open, sign up, purchase, the screens people reach. The client tracks app_open (via activity lifecycle) and sessions automatically and attaches device, OS version and app version to every event, so device and version breakdowns work out of the box. You add track() on the two or three key moments, or let the agent find them.

What no data-silo tool can do: because your coding agent installs and instruments it, and it sits in your repo next to your analytics, you can ask "which release moved day-7 retention?" from your editor and get a number that provably equals the dashboard (a CI test enforces it). Self-host the open-source binary free or hosted from $49/mo, cookieless with no consent banner.

Honest pricing: 14-day full trial, no credit card. Then Pro $49/mo, never metered on seats or sites. Overage is $8/million with an emailed receipt, the dashboard never locks, and self-hosting the single Go binary is free forever (MIT).

Add analytics to Android tonight.

One snippet, or one endpoint. Tomorrow morning the verdict tells you which part of the funnel to fix.

questions

How do I add analytics to Android?
Android analytics usually means an SDK plus a lifecycle observer plus a track call on every screen. smolanalytics instead has your coding agent open a PR that wires it in for you. The client is one small dependency-free file (HttpURLConnection, no OkHttp, no androidx) with an offline-safe persisted queue, sessions and device context. Then you ask your numbers in plain English from your editor.
Do I need a cookie banner?
Not in cookieless mode. smolanalytics can run without storing anything on the device, so there is no consent banner to add. You still get visitors, referrers, funnels, retention, and paths, and AI-assistant referrals (chatgpt.com, claude.ai, perplexity.ai) show up as their own channel.
Is it enough for a real product, or just page counts?
It does funnels, retention, paths, cohorts, and a daily verdict on what to fix, from the same events, and you ask it in plain English. It also ships feature flags, A/B experiments, click heatmaps, in-product surveys, and a session inspector that replays a user's journey from their events; the one thing it skips is pixel-perfect DOM session recording. If you want a straight answer on what to fix, plus the full toolkit, that you own and can self-host free, it fits.

keep reading