[FR]Add Grouping Support for Grid View Databases in the Web Client
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- typescript
Research direction
Start by locating the Web client’s Grid View database implementation and compare its available controls with the Desktop client’s grouping behavior. Done means Web users can create and manage grouped Grid Views, including existing grouped views, with the Group option available.
Written by the indexing model from the issue text.
Description
Feature Description
Please add support for grouping records in Grid View databases in the AppFlowy Web client.
This functionality is currently available in the Desktop client, but the same database view does not provide grouping options when accessed through the Web client.
Current Behavior
In the AppFlowy Desktop client, users can group Grid View database records by a property/field.
In the Web client:
The Group option is not available.
Existing grouped database views do not provide the same grouping controls as Desktop.
Users must switch to the Desktop client to create or manage grouped Grid Views.
Use Cases
Grouping is especially useful for databases such as:
Tasks grouped by Status
Contacts grouped by Company
Projects grouped by Owner
Opportunities grouped by Stage
Meetings grouped by Customer
Records grouped by Category or Type
Without grouping support in the Web client, users working across both Desktop and Web do not have feature parity and must return to the Desktop application to manage these views.
User Impact
The lack of Grid View grouping in the Web client creates a significant usability gap between the Desktop and Web experiences.
Users who rely on grouped database views to organize information by status, customer, owner, category, project stage, or other properties lose that organization when accessing AppFlowy through the Web client.
This impacts users by:
Requiring them to switch back to the Desktop client to properly work with grouped databases.
Making the same database behave differently depending on which client is being used.
Reducing the usefulness of the Web client for users who primarily access AppFlowy through a browser.
Making it harder to quickly understand and navigate larger databases because records are presented as one continuous list instead of logical groups.
Creating friction for teams where some users use the Desktop client while others use the Web client.
Limiting the Web client as a complete alternative to installing the Desktop application.
For self-hosted deployments, this can be particularly important because organizations may want to provide users with browser-based access without requiring every user to install and maintain the Desktop client.
Adding grouping support would significantly improve Desktop/Web feature parity and make Grid View databases much more practical for users who depend on the Web client.
Potential Implementation Ideas
No response
Additional Context
No response
- Dominant language
- TypeScript
- Stars
- 354
- Forks
- 186
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 71
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-Web
-
[Bug] The inline code block should have a monospaced fontPossibly taken @Rezapurian claimed this 143 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
AppFlowy-IO/AppFlowy-Web#394 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 Half a day Newbie friendliness 22/100
AppFlowy-IO/AppFlowy-Web#692 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
[Bug] Unable to replace the selected text by pasted textMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 68/100
AppFlowy-IO/AppFlowy-Web#580 ·
Maintainers usually reply within 1 day
-
[Bug] Sidebar spaces appear empty after switching workspace (expand state is global and pruned per workspace; reload fixes it)Possibly taken @breken-ai claimed this 73 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 68/100
AppFlowy-IO/AppFlowy-Web#526 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
AppFlowy-IO/AppFlowy-Web#521 ·
Maintainers usually reply within 1 day
All issues in AppFlowy-IO/AppFlowy-Web
Similar issues
-
[MCP]: page snapshots in .playwright-mcp/ are not git-ignored (.playwright-cli/ is, since #42318)Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
microsoft/playwright#44289 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 Half a day Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
blamechris/chroxy#9272 ·
Maintainers usually reply within 1 day
-
no-repo-link tool-submission
Difficulty 1/5 Under an hour Newbie friendliness 66/100
BraveOPotato/NoSignups#2458 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
drmrd/vernacular#1061 ·
Maintainers usually reply within 1 day