Customizable stats screen

[GoogleCodeExporter]

The stats screen should be customizable by the user.

We'd favour a solution where the user can simply drag fields around as he
wishes. Maybe in a similar way that icons are manages on the Android home
app. Maybe we can also provides a set of typical template layouts for
different sports activities. Most important here that we find a simple UI
that leverages the touch screen capabilities to drag stuff around etc.
rather than introducing more menu items etc.

Original issue reported on code.google.com by rdama...@google.com on 18 May 2010 at 9:40

[GoogleCodeExporter]

Even if you just had a list of all the fields available and could check the 
ones you'd like displayed.  That way at least with just 4 or 6 important ones 
they would be big enough to see on a quick glance down while riding a bike or 
so.

Original comment by kurchi...@gmail.com on 14 Jul 2010 at 1:05

[GoogleCodeExporter]

The customizable screen of garmin's forerunner 305 is good enough for me.

User can configure the 3-4 items on the the stats screen. For the android's 
bigger screen, we can have more items and chioces:P E.g. 4-8 items.
See page 43 for the detail: http://www8.garmin.com/manuals/984_OwnersManual.pdf

And Garmin forerunner 305 has 2 main screen for all the profiles and 1 screen 
for each sports. And these screen can be configured to scroll automatically 
during workouts. 

I do like this design. Simple and easy, just enough for my usage.

As you mentioned, another approach is the Home screen's widgets style:
The stats screen may support 1-3 sizes of icon, and these icons can be dragged 
like the icon/widgets on Home screen. Each icon can be set to display some kind 
of data.

This way is more fasion and we can add the feature requested from  "Issue 1:     
MyTracks widget".

Original comment by binbi...@gmail.com on 16 Jul 2010 at 12:40

[GoogleCodeExporter]

Issue 106 has been merged into this issue.

Original comment by rdama...@google.com on 25 Aug 2010 at 5:18

[GoogleCodeExporter]

Like the idea of customizing the screen since I am not interested in all 
information at all times. When I am running in the city, altitude and rise is 
not interesting for me. But when I am mountain biking, rise becomes interesting 
(although this is not exact).

Other stats I would usually deactivate:
- latitude/longitude
- min/max inclination
- altitude

I guess for most of us this pretty much depends on the individual user and even 
on the use case.

I'd also like to see new measures added as optional stats:
- current heart rate
- average heart rate
- max heart rate

It would be great if these were not shown by default. As soon as a user 
connects a HRM for the first time, they could be enabled. After that, the user 
can enable/disable the individual stats display.

Original comment by marian.s...@gmail.com on 19 Nov 2010 at 4:24

[GoogleCodeExporter]

The flow we have been talking about internally is something like this:

Move to stats screen with nav arrows.
Menu->Edit Layout
First there is a menu to either select one a few few pre-created layouts like:
Geo-cacher
Runner
Cycling
Pilot
or User customizable => Choose the number of fields to display.
If the user chooses customizable they go into a view where each field on the 
layout is a button.  Pressing on that button brings up a menu to choose what 
data to display in that field.

Original comment by sandordo...@google.com on 19 Nov 2010 at 6:41

[GoogleCodeExporter]

Having role-specific templates sounds good. So can geocachers, runners, 
cyclists, pilots, (hikers, ...) agree on what they need? How do we come up with 
good defaults? I guess we should ask at least a couple of each what they'd 
expect to be there and compile that. For that, we would need a complete list of 
all fields. Here is what I can get out of res/strings.xml

- Average Moving Speed
- Average Moving Pace
- Average Speed
- Average Pace
- Elevation Chart
- Elevation Gain
- Elevation
- Latitude
- Longitude
- Min Elevation
- Min Grade
- Min Pace
- Max Elevation
- Max Grade
- Max Speed

We'd also have to ask about fields that aren't there yet, like heart-rate 
related values, power and cadence related etc.

We probably should do this outside of code.google.com as a structured survey. 
That would simplify getting results out of it. A spreadsheet with a form maybe.

What do you think? Is it worth the effort?

Original comment by marian.s...@gmail.com on 20 Nov 2010 at 9:23

[GoogleCodeExporter]

We have more data than that which could be displayed, but is not in the current 
display because it'd be useless for most people. Some examples:
* Bearing
* Direction (not the same as bearing, the phone could be turned one way but 
moving in another)
* Precision
* Non-moving time
* Heart rate
* Power
* Candence
* etc.

Original comment by rdama...@google.com on 20 Nov 2010 at 9:39

[GoogleCodeExporter]

I expect more and more people will start useing HRMs, so Heart Rate ought 
definitely be displayed.

As a Garmin user, I like the idea of being able to choose which data fields are 
displayed, and at which screen position.

Original comment by stephen....@googlemail.com on 3 Mar 2011 at 2:05

[GoogleCodeExporter]

As a windsurfer I would really like to have the following stats on the stats 
screen:
Total time
distance
max speed
10 seconds avarage max speed   (new feature)
30 seconds avarage max speed   (new feature)
50 meter avarage max speed     (new feature)
100 meter avarage max speed    (new feature)

Actual data as speed/course/etc are not interesting because I've never been 
able to look at the screen while going high speed on the water.

Original comment by TheXtrem...@gmail.com on 9 Apr 2011 at 9:44

[GoogleCodeExporter]

On my hiking adventures, I record trails and post pictures online for others to 
see. Besides the total distance, a big factor on rating trail difficulty is the 
elevation gain. Currently there is only min/max. If I went up and down a bunch 
of small hills it would appear I only hiked one of these hills.

The elevation graph profile is especially helpful for someone to determine if a 
trail is right for them. However, the elevation graph must be visually 
interpreted. When comparing one hike to another the scale of each graph must be 
taken into account.

I would like to post the total elevation gain/loss to more accurately compare 
one trail to another. This would be an elevation sum total of all uphill and a 
total of all downhill path segments.  This way a trail that had one steady 
climb of X feet could be compared to another that had multiple climbs that 
totaled X feet.

Original comment by bradsmit...@gmail.com on 8 May 2011 at 11:33

[GoogleCodeExporter]

this may not be the appropriate issue for this suggestion, but it would be nice 
to see a way to separate (or filter) the aggregate statistics by different 
activity types (ie, see stats just for cycling) or into date blocks (ie, see 
total miles travelled in april)

Original comment by george.h...@gmail.com on 25 May 2011 at 7:41

[GoogleCodeExporter]

(just removing OpSys-Android label, all issues are in Android anyway)

Original comment by rdama...@google.com on 26 Jul 2011 at 1:00

• Removed labels: OpSys-Android

[GoogleCodeExporter]

Issue 533 has been merged into this issue.

Original comment by sandordo...@google.com on 27 Jul 2011 at 4:26

[GoogleCodeExporter]

Any chance this will be upgraded from priority low?  I love the heart rate 
monitor functionality that has been added but without any sort of display, its 
not immediately useful.  I tried running my tracks in the background and 
another generic HRM app in the foreground but found that they couldn't both 
grab data from the same device at the same time.  Please correct me if I am 
wrong about this.

Original comment by Btpaul...@gmail.com on 18 Jan 2012 at 3:09

[GoogleCodeExporter]

On the Garmin Edge 705 and 800 bicycle computers, there are multiple screens 
with user-configurable data fields. On the touch-screen operated Edge 800, the 
screens are switchable by a swipe action. Something like that would be very 
nice.

Ideally, the selection of data screens would be tied to a profile. If I have an 
ANT+Sport sensor on a touring bike and another on a MTB or racing bike, I would 
get a different selection of data screens.

Original comment by msmak...@gmail.com on 25 Mar 2012 at 8:12

[GoogleCodeExporter]

Issue 834 has been merged into this issue.

Original comment by jshih@google.com on 10 Sep 2012 at 10:45

[GoogleCodeExporter]

Issue 249 has been merged into this issue.

Original comment by jshih@google.com on 10 Sep 2012 at 11:27

[GoogleCodeExporter]

Original comment by jshih@google.com on 13 Oct 2014 at 9:47

• Changed state: WontFix