Comments (4)
I wonder if I should combine this with issue #27 and re-think the data model. Maybe rather than days being a fuzzy thing, a collection of items that share the same date, maybe Day
should be a part of the domain model, with all entries belonging to a Day
.
And maybe new entries should be added to a Day
from the day card (instead of a floating action button)? Although I don't know if this might make data-entry more cumbersome. Maybe there should still be a shortcut FAB for adding to the current day (or JIT creating one if necessary).
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Tuesday, January 2, 2018 ┃
┣━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┫
┃ Slept 8hrs, awoke twice. ┃
┠───────────────────────────────────┨
┃ 8:00am Ate cereal ┃
┠───────────────────────────────────┨
┃ 8:05am Drank soy latte ┃
┠───────────────────────────────────┨
┃ 10:00am Energy level high ┃
┠───────────────────────────────────┨
┃ [+ food] [+ exercise] [+ symptom] ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
from personal-logger.
Interesting questions. I think the question of whether Day is an attribute or a first-class domain member. I ask myself, “what is the goal of the app - are you trying to identify the Day in which bad allergy events occur? Or are you more interested in identifying the influencing events (sleep, food, activity) that correlate most strongly with the allergic effect? In my mind, the potential Causes should be first class data objects, and in that view, Day is just a piece of metadata to help properly link possible Cause to possible Effect.
The reporting layout, while a significant piece of engineering in any data app, I try to avoid constraining the data model to one particular reporting design.
The more I think about it, the original “all items interleaved” approach might make it hard for a non-expert-User (like your doctor) to quickly associate data that *should be associated.
Ideally in this kind of application, it would be great to present two timelines: one for potential causes and the other for potential effect - and then allow the user to offset one timeline from the other so that they can form their own theories about whether and how often/strongly a potential cause precedes a potential effect by some rough window of time.
I don’t expect that it should be too important to be exact (i.e. each human’s reaction times - and precision on capturing the time of each events - can vary - I might react to gluten within a couple of hours, someone else might notice a different symptom a day or two later).
I think it would be more important to be able to see the pattern - e.g. do most episodes follow a certain food by 8-12 hours, or follow a poor sleep by 1-2 days? No idea what the intervals should be - I would like to be able to drag the causes timeline back smoothly until I see or don’t see a pattern (and the only indication of hours is hour or two-hour increments out of the central part I’m looking at - minimise distraction when I’m doing heavy cardio genitive work of looking for patterns).
Wow, that was a bit much - and likely would benefit from a mock-up or two to illlustrate what I see in my head - if you’re even interested in exploring this alternative, that is.
from personal-logger.
Please feel free to share any mockups you'd like to, sure thing.
from personal-logger.
Maybe I could use a layout similar to these "bullet journal" apps in the iOS store? I particularly like the UI style of Bullet Diary by Jin W Roh
I also like the daily average ranking shown on the monthly view of Perspective - Daily Journal by Blinky
from personal-logger.
Related Issues (20)
- Add iOS PWA meta tags HOT 1
- Sleep duration should support decimal values HOT 1
- Numeric inputs should allow the 0 to be deleted HOT 1
- Direct navigation to pages other than the root URL breaks without service workers HOT 11
- Saving a resource doesn't return to list page (on production) HOT 1
- Add confirmation modal to delete process HOT 1
- Disable Safari/iOS page bounce behavior HOT 4
- Fix elastic scroll bounce for iOS
- Add spicy Boolean attribute to food HOT 1
- Disable auto capitalize behavior for inputs HOT 8
- Unable to authenticate with GitHub provider HOT 9
- First-time Twitter authorization throws multiple console errors HOT 1
- Is linting always desired for JSON and CSS files, or only at precommit? HOT 1
- Report view HOT 5
- Add "meal size" attribute to food entries HOT 5
- Replace Firebase/Firstore with something better HOT 15
- Add `calories` in the food form HOT 1
- Protect app from unauthorized users HOT 1
- Can't login via Google/Github/Twitter in Chrome/Safari HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from personal-logger.