[FR] Database views & linked views should live inside their database (collapsible in the sidebar), not as separate sidebar items
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue gives no file or test pointers. Begin by locating the sidebar tree builder in the Flutter codebase and how database views are inserted as nodes. Done means views are contained under their database in the sidebar, not flattened as separate items, per the described principle.
Written by the indexing model from the issue text.
Description
Description
In AppFlowy, every view of a database — and every linked view (referenced grid / board / calendar) — is injected into the sidebar tree as its own node, sitting next to real pages and real databases as if it were a standalone item. The same object (a view) therefore exists in two places with two different meanings: inside the database block it behaves like a tab/capsule, but in the sidebar it behaves like a page. The sidebar tree stops reflecting the real structure of the workspace.
A concrete example from my own workspace (Screenshot 1):
- The page
Tracker Event Medical Rebcontains two databases:Doctor Viewswith 6 views: Doctor Views, Al-Monsha, El-Usayrat, Gerga, Al Balyana, Dar El Salam.Plan Weakwith 7 views: Plan Weak, Saturday, Sunday, Monday, Teusday, Wenesday, Thursday.
- Inside the page, these views are nicely contained as tabs/capsules on top of each database block (this part already works well).
- But in the sidebar, all 13 view names are ALSO added as child items under the page, mixed together with real pages and real databases. From the sidebar alone it is impossible to tell:
- which entry is a real page,
- which entry is a real database,
- which entry is "just another view of a database I can already see above".
Screenshot 2
– AppFlowy sidebar: every view of "Doctor Views" and "Plan Weak" flattened in as child items, mixed with real pages and databases](PASTE_SCREENSHOT_1_HERE)
Why this becomes a much bigger problem now (and will keep growing)
AppFlowy is no longer a small app. Now that it supports mature database features — especially formulas, plus relations, rollups and linked views — a serious workspace naturally grows many views per database, because each view is built to do one specific job in the system (one filtered view per city, one per weekday, one aggregated view per status, one linked view embedded in a report page, and so on).
In my system every linked view has a specific function. That means the number of sidebar nodes grows linearly with the number of views I create. Only two databases with ~13 views already make the sidebar unreadable (Screenshot 1). A real CRM or research tracker with dozens of linked views will make the sidebar unusable. The more we use AppFlowy's best features, the more the sidebar punishes us.
The behavior I am asking for (a principle, not a pixel-copy of anyone)
I am NOT asking AppFlowy to look like any other product. I am asking for one information-architecture principle:
The sidebar should show the structure of the workspace (pages and databases). Views are presentations of a database, so they should live inside their database — not beside it in the tree.
Concretely, any of the following (or a combination), implemented in AppFlowy's own design language, would solve it:
- Collapse views under their database in the sidebar, collapsed by default. The database entry gets a small toggle; views hide behind it and only appear when I explicitly open it. Each view row clearly shows which database it belongs to.
- A per-database option: "Show / hide views in sidebar". Users who like today's behavior keep it; users with big systems turn it off.
- Linked views created inside a page stay inside that page. An inline linked-view block should not create a new sidebar node at all, unless the user explicitly pins/favorites it.
- Keep and strengthen the in-block tabs (capsules). The tabs row on top of the database block is already the right home for views; overflow views can be grouped into a "more views" menu so the block stays compact even with many views.
- Every linked view keeps its own independent name, plus a visible way to jump back to its source database (a small link/breadcrumb on the view), so at any moment I can answer: "where does this data come from?".
These are suggestions for the principle; the exact UI is up to the maintainers. What matters is: views stop competing with pages for space in the sidebar.
Impact
Who is affected: anyone building a real multi-database system in AppFlowy — CRMs, trackers, research workflows, team dashboards. The pain scales with formulas/relations/linked views: the more powerful the database features get, the more views users create, and the more cluttered the sidebar becomes.
- Current pain (measured in my own real workspace):
- The sidebar no longer tells me what belongs to what; I genuinely cannot map sidebar entries back to their databases (Screenshot 1).
- Navigation cost grows linearly: every useful new view = one more row of noise.
- Risk of mistakes: a view row in the sidebar looks close enough to a page row that deleting/moving the wrong item is a realistic fear.
- First-impression cost: a new user who builds their first multi-view database immediately sees a tree that "looks broken", which hurts trust in an otherwise excellent FOSS product.
- Benefit if fixed:
- The sidebar reflects the real workspace structure again (pages + databases), at any scale.
- Users can create as many purpose-specific views as formulas/relations enable, with no navigation penalty.
- Less cognitive load, fewer accidental operations, cleaner onboarding.
- No breaking change needed: with default-collapsed or opt-in/opt-out settings, existing workflows keep working exactly as they are.
Additional Context
- My real-world case (why I feel this deeply): I am a bioinformatics researcher, and part-time I organize the CRM of a medical-rep team. In that CRM I created only two linked view databases — and the sidebar immediately became tangled: I could no longer tell which entry belongs to which database. Screenshot 1 is my actual workspace, attached as practical evidence of what I am describing, not as a hypothetical.
- Attached screenshots:
- Screenshot 1 (AppFlowy): the sidebar of page
Tracker Event Medical Reb, with all views ofDoctor ViewsandPlan Weakflattened in as child items. - Screenshots 2–5 (from another, proprietary tool — Notion): attached ONLY to illustrate the alternative information architecture (views contained as tabs/capsules inside the database block, overflow compressed into a "more" menu, sidebar staying clean).
- Screenshot 1 (AppFlowy): the sidebar of page
Screenshot 2
Screenshot 3
Screenshot 4
Screenshot 5
- Important clarification — this is NOT a "copy Notion" request: I deeply respect that AppFlowy is a FOSS project with its own identity, and I want it to stay itself. The screenshots of the other tool are here only because they demonstrate the information-architecture principle I am describing (views belong to their database, not to the workspace tree). I am asking AppFlowy to adopt the principle in its own design language, not to clone anyone's UI. Inspiring from correct ideas is not copying.
- Related discussions in this repo (same root cause): "[FR] linked views should be hidden instead of auto added" (Oct 2024); the v0.11.0 fix "Linked views should be hidden instead of automatically added to the original database"; the release note "new linked views will only show up under the pages where they are added"; and "[FR] Option to hide sub-pages from left sidebar navigation". Together they show the community keeps hitting the same wall: the sidebar tree is being used to hold objects (views) that users do not think of as tree nodes.
Clarification: Information Architecture, not a code bug
Just a quick follow-up thought to clarify my perspective:
I don't see this as a code bug at all — the backend state management for views is actually great. I see it more as an "Information Architecture" gap. Currently, the sidebar tree is being used to hold objects (views) that users don't mentally model as standalone tree nodes.
Fixing this UI hierarchy would just align the app with how users mentally organize their data, especially as features like formulas and relations scale up. Hope this makes my suggestion clearer! 🙏
I am happy to provide more screenshots, test builds, or edge cases from my workspace if that helps.
- 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AppFlowy-IO/AppFlowy
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
AppFlowy-IO/AppFlowy#9147 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AppFlowy-IO/AppFlowy#9118 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
AppFlowy-IO/AppFlowy#9094 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AppFlowy-IO/AppFlowy#9075 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
AppFlowy-IO/AppFlowy#9074 ·
Maintainers usually reply within 1 day
All issues in AppFlowy-IO/AppFlowy
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
ccch1mneyyy/dsh-Go#1682 ·
Maintainers usually reply within 1 day
-
help wanted
Difficulty 1/5 Under an hour Newbie friendliness 76/100
pesaclarity/ujumbe-parsers#64 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
patarapolw/lingua_srs#278 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
dreautall/waterfly-iii#890 · 1 comment ·
Maintainers usually reply within 1 day