Completed
Custom tracking
Being able to manually track yes/no variables that you can create yourself. An example would be tracking “coffee” or “meditation” by adding the relevant tag for this event to your list of tags for the day.
We have long-term plans to add the ability to manually track things like a habit tracker app does that our service integrations don’t support, like number of coffees, or migraines, or whether you’ve meditated today. Unfortunately it requires a bit of a large architectural rejigger (technical term) on our end so while we’re conscious of it being a pretty nice feature to have, it’s going to take a while.
Whatever external habit tracking services we end up supporting, we need to add a large list of attributes to match, ie. “things you can track”, as well as the architectural changes to support this. It’s unfortunately not as simple as “outsource this to X service” or we would just be asking you to vote those up and this suggestion wouldn’t exist :) please vote for this suggestion if you’d like us to be able to support custom tracking at all, and vote for other specific service suggestions if you’d like those to be integrated once this is done.
I think custom variables are a necessity at some point. There will always be some variable beyond what you’ve thought of that will be applicable to some user, and it could be something very valuable for them to understand. An example would be that my dentist made me a nightguard, which I almost always use when I sleep, but I suspect that I sleep better without it. I need the ability to define {var=wearing_nightguard;type=boolean;desc=”blah blah”} etc. and then I can just set it, forget it, and look at the data in a couple of months to validate my hypothesis. This kind of thing shouldn’t be surprising to anybody reading this, we’re all here buying into the concept…
oh, and bonus points for building the ability to log these variables directly in the exist app… :)
@stephenanspach I appreciate that, but Exist just doesn’t work that way. We can’t create all the data around attributes, for example putting them in a sentence to make a correlation, if we aren’t the ones defining the attribute, or variable as you say. Plus, it’s just very hard to go there architecturally at this point, as Exist was never designed for that. I do understand that it’d let people track anything they want, which would be great. But at least for the foreseeable future, attributes will have to be managed by us.
We are planning on adding a big list of new ones when we support custom tracking, though.
@derekgurney hey Derek, I’m sorry if you got the impression anywhere that we currently support manual tracking. We list all of our supported services on the home page but deliberately do not mention manual tracking anywhere, as we don’t do it yet. If you don’t find Exist useful without manual tracking, you’re welcome to give it another try later when this development is completed.
Just as an update to everyone following this, we’ve chosen to implement something similar but not exactly the same we’re calling “custom tracking”. We talked about it a little on our last podcast if you’d like to hear more about how we arrived at this decision. Custom tracking is currently in beta testing, and if you’re an Android user you can help test it by joining the group here: https://groups.google.com/forum/#!forum/exist-for-android
The next step will be to get this done in the iOS app also, then it’ll be ready for everyone to use!
It’ll be available via the API as we use the same API for mobile apps as we provide for everyone else :) I’ll document how to do it in the docs once it’s live.
I forgot to add the link, but for everyone else the podcast is here: http://blog.hellocode.co/post/podcast-21-apple-health-custom-tracking/
Just to keep everyone updated, the main hold-up on this right now is the iOS app, which I’m working hard on! I’ve only got a couple of big, main sections of this feature to add before I start focusing on design and fixing bugs. I’m hoping to get it to beta testers by the end of June, but I’ll keep you all updated here along the way.
Oiseau Bleu, I’ve just added you to the iOS beta, so you’ll get the custom tracking update as soon as it’s released in TestFlight.
I’m currently working on final polish and bug fixes for this feature before it goes out to beta testers—looking on track to get it into beta testing before June is over!
Hooray, this is live and available for everyone! The announcement blog post is here: https://exist.io/blog/custom-tracking/
Thanks to all our beta testers for their help.
Great progress! What I’d also like is the ability to track numbers against the tag. So if I did 50 pushups today, I want that recorded in the data, not just the fact that I did pushups. Then I can start tracking against a goal. I use an app called “Strides” for this at the moment, which does it really nicely - would be great to get this all in one place in Exist.
I’d support Stuart on this wish. For instance now I have a tag called coffee which is virtually always tagged which means there is no variation even if I some days drink 7 cups of coffee and others only 3. Its hard to come up with a good cut-off point for what I should be tracking - coffee3+ or coffee5+. So custom tracking of interval data would be a great improvement - e.g. also if you want to track your blood pressure.
I’ve made a suggestion for manual tracking of numeric values which may be RTYI: https://changemap.co/hellocode/exist/task/1828-manual-tracking-or-adding-numbers-to-custom-tags/
First, I love the custom tagging feature and super excited that you added it.
some things i would like to see in the future as possible are included below.
Custom Tagging tweaks,
I have found that there is a limit of 250 characters for creating tags in the mood tool. This limits a number of things that I would like to track. It would be nice to be able to track more than this limit.
It would be great to be able to select and deselect custom tags from the goals window.
It would be nice to be able to rename a tag but keep all the associated information. == I started tagging things that were common with the additional letter to indicate a “category” example. Med Trileptal With Med being the category and Trileptal being the medication. That way these things display next to each other and can be easily selected. Another example I used S = symptom so that S Cough, s runny nose is next to each other. however because I didn’t start with this process some tags aren’t associated.