First, search the help docs and this forum. Maybe your question has been answered! The debugging steps can help, too. Still stuck? Delete this line and proceed.
Hi everyone,
I’m currently evaluating different architectures to set up a habit tracker in my vault. My primary goals are long-term maintainability, performance, and keeping my data as native to Markdown as possible.
The setup I’m looking into consists of:
-
Data layer: Storing habit status using boolean/checkbox properties in the YAML frontmatter of my daily notes (
habit_name: true/false). -
Dashboard: A single Canvas file containing individual cards per habit.
-
Visualization / Logic: Using
dataviewjscode blocks inside each card to read the daily notes, calculate streaks/completion rates, and render visual monthly calendars.
On paper, this seems like a solid approach since it avoids single-purpose community plugins and keeps everything contextualized within daily notes. However, before committing to it, I’d love to get feedback from anyone running this or similar setups:
-
Performance & Scalability:
As the vault grows over time (hundreds of daily notes), does executing multipledataviewjsqueries across Canvas cards lead to noticeable rendering lag or high memory usage, particularly on mobile? -
Maintenance vs. Dedicated Plugins:
Compared to dedicated plugins (like Habit Tracker 21, Heatmap Tracker, etc.) or native Obsidian database views, is maintaining customdataviewjsblocks worth the extra flexibility in your experience? -
Bottlenecks:
Are there any unforeseen drawbacks or edge cases with this architecture that I should be aware of for long-term vault longevity?
I’d really appreciate any insights, alternative recommendations, or lessons learned from your own workflows!