[FR] GitHub-style Contribution Heatmap Widget for Dashboards (Single & Multi-Database)

Open
#9,124 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
dart, flutter
Domain
design, frontend

Research direction

Start by reading the dashboard widget implementation and how widgets query and aggregate database records; the issue does not name specific files or tests. Define how single and multiple data sources, date fields, activity triggers, color thresholds, and year selection should work, then confirm the expected behavior with maintainers before implementation. Done means the dashboard can display the requested daily contribution heatmap with these settings.

Written by the indexing model from the issue text.

Description

Description

I'd like to suggest a new feature for the Dashboards released in v0.15.0. The idea is to add a widget that shows data as colored squares, exactly like GitHub's contribution graph.

To make it actually useful, it needs to be flexible and work in two ways:

Mode 1: Track a Single Database
  • The user picks one specific database or view (e.g., "Doctor Visits").
  • The widget counts rows created or updated based on a date field.
  • Color intensity changes with the count (e.g., 1 = light green, 5+ = dark green).
  • My use case: Seeing how many doctors I visited each day over the year.
Mode 2: Aggregate from Multiple Databases
  • The user picks multiple databases or filters the whole workspace.
  • The widget combines all completed items from these sources into one daily score.
  • My use case: Getting a full picture of my day (visits + pharmacy sales + personal tasks) in one look.
Settings (To avoid the Black Box effect)

To make sure the user knows exactly what's happening, there should be clear controls:

  1. Data Source: Dropdown for "Single DB" or "Multiple DBs".
  2. Date Field: Pick which date property to track (Created At, Completion Date, etc.).
  3. Trigger: What counts as activity (e.g., Status = Done, or just row creation).
  4. Color Scale: User sets the numbers that change the color.
  5. Year Range: Pick which year to display.
Impact

Daily motivation: This visual shape makes you feel the progress and want to keep going, just like GitHub does for developers.

  • Productivity clarity: Instead of staring at tables and numbers, you see the full picture in a second.
  • Competitive edge: No self-hosted open-source tool has this natively integrated with databases.
  • Great for self-hosted users: For workflows like mine (tracking my job as a medical rep), this makes the dashboard actually useful, not just a pretty UI.
Additional Context

I'm a self-hosted AppFlowy user (running via Podman) and a contributor to the AppFlowy-IO org.

  • I work as a medical representative in South Sohag and I'm building a system to track doctor visits and pharmacy sales. This feature would be a huge help for my daily workflow.
  • This aligns with AppFlowy's AGPLv3 philosophy: powerful, transparent tools the user can actually control.
  • The main reference is GitHub's graph. Obsidian has community plugins for this, but nothing native in open-source tools.
  • I'm ready to help with testing or feedback if the team needs it.
Screenshot example
Image
Dominant language
Dart
Stars
79.1k
Forks
6.3k
Avg merge
17h 29m
Merged PRs (30d)
1

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AppFlowy-IO/AppFlowy

All issues in AppFlowy-IO/AppFlowy

Similar issues

More Dart issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.