-
Notifications
You must be signed in to change notification settings - Fork 711
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
[Feature Request] UI/UX Enhancement - Creating a back button on relevant modals/dialogs/views #2825
Comments
I dont see as a problem dont have a close/back as the downloads and settings views are like tabs of the application. |
Yeah sure, I'll make a PR with PoC for your perusal. |
Hi @jeanfbrito, Team, Apologies for the delayed response on this. Had my Midterm Examinations, which got over today. I understand your Tabs approach, i.e. imagining Add new server, Downloads, Settings & Different Servers as separate 'Tabs' (like chrome tabs) & user is switching between tabs. Personally, having a Back button makes sense because Add new server, Downloads & Settings are different from server buttons/views because they have a different purpose which affects whole desktop app (manage downloads, settings, add new servers etc. across the entire Desktop app). To align your tabs analogy with what I implemented, the proposed solution would retain the tab structure while introducing a dedicated Back button for improved UX (for E.g., take the PFB the outputs of my POC & let me know your thoughts on this & the way forward ! POC SpecificationsI have created a Video demo:back_button.webmSource CodeThe code for this can be viewed & cloned from feature/back_buttons branch in my fork of this repo. Guidance requiredI faced challenges with creating new actions similar to |
Hi @jeanfbrito , Let me know your thoughts in this. |
Is your feature request related to a problem? Please describe.
Hi Rocket Chat Team,
I have been using the app (on Ubuntu 22.04.3 LTS) for some time now & love the seamless functionality & features built into the Desktop app.
During my usage, I observed an enhancement in the user interface that I believe could improve the overall navigation experience. Currently, there is no dedicated
Exit
orBack
button withinAdd Server
,Download
&Settings
views/dialogs. While the application offers a plethora of features, the absence of a straightforward way to navigate back might pose a slight challenge for users, especially those accustomed to such navigation elements in standard interfaces.Describe the solution you'd like
I propose adding an
Exit
/Back
button or a ❌(cross) in the top-right or top-left corner of theAdd Server
,Download
&Settings
Views, consistent with UI design principles. It would allowing users to easily navigate back to the previous screen, oropen.rocket.chat
page/view.For a better understanding of my request, I have attached screenshots of similar UI element that I observed while using Discord (circled in green) that I would also like in the Desktop app:
Describe alternatives you've considered
An alternative to this is you click the
open.rocket.chat
button (ref. screenshot below) on the top left of the root window which takes you to theopen.rocket.chat
server. I presume that if there are multiple servers, clicking on that server button leads to the respective Panel/Server View.Additional context
Benefits:
Exit
orBack
button aligns with common UI patterns, enhancing the overall usability of the desktop app.Implementation:
I have a potential implementation in progress and can provide a pull request once the enhancement is approved. As a PoC, I implemented this functionality in the
Add Server
view that pops up when user clicks the ➕ sign in theSideBar
. Please refer the screenshot below:Screenshots (of PoC implemented):
Clicking
Exit
takes the user back tohttps://open.rocket.chat/
Note:
Please let me know if the scope for this needs to be augmented to cover other views/elements for uniformity or adding key binding to this functionality (like pressing
Esc
takes you back as well). I mentionedAdd Server
,Download
&Settings
because these are the views/functionalities most commonly used by me.The text was updated successfully, but these errors were encountered: