Built by an indie developer who needed it.
AppMetricsKit exists because measuring a subscription app should not require choosing between your users' privacy, a data engineering team, or flying blind.
The story
AppMetricsKit is built by Marwan Akhandaf, an independent developer shipping iOS and Android apps. It started as the tool he wanted for his own apps: analytics that could answer the questions a subscription app actually runs on — does onboarding reach the paywall, do trials convert, do renewals hold — without sending user behavior to an advertising company or standing up a warehouse to get event-level answers.
The existing options each solved half the problem. Privacy-first analytics tools stopped at usage signals. Revenue platforms knew about money but not behavior. The big suites knew everything but wanted your users' data in an ad ecosystem and your evenings in a query editor. AppMetricsKit is the intersection: privacy-first by architecture, subscription-aware by default, and sized for developers whose app is their livelihood.
It is an independent product, funded by its customers rather than by advertising or data resale — which is the only business model under which a privacy promise is structurally believable.
Open where it counts
Privacy is architecture, not a setting
No advertising identifiers, no cross-app tracking, anonymous IDs hashed on device, and server-side guardrails that flag PII before it is stored. The analytics is designed so there is less to disclose, less to defend in review, and less to leak.
Subscription revenue is part of analytics
Usage charts alone cannot tell you why trials convert or renewals slip. AppMetricsKit ships a canonical subscription event taxonomy, paywall funnels, and RevenueCat, Adapty, and Superwall webhook ingestion so store-side truth and client behavior land in one stream.
Indie-sized by intention
Volume-based pricing with a real free tier, SDKs that install in minutes, dashboards that answer questions without a data team, and honest comparison pages — because the product is built for developers whose app is their income.
Built in the open where it matters
The Swift and Kotlin SDKs are open source on GitHub, the roadmap and changelog are public, and compliance guides cite primary sources. Trust in an analytics vendor should be inspectable.