You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A user has shared feedback about the way stats are displayed in the Jetpack mobile app. Currently, when viewing stats for an individual post, the bar graph is shown prominently at the top, while total views are not immediately visible.
User Suggestion:
Prioritize total views as the first stat displayed for a post.
Make the bar graph less prominent or secondary to key metrics.
Improve the flow so that users can quickly check stats without unnecessary clicks.
User Context:
The user frequently checks post stats on mobile while away from their desktop. They find the current layout unintuitive because total views are the most important metric for them at a glance. They also mentioned that the "Discard Changes" prompt appears unexpectedly when exiting post view, which could cause accidental edits.
This was reported via Zendesk, check the ticket for more context: 9443342-zd-a8c
The text was updated successfully, but these errors were encountered:
kean
changed the title
User Feedback: Improve Jetpack Stats Display in Mobile App – Show Total Views First
Prioritize Total Views in Post Stats
Mar 4, 2025
Description:
A user has shared feedback about the way stats are displayed in the Jetpack mobile app. Currently, when viewing stats for an individual post, the bar graph is shown prominently at the top, while total views are not immediately visible.
User Suggestion:
User Context:
The user frequently checks post stats on mobile while away from their desktop. They find the current layout unintuitive because total views are the most important metric for them at a glance. They also mentioned that the "Discard Changes" prompt appears unexpectedly when exiting post view, which could cause accidental edits.
This was reported via Zendesk, check the ticket for more context: 9443342-zd-a8c
The text was updated successfully, but these errors were encountered: