Thanks for the feedback Frenik.
Regarding medicines and such: I break it down into medications or supplements. So, you can say to Google Home, "I took two tylenol at 3pm today" and it'll get logged as medication. Or "I took 200 milligrams of Vitamin C at 10pm yesterday" and it'll get logged as a supplement.
We also log symptoms and health incidents. Here's a partial list of the list of symptoms (listed on the left) and the their synonyms that Google Home will recognize and equate them to:
and here's a list of the health incidents:
(When we log an incident or symptom we also use a severity scale to note how serious it is.)
Here's a standard comparison page where I've chosen to compare medications and symptoms (you can do this with any 2 types of Events).
The first cluster is a lingering cough and cold at the end of 2018. The second tighter cluster is a nasty sinus infection - I never had one of those before and it was crazy - I was popping 6 - 8 tylenol a day for a while there. Just getting over it now.
I'm not sure which definition of "social things" you mean. Like, logging how much time you spend on social media or out with friends? There is a "Leisure" category with Events for Family Time, watching (broken down into tv episodes/movies/online videos), reading, listening, web surfing and a generic "socializing" Event as well. If you tell me more about what you envision, I'd definitely consider adding it.
Yes, it's all manual logging now, though I'm trying to make it as easy and quick as possible by using Google Home to log. We have one in the kitchen and one upstairs so it's pretty easy to log most things without having to stop what we're doing or reach for a phone.
I definitely agree that automating Event logging as much as possible is key. I wear a Fitbit and I definitely want to automate the collection of a bunch of its data - the sleep summary data is especially interesting to me. But it's a lot of work to integrate with their API on a scalable basis, so I probably won't tackle that until I see there's interest in it.
Up til now, my philosophy has been to focus on the things that aren't easily automated and to make it as easy as possible for people to log those things so they don't get lost. But hearing you confirm the importance of automation makes me think I should move the fitbit API integration higher up on my "road map".
Thanks again for the feedback! I really appreciate it.