Skip to content

feat: add settings screen back button#567

Draft
ZaidNAlAsali wants to merge 1 commit into
MorpheApp:devfrom
ZaidNAlAsali:fix/settings-back-button
Draft

feat: add settings screen back button#567
ZaidNAlAsali wants to merge 1 commit into
MorpheApp:devfrom
ZaidNAlAsali:fix/settings-back-button

Conversation

@ZaidNAlAsali

Copy link
Copy Markdown

Summary

Adds a visible back button to the settings screen.

This gives users a clear way to return from settings without relying only on system gestures or navigation buttons, improving accessibility and discoverability.

Closes #396.

Testing

  • Ran git diff --check
  • Confirmed the only SettingsScreen call site is updated
  • Verified there is no existing reusable generic back/navigation string
  • Verified SettingsScreen did not already have a top app bar/header
  • Tried .\gradlew.bat :app:compileDebugKotlin, but local Android SDK configuration is missing:
    SDK location not found. Define a valid SDK location with an ANDROID_HOME environment variable or local.properties.

@LandonMoran

Copy link
Copy Markdown

Thank you so much, I was going to open an issue on this but I guess I don't have to being blind and all that, I physically don't know how to use the back gesture so I back button for settings is super nice though. To be fair, it wasn't a huge issue because I didn't enter the settings too often

@MarcaDian

Copy link
Copy Markdown
Contributor

This PR seems to be generated by AI. Currently, some redesign has been done in the dev version, but we don't have a concept for adding such a button to the current settings yet. The standard toolbar (added as I understood in this PR) is not suitable in terms of design. We are open to suggestions, preferably with a visual preview.

@ZaidNAlAsali

ZaidNAlAsali commented May 19, 2026 via email

Copy link
Copy Markdown
Author

@MarcaDian

Copy link
Copy Markdown
Contributor

I tried adding the back button to the bottom tab bar, so that it wasn't in a separate header, I don't know how correct that is. This button is read first in Talkback as if it were at the top, so there shouldn't be any problems for blind users with screen readers.

Screenshots

Screenshot_2026-05-19-23-27-54-074_app.morphe.manager.debug-edit.jpg

@LisoUseInAIKyrios

Copy link
Copy Markdown
Contributor

A back button on the buttom nav bar is unusual, and I agree I don't think it would look good with a top nav bar either.

Maybe we will figure out a different solution that isn't an explicit back button at all.

@MarcaDian

Copy link
Copy Markdown
Contributor

As a separate solution for screen readers, we could add an invisible back button. But some sighted users might want a visible button, so this is a controversial solution.

@LandonMoran

Copy link
Copy Markdown

Let you guys know that when a back button in the YouTube settings, like the custom settings menu you guys have, there is a back button. I can tell it's the back button, but not because it's labeled, specifically because it's the only unlabeled button. So I literally have to distinguish the back button by the fact that it's unlabeled, same with the refresh video button in the video player. That is basically the only issue I've seen. I'm still having the issue where occasionally when entering comments the application will crash. Although I still think that's an Android 17 bug, but it seems to be less frequent now so I don't know what's up with that. And earlier today I had a bug where literally when I turned up the volume it crashed my application

@LandonMoran

Copy link
Copy Markdown

What I mentioned also has to do also occurs with the save to watch later button. I just forgot to mention that cuz I don't use that button

@MarcaDian

Copy link
Copy Markdown
Contributor

How does this apply to the Morphe Manager?

@LandonMoran

Copy link
Copy Markdown

It doesn't but it's just something I'm pointing out because it has the exact same issue and I don't want the buttons here to be issue that the button's there have of no labels

@MarcaDian MarcaDian marked this pull request as draft May 20, 2026 22:43
@ZaidNAlAsali

ZaidNAlAsali commented May 21, 2026 via email

Copy link
Copy Markdown
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants