App analytics

Measure mobile-app activity, retention, screens, versions, operating systems, and engagement events.

Video placeholder

Add a localized screen recording here: compare daily, weekly, and monthly active users, inspect app versions, and explain the pending engagement panel.

Open /analytics/app. The view reads mobile-app lifecycle, screen-view, and engagement events attributed to the active organization.

Activity KPIs

  • Daily active: unique app users active during the last day.
  • Weekly active: unique app users active during the last seven days.
  • Monthly active: unique app users active during the last thirty days.
  • App opens: Application Opened events in the selected range.
  • Returning: the share of users in the selected range who were also seen in the immediately preceding period of equal length.

Daily, weekly, and monthly active values use their fixed rolling windows. App opens and returning users use the selected range and its preceding comparison window.

Active-user trend

The active-user chart uses daily buckets for 7d, 30d, and 90d. For 12m, it aggregates users into monthly buckets. A day or month with no activity remains visible as zero.

Screens, operating systems, and versions

  • Top screens: up to twelve app screen names ordered by screen-view count.
  • Operating systems: unique users grouped by the reported $os value.
  • App versions: unique users grouped by the reported $app_version value.

Operating-system and version cards can include Unknown when the event does not contain the relevant property.

Engagement

The engagement panel counts these events:

  • Prayer-times views
  • News views
  • Event views
  • Qibla opens
  • Stream joins
  • Notifications opened

The panel may show a pending state until the corresponding mobile-app instrumentation is deployed and the community uses a version that emits those events. This is different from a normal no-data state: pending means the data source is not available yet, not necessarily that nobody used the feature.