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
As there are sometimes very long lists in statistic views (sites, keywords,...) we need to implement a kind of paging.
First time loading a statistic view only the top 25 (or 30, 50, maybe configurable) entries should be loaded from the api to be displayed. If there are more entries available there should be a "show all" button at the end of the list to reload the view and dislay all.
The text was updated successfully, but these errors were encountered:
Great! One small question... Imagine the following:
User clicks "Country". Now the statistic list appears having - for example - 50 entries.
Then user clicks the "show all" button within the statistics view.
Now we'll display the complete list, not just those 50 entries. On the very bottom we add a button called "show less"
Now the user goes back and chooses another statistic, let's say "Search engines".
My question is:
Shall we now again show just 50 results and the user has the possibility to again click the "show all" button?
Or shall we save this in the session (while the app is opened) and display all existing values directly and the user has the possibility to click a "show less" button on the bottom of the statistic list?
I think on a mobile most users only watch the overview of traffic and not often go deeper. I think leaving as it is, showing 50 and click to View more is the best way to do it. I don't think the setting is so useful.
It would be lot more useful to be able to view all Columns of the report, to see Conversion rate, Revenue and Bounce rate per entry.
(In [3983]) fixes #2107 added paging to Android and iOS. By default the first 50 items will be displayed, then the user has the possibility to press the show all button which will display all items. This causes a faster rendering and less data network traffic
As there are sometimes very long lists in statistic views (sites, keywords,...) we need to implement a kind of paging.
First time loading a statistic view only the top 25 (or 30, 50, maybe configurable) entries should be loaded from the api to be displayed. If there are more entries available there should be a "show all" button at the end of the list to reload the view and dislay all.
The text was updated successfully, but these errors were encountered: