The user should be able to view all columns of the report, to see Conversion rate, Revenue and Bounce rate per entry.
Maybe we add an event listener to the title of the statistic list. The title is the blue label containing for example the text "Unique Pageviews" or "Visits". As soon as the user clicks the label we'll open an Option Dialog where the user is able to select the appropriate? I think there is not really enough space in the headline for another icon.
Another question is: shall we save this selection in a session and use this selection preferably (if the selected statistic supports this)?
Would it be possible to display more columns for example when the phone is in landscape mode (and there is more space) ?
we currently do not support landscape mode. We have to refactor the app a bit first. I plan a bigger refactoring in may/june this year. Also, in landscape mode there would be just enough space for only two or three more columns. I would like to provide all available columns
Maybe I have an idea, see screenshots (opened.png, closed.png).
We could remove the "website" and "date" icon from the headline and add a "Change" or "edit" or ... button instead. The user has the possibility to press the "Change" button. This will open a toolbar below the headline (or always visible at the bottom of the screen). The button is now highlighted so that the user sees that he can close the toolbar if he presses the "change" button again. We would save the state of the toolbar in the app. If the user opens another view we will restore the saved state. So the app is clearly arranged for users who won't change settings like date and "power users" have the possibilty to change these settings easy.
Don't be frightened by the UI of the usability. I just added a simple button and a simple toolbar and haven't styled it cause I just want to visualize it. Instead of text like "website", "column", ... we could display icons. Cause of the translations we can not be sure that enough space is available for all three labels.
Maybe some users are here and could give feedback whether this UI pattern could work from the usability perspective and so on.
I think it is better to show that the calendar is clickable, and maybe also add an arrow next to the website name, to show that user can see other websites by clicking on it (make the area big enough so it is easy to access).
Then the columns settings could be part of the other "general settings" that you already have (maybe high in the list?). Easier than introducing the new button & icons maybe. Are there other similar settings you can think of in the future?
(In ) refs #2116 a first working version. allow to change the displayed metric for some reports. removed date and website icon, made date and website row clickable and added an arrow beside their name cause we need the space in the header for segmentation and so on
(In ) refs #2116 forgot to commit the choose metric command
(In ) refs #2116 added translation
(In ) refs #2116 fix select metric, website and date was not working on iPad. Website is now again selectable in live and visitor log screen. Disabled graph title in statistics screen cause the title is now visible below the graph
(In ) refs #2116 fix detection of default metric and removed no longer needed icons
Thomas great stuff! would you mind posting a screenshot of feature?
Attached you'll find some screens. I do display the current used metric below the graph now. The row is clickable. A click opens a dialog where the user is able to choose another metric. The chosen metric effects the displayed graph as well as the displayed statistics (except reports having no dimension, e.g. VisitsSummary.get does only effect the graph but not the displayed data).
Also made the website/date row clickable and removed the icons from the navigation bar. So we have enough space for example for the segmentation icon in nav bar and it is consistent with the metric row.
Looks nice!! :) well done Thomas!
(In ) fixes #2116 get available metrics from the columns object returned by the processedReport API request instead of metadata. the columns object contains all working metrics for the processedReport. metadata contains some metrics which do not work