262 karma · joined December 19, 2008
One of the best-implemented hiking sites in my opinion is hikr.org, though the information I need tends to be on local sites like wta.org or nwhikers.net.
In addition to submitting trip reports to wta.org, I keep a record of my hikes at https://zenobase.com/#/buckets/u07qih0a27/. It's a more general-purpose service, but I can filter by any combination of region, hiking distance, duration, season etc.
BodyMedia's FIT detects when you lie down and get up (so no need to push any buttons), and you don't need to transfer the device into an awkward wrist strap (since you're wearing it on your upper arm).
One reason for this is that the human body is too complex (and the data too incomplete) for simplistic advice like "walk x steps per day to reach weight y".
You're also unlikely to discover a novel correlation that can be used to lose weight (and write a book and get rich)... But what you can do is use your data to determine which known solutions are working for you, and which are not (e.g. do I really sleep better when going to bed before midnight, all else being equal?).
I'm eager to see how exist.io handles all of this! (I run another service in this space, zenobase.com)
It's the same issue as with Google AdSense, though there you have options to exclude certain ads.
Completely agree that "graphs without the ability to manipulate data are worse than nothing"--it's hard to gain much insight without being able to drill down and filter the data. Simple questions such as "how strong is the correlation between room temperature and sleep" end up having to be refined e.g. with "ignore weekends" and "correct for different amounts of physical activity".
Being able to "get as much data as possible" sounds good, but garbage in, garbage out applies...
Finally, I don't think it's possible to create a single mobile app that suits everyone, which is why Zenobase has a flexible, generic data model and an API.
Otherwise there are better options, given the hard to configure and slow build process, bloated artifacts, infrequent releases, missing features (in the Java version) and incomplete/outdated documentation.