-
Notifications
You must be signed in to change notification settings - Fork 309
Make combined feed quicker to reach #1164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
a-home
The home screens of the app; finding and starting conversations
beta feedback
Things beta users have specifically asked for
Milestone
Comments
Another user saying that "Combined feed" is the most important view for them: https://chat.zulip.org/#narrow/channel/48-mobile/topic/Flutter.20app/near/2008115
|
gnprice
added a commit
to gnprice/zulip-flutter
that referenced
this issue
Dec 18, 2024
gnprice
added a commit
to gnprice/zulip-flutter
that referenced
this issue
Dec 19, 2024
Another user saying "Combined feed" is important to them, in a beta-feedback email to support@:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
a-home
The home screens of the app; finding and starting conversations
beta feedback
Things beta users have specifically asked for
Currently in order to reach the combined feed, it takes two taps: the menu button in the bottom nav bar, and then the "Combined feed" option in the middle of the menu.
We've heard from a couple of users (chat thread) that the combined feed is the most important view for them on mobile, and it'd be good to make it quicker to get to.
For example it could appear as one of the options in the bottom navigation bar on the home page. OTOH one tricky thing there would be that we currently don't show the bottom nav bar on message lists (rationale here and in the message from Vlad just below that); so we'd have the oddity of tapping a bottom nav bar button give you a page where the bottom nav bar is gone, or else we'd show a bottom nav bar there after all despite the reasons we currently don't do that.
This issue thread is here to help us track user feedback for future design conversations. This is not an issue that's ready for someone to pick up and work on.
The text was updated successfully, but these errors were encountered: