I think I am confused by the use case here. Could you give an example of why you would want this feature? From your description it sounds like bookmarks should already cover this use case.
this post was submitted on 20 Nov 2023
5 points (85.7% liked)
Summit
741 readers
2 users here now
Community to discuss Summit, a Lemmy reader for Android.
App (Play Store): https://play.google.com/store/apps/details?id=com.idunnololz.summit
APK: https://github.com/idunnololz/summit-for-lemmy/releases
Patreon: https://patreon.com/SummitforLemmy
Ko-Fi: https://ko-fi.com/summitforlemmy
Website: https://summit.idunnololz.com/
founded 1 year ago
MODERATORS
Well, when I first started using this and saw that a list of communities was in the menu of the top left button. After I logged in, I was kind of expecting that a list of the communities that I'm subbed to didn't appear.
It would just make things easier and would be more intuitive for new users of this app. Especially since most other Lemmy clients have, and do, basically the same thing; have a user-subscribed section in that kind of section.
Also, with bookmarks, you can only bookmark posts not communities.
Ohhh I think you are missing a part of the app. If you swipe from left to right on the community/post list screen you will see your community bookmarks as well as your subscriptions.
You can also access that screen by tapping the menu button (bottom right) and then tapping "my communities".
Yeah, I was missing half of that part. I knew about the button but not the swipe to access. That would make sense.
In that case, maybe consider a guide or short tutorial for when people first install the app. Or something in the settings page showing how things can be accessed and whatnot.
Cuz a lot of this is stuff I probably would have never figured out and the same is very likely true for many others as well.
Yeah this is always a tough one. I hate tutorials and personally would never read them and auto dismiss them. The best app designs are ones where actions are intuitive or at the very least discoverable. This is a flaw of the "hamburger menu". It's not intuitive and it's usually hard to discover. In my past apps I constantly got feature requests to features that already existed in the side menu. Moving to the bottom menu pretty much got rid of all those bug reports despite a lot of people not liking it because it takes up screen space.
For Summit, I'm not sure what to do just yet. Technically the side menu has a button dedicated to it in the overflow menu so it's slightly discoverable but it's still buried. I think I'd have to think about it more. Maybe I can add a button to the "community browser".
I'm confused as to how the "hambbuger menu" is not intuitive. It's one of the first things people look for and if it is not there, they will see if the top right or left have a button that does the basically the same thing. And therefore, makes it one of the most intuitive things that an app like a Lemmy client can have.
Yeah you'd think so but I got at least one email a week about it back then.