Repository navigation
[Feature]: Add subscription groups / tagging system to organize subscriptions #172
Description
Activity
Hey @kapdon, thx a lot for the detailed proposal and especially for offering to contribute. I really like the idea, particularly for people who have many subscriptions and need a cleaner way to organize their feed.
What would interest u the most: working on the frontend, the backend, or both? There is no expectation for u to implement the entire feature alone.
The backend would handle the database model, account isolation, group membership, API endpoints and feed filtering. The frontend would handle group management, channel assignment and filtering.
If both parts interest u, I think the cleanest approach would be two smaller PRs: the Server contract first, followed by the Frontend integration. I can help review each part along the way.
For the first version, I would focus on named subscription groups:
- create, rename and delete groups;
- allow a channel to belong to multiple groups;
- add or remove subscribed channels;
- filter the subscriptions page and feed;
- preserve the existing global feed and ungrouped subscriptions.
Tags and PocketTube import are interesting too, but they can come later so the first contribution stays manageable.
The general development workflow is explained in Contribute. The setup and required checks are also documented separately for contributing to the Server and contributing to the Frontend.
Contributions should start from
devand targetdev. Once u tell me which part interests u, I can point u toward the relevant files, help define a good first step and review the design before u start implementing everything. I would genuinely appreciate the help!Reacted by kapdonI’m taking the backend-first path and have started the Server contract for named subscription groups. The first PR stays within the agreed v1 scope: account-isolated group CRUD, many-to-many subscribed-channel membership, subscription/feed filtering, and preservation of the global and ungrouped views. I followed the Server contribution guide, worked from
dev, and targeted the Server PR todevbefore beginning any Frontend integration.Work-in-progress branch: https://github.com/kapdon/TypeType-Server/tree/feat/subscription-groups-server
Backend PR: TypeType-Video/TypeType-Server#76
Thanks for merging @Priveetee , especially in answer my questions and providing clarifications.
I must admit. UI design isn't particularly my strong suit, but I'll take a shot at it.
Before I start, do you have any preferred design decision or scope for the group subscription feature? any guidance is appreciated or things to watch out for.
UX wise I'm thinking of borrow a lot of the flow from PocketTube as that is the one I'm most familiar with. I have no strong opinions on the design so I'm open for alternatives as well.
While planning the frontend integration, I realized the channel management view needs a quick channel centric representation of group membership. Fetching subscriptions once per group would require N requests, and adding
groupIdsto the shared subscription model would affect unrelated API paths.I opened a small follow-up Server PR here:
Reacted by Tax_TuxHey @kapdon, thx again for moving this forward! :)
I put a small clickable mock online so u can see the TypeType design language I have in mind for the Frontend part:
It uses mock data and the route is not linked from the UI yet, so u can explore it safely :p
If u have time, try it on desktop and mobile.
The flow I’m imagining is:
- after importing subscriptions, TypeType can suggest organizing the new channels;
- a dedicated management view with group filters, an ungrouped view and search;
- multi-select with bulk add/remove actions;
- inline group creation;
- each channel showing its assigned groups directly on its row;
- grouping staying optional, so nobody is forced to group every channel.
PocketTube can still be useful as interaction inspiration, but I’d like the visual and UX direction to stay consistent with TypeType’s own design language. This mock is only a starting point, not a pixel-perfect specification. Feel free to simplify the interactions, adjust the layout or suggest a better flow.
I’m much more frontend/UI/UX-oriented than backend-oriented. Feel free to share your ideas, and I’ll be happy to discuss the UI/UX with u as the flow takes shape.
One small GitHub note: it genuinely makes me a little sad not to see u in the repository contributors list yet. GitHub isn’t linking your commits to your account at the moment, so I’d really like to see u listed there too :)
For future commits, u can configure a GitHub-linked email by following this guide:
It should make GitHub attribute your next contributions to
kapdon:pThx again, I’m really happy to see this feature taking shape!
@Priveetee Hey, I put together two desktop prototype flows based on your mockup and TypeType’s existing design language.
1. Editing one channel
Selecting a channel opens its group memberships directly inside that row as a searchable multi-select. Existing groups can be removed, additional groups can be selected from the dropdown, and the changes can then be saved or cancelled.
This provides a quick way to edit one channel without leaving the channel list.
2. Editing channels in bulk
The groups in the sidebar act as filters over the same shared channel library. Selecting a group shows its members, while Invert switches the view to channels that are not currently in that group.
For example:
Select Tech → Invert the view → Select channels outside Tech → Add them to TechThe fixed controls above the list can then add the selected channels to a group, remove them from a group, remove all group memberships, or clear the selection. The GIF finishes by returning to the Tech view so the updated memberships can be confirmed.
The prototype is focused on the desktop group management workflow for now, I haven't look at mobile at all.
P.S. I noticed that TypeType-Video/TypeType-Server#80 was closed... is there something I should adjust before continuing?
What the freak sorry missclick I was tired yesterday and watching from my phone and I fall asleep with my phone open and I may have clicked on closed, sorry 😭
oh no worries, what you think about the UX flow here?
Reacted by Tax_TuxHey @kapdon, sry for the late reply!
I really like this direction :) The inline channel editing feels natural and keeps the context visible, while the bulk flow makes a lot of sense for users with many subscriptions.
The shared channel list with groups acting as filters also feels like the right mental model to me. I’d keep this general flow and only refine a few details:
- I’m not sure “Invert” is immediately clear. Something like “Not in this group” may be easier to understand.
- The selected count and current action should stay visible when filtering.
- “Remove from all groups” should probably require a confirmation since it is destructive.
- The mobile version will be important too, since this feature will mainly be used to manage large subscription lists.
These are just details though. The core UX direction looks solid to me :p
And sorry for the late response, I was busy with work and the release of TypeType and TypeType-Android :)
Great, I'll continue with your suggestions. I'll be traveling next week so it might take awhile.
Reacted by Tax_TuxGreat, I'll continue with your suggestions. I'll be traveling next week so it might take awhile.
No worries, take your time and enjoy your vacation it’s important! If at any point you’re no longer interested, no problem at all, just let me know and I’ll take over :)
I came here to suggest this feature and was glad to see it's already been worked on!
I'm self hosting and am a cloud engineer by day so would be willing to test a beta version if required.
Reacted by Tax_Tuxgot sick after the trip, feeling better now, resuming
Reacted by Tax_Tuxgot sick after the trip, feeling better now, resuming
Hello, I hope u're doing better ! Take ur time brother no need to rush, no worries ! If u have any question let me know :)
Type of request
New feature
What problem would this solve?
I have a lot of subscriptions and been using PocketTube extension to organize them for years and it’s hard to organize, prioritize, or quickly find subsets of channels I care about in TypeType even though I really like the fact you can view all three platform's videos. There’s no way to group channels (by topic, interest, or custom folders) or tag them for filtering. This makes managing many subscriptions and using the subscription feed a little noisy.
What would you like to see?
Add a subscriptions organization system (groups/folders and/or tags) so users can create named groups or assign tags to channels.
UI: allow creating groups/folders, assigning channels to groups, tagging channels, and filtering the subscriptions view and subscription feed by group or tag.
API/Backend: extend Subscriptions table or add a join table for groups/tags, add endpoints for CRUD on groups/tags and for filtering the subscription list/feed.
Import: consider supporting PocketTube export/import or offering compatibility with PocketTube formats as a migration path.
Inspiration: PocketTube (browser extension), Piped, and ytzero implement grouping/tagging or enhanced subscription views—referencing them may help design trade-offs and UX patterns.
I'm happy to PR this, if you have any ideas or design decisions I'd be happy to work within the requirements.
Area
Frontend (web app)