wordpress-mobile / wordpress-mobile/WordPress-Android

Stats - Provide more context about different aggregate stats in similar looking cards

Open
#17,450 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

[Status] Needs Discussion [Type] Enhancement Stats
Dominant language
Kotlin
Stars
3.2k
Forks
1.4k
Avg merge
1d 11h
Merged PRs (30d)
69

Description

Expected behavior

The views and visitors aggregation stats less ambiguous, especially where the aggregations are performed differently for similar looking cards.

Actual behavior

Some cards show different numbers, but the underlying aggregations are deliberately different. This can result in confusion. E.g. see this issues: https://github.com/wordpress-mobile/WordPress-Android/issues/17211, https://github.com/wordpress-mobile/WordPress-Android/issues/17212

This issue is to consider enhancing the UI to make it more clear why these numbers would be different.

More discussion here (internal ref): pbArwn-5yF-p2#comment-6939

tl;dr weeks view (and overview) show "fixed week" stats, with the current week usually being "incomplete". The insights card shows the latest available complete week compared to the week prior to that, on a rolling basis (i.e. week ending yesterday, and week ending 7 days prior to yesterday) to eliminate bias in the performance metric. This difference is not immediately obvious from the similar design of the respective UIs, and can lead to the impression that the stats are inconsistent or inaccurate.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by reviewing the stats views and cards, then read linked issues 17211 and 17212 to compare fixed-week and rolling-week aggregations. Done should make the differing periods and aggregation behavior clear in the UI.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
analytics, design, mobile
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.