#inclusiveandroidapps
Live, measured metrics for the hashtag #inclusiveandroidapps from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #inclusiveandroidapps
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · mastodon.social (Mastodon public tags API) · fetched 2026-10-13 11:22 UTC1 uses by 1 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.social (Mastodon public search API) · fetched 2026-10-13 11:22 UTCNo related tags with measured usage found for #inclusiveandroidapps.
Live pulse
measured · mastodon.social (Mastodon tag timeline) · fetched 2026-10-13 11:22 UTCEverything below is measured over the latest 16 public posts (spanning ~5980 hours).
Posting hours (UTC) — busiest: 10:00
Languages: English (16)
Avg boosts / post: 0.7
Top of the latest posts
In case you missed it, Issue #10 of Inclusive Android Apps is out! 🚀 This one's about gesture-only interactions like pinch-to-zoom on maps and graphs, and how to fix them. Code included. Read it: https://buttondown.com/inclusive-android-ap
Issue #10 of Inclusive Android Apps drops tomorrow 📬 This one's about gesture-only interactions like pinch-to-zoom on maps and graphs: what happens when touch gestures are the only way to interact with something, and how to fix it. Code in
Issue #8 of Inclusive Android Apps drops Tuesday 📬 This one's about animations: how they can cause real physical symptoms for many users, and how to make sure your app respects the Remove animations setting. Code included. Subscribe to get
#inclusiveandroidapps across platforms
every network with a public tag surfaceFollow #inclusiveandroidapps straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/inclusiveandroidapps