Idea checked

a privacy-first mobile analytics SDK

This idea is already crowded: several privacy-first analytics SDKs exist, with Aptabase and Respectlytics the clearest mobile-native examples.

Confidence: medium — There is real evidence of existing mobile SDKs and adjacent privacy-first analytics products, plus some user demand signals on HN. But the signals are thin on pricing, revenue, or actual adoption, so market size is mostly inference.

55 signals collected
13.4s to run
2026-08-01

hackernews 32
github 14
tavily 9

Who is already building this From data

Aptabase already ships privacy-first SDKs for Swift, React Native, Flutter, Unity, MAUI, Kotlin, Electron, JavaScript, Python, and Go, and positions itself as an open-source alternative to Firebase/Google Analytics for mobile, desktop, and web apps [2][5][8][12][14][17][20][24][27][29][35].
Respectlytics is another direct competitor for mobile, with Swift SDK messaging that emphasizes 'No IDFA, no IDFV, no device fingerprints' and a 2-line integration pitch [9].
- tavily Swift Analytics SDK - Privacy-First Analytics for iOS & macOS | Respectlytics
Ours Privacy has an Android SDK that explicitly markets itself as privacy-first analytics for Android apps [1].
- tavily Android SDK (client)
There are also adjacent privacy-first analytics products in the market, including Countly, Plausible, Panelbear, PrivateAnalytix, HitKeep, and others seen in HN discussions and review pages [4][10][11][18][28][34][48].

What people actually say From data

The strongest repeated complaint is that mainstream mobile analytics SDKs quietly collect device IDs, ad IDs, and IP addresses, which forces founders to work backwards on compliance [0][18].
- hackernews Show HN: Respectlytics – Open-source, privacy-first mobile analytics (MIT+AGPL) 2026-02-15
- tavily Third-Party SDK Compliance: How to Audit and Control Data Sharing in Mobile Apps | Secure Privacy Blog
People keep asking for privacy-first alternatives in HN posts: 'Free, Privacy-First Analytics for a Better Web,' 'opensource, privacy-first Google Analytics,' and 'privacy-first analytics for iOS apps' all got posted [7][11][19][30].
A recent HN post for YAAT says EU companies want to avoid sending data to US servers and want direct SQL access to raw events instead of fixed dashboards [23].
- hackernews Show HN: YAAT – Privacy-first analytics for EU companies (need for beta users) 2025-11-20
Another HN discussion says people want simple, actionable dashboards because big analytics tools feel like 'too many numbers' and 'most of the data isn't even actionable' [52][53].
- hackernews I built my own privacy-first analytics tool after running dozens of sideprojects 2025-12-19
- hackernews [dead] 2025-11-15

Where the opening is Model estimate

The model's read of the signals below — not something anyone measured.

There is still room if you focus narrowly on mobile-first workflows, because many of the visible alternatives are either web-first or broad analytics platforms rather than SDK-first mobile products [3][4][28][34][48].
A clear gap is consent and compliance automation inside the SDK itself: the HN complaint is about retrofitting compliance after data collection, so a product that makes the data model obvious and auditable could differentiate [0][13][18].
Another gap is developer trust: open source plus a narrow event schema and explicit field-by-field docs may matter more than a large feature set, because users keep saying the existing tools are too heavy or opaque [0][15][52].

How big the market might be Model estimate

The model's read of the signals below — not something anyone measured.

The market is likely real but not huge: the signals show repeated interest over several years, yet most HN posts have modest engagement, with only Cloudflare's privacy-first web analytics standing out at 266 points and 115 comments [3][7][11][19][30].
Aptabase has multiple SDK repos with relatively small public star counts, such as 44 for Swift, 41 for React Native, 27 for Flutter, 21 for JS, 21 for Unity, 15 for MAUI, and 15 for Kotlin [2][5][8][12][14][17][20][24].
That points to a niche developer market with some demand, but nothing here proves large-scale adoption or strong willingness to pay [2][5][8][12][14][17][20][24].

What could go wrong Model estimate

The model's read of the signals below — not something anyone measured.

Direct competition is already visible from open-source and commercial privacy-first tools, so a generic 'privacy-first mobile analytics SDK' pitch is easy to copy and hard to defend [1][2][4][6][9][42][43][44].
Feature creep is a real risk because competitors already bundle sessions, revenue, crash reporting, engagement, offline tracking, and even session replay [4][42][43][44].
Compliance claims are easy to overstate and easy to challenge; HN explicitly calls out tools that are 'not that compliant' once inspected [0].
- hackernews Show HN: Respectlytics – Open-source, privacy-first mobile analytics (MIT+AGPL) 2026-02-15
Open-source licensing may scare some buyers or slow adoption if it is MIT+AGPL like Respectlytics [0].
- hackernews Show HN: Respectlytics – Open-source, privacy-first mobile analytics (MIT+AGPL) 2026-02-15

What to do this week Model estimate

The model's read of the signals below — not something anyone measured.

Pick one platform first, probably iOS or Android, and ship a brutally small SDK that tracks only a few core events with an explicit allowlist of fields; Respectlytics already shows that '2 lines of code' and no device fingerprints is a clear message [9].
- tavily Swift Analytics SDK - Privacy-First Analytics for iOS & macOS | Respectlytics
Differentiate on auditability: expose exactly what is sent, provide a visible privacy label, and make the SDK output easy to inspect, since people are worried about hidden collection [0][15][18].
Build around a mobile-native use case that web tools do not serve well, such as offline-first event tracking or revenue analytics for Flutter/React Native/Android/iOS [42][43].
- github Adopture/adopture-flutter 2026-04-08
- github Adopture/adopture-react-native 2026-04-08
Validate demand with developers who already complain about GA-style tools and privacy compliance, because the public signals suggest the market exists but does not yet show strong proof of scale [0][23][52][53].

Who is already building this From data

What people actually say From data

Where the opening is Model estimate

How big the market might be Model estimate

What could go wrong Model estimate

What to do this week Model estimate

Nearby ideas

Check another idea