# Feature request: Android goal detail data point timestamps **URL:** \ **Category:** Bugabee\ **Created:** [December 31, 2019, 5:21pm UTC](https://forum.beeminder.com/t/feature-request-android-goal-detail-data-point-timestamps/6161 "2019-12-31T17:21:07Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![narthur](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/narthur/32/5113_2.png) [@narthur](https://forum.beeminder.com/u/narthur)\ **Post date:** [December 31, 2019, 5:21pm UTC](https://forum.beeminder.com/t/feature-request-android-goal-detail-data-point-timestamps/6161/1 "2019-12-31T17:21:07Z")
Not infrequently, I run into situations like this where there is no easy way to tell which is the most recent data point below the graph: ![Screenshot_20191231-121746](https://us1.discourse-cdn.com/flex019/uploads/beeminder/original/2X/1/13497d44968b586f9164a29f9ca67147d95a5fb5.png) I’m not sure what the right solution is, but could a data point on the right of each entry be added, or some other change be made to make it clear what order the data points were added, even when all shown points were submitted on the same day? ---
**Author:** ![adamwolf](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/adamwolf/32/484_2.png) [@adamwolf](https://forum.beeminder.com/u/adamwolf)\ **Post date:** [January 3, 2020, 3:08pm UTC](https://forum.beeminder.com/t/feature-request-android-goal-detail-data-point-timestamps/6161/2 "2020-01-03T15:08:48Z")
Let’s brainstorm ways we can show this data and fit it in. This screen is already a tight fit that tells you a lot of things. ---
**Author:** ![narthur](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/narthur/32/5113_2.png) [@narthur](https://forum.beeminder.com/u/narthur)\ **Post date:** [January 3, 2020, 3:34pm UTC](https://forum.beeminder.com/t/feature-request-android-goal-detail-data-point-timestamps/6161/3 "2020-01-03T15:34:28Z")
Yeah, it is tight… Firs thing that came to my mind: > 31 4 An incredibly long comment … 5:57 > 31 7 Another data point with a b … 18:19 Of course, what that doesn’t solve is the general ambiguity at first glance of what the different numbers mean. ---
**Author:** ![adamwolf](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/adamwolf/32/484_2.png) [@adamwolf](https://forum.beeminder.com/u/adamwolf)\ **Post date:** [January 3, 2020, 4:37pm UTC](https://forum.beeminder.com/t/feature-request-android-goal-detail-data-point-timestamps/6161/4 "2020-01-03T16:37:50Z")
To be completely honest, I don’t like a lot of things about this screen, like the leading numbers on this screen. The fact that the only indication that the 31 is part of the date is at the very _bottom_ of the screen really, really irks me. I would like to think about bringing the data entry above the data point list, and sort them so that when you submit a datapoint, the data point goes to the top of the list, and the rest shift down. I think this may even help with your “which is newest” issue. ---
**Author:** ![adamwolf](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/adamwolf/32/484_2.png) [@adamwolf](https://forum.beeminder.com/u/adamwolf)\ **Post date:** [January 8, 2020, 3:27am UTC](https://forum.beeminder.com/t/feature-request-android-goal-detail-data-point-timestamps/6161/5 "2020-01-08T03:27:46Z")
Hmm. @dreev what do you think of this screen and these thoughts? ---
**Author:** ![dreev](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/dreev/32/4311_2.png) [@dreev](https://forum.beeminder.com/u/dreev)\ **Post date:** [January 8, 2020, 7:59am UTC](https://forum.beeminder.com/t/feature-request-android-goal-detail-data-point-timestamps/6161/6 "2020-01-08T07:59:30Z")
My first thought is: Let’s ensure that the datapoints shown are always strictly in the order they were entered (even if that means they’re not ordered by actual datapoint date). I’m reluctant to add more visible information in the UI without thinking it all through from the ground up.