Confusing app settings

littlefox commented

2026-10-18 10:03:24 +00:00

Owner

Opening the App settings you still have the "Read next post" button at the bottom with the "Save" and "Close" buttons out of view. The user thinks the button for reading next post will close the settings, but it does not. Close and Save are not visible to the user and the user then thinks they can close the tab without actually saving their setting.

Make the settings screen its own, not just taking up the center reading space of the UI.
Make the settings save automatically.

Opening the App settings you still have the "Read next post" button at the bottom with the "Save" and "Close" buttons out of view. The user thinks the button for reading next post will close the settings, but it does not. Close and Save are not visible to the user and the user then thinks they can close the tab without actually saving their setting. Make the settings screen its own, not just taking up the center reading space of the UI. Make the settings save automatically.

littlefox added the

area/ui

kind/bug

labels

2026-10-18 10:09:25 +00:00

littlefox commented

2026-10-18 10:09:25 +00:00

Author

Owner

Triage: a UX bug. The plan is for settings to become a full screen of their own: no command bar, no side columns, a back/close button at the top. Changes then save by themselves, with no Save button.

One catch with saving automatically: the LysKOM user area is stored as a text on the server, so every save writes a new text. Rather than one write per click, changes save when you leave the settings screen (back, close, or going elsewhere), with a short 'Sparat' note. Device-only settings like the theme take effect at once, as they do now. Next after #96.

Triage: a UX bug. The plan is for settings to become a full screen of their own: no command bar, no side columns, a back/close button at the top. Changes then save by themselves, with no Save button. One catch with saving automatically: the LysKOM user area is stored as a text on the server, so every save writes a new text. Rather than one write per click, changes save when you leave the settings screen (back, close, or going elsewhere), with a short 'Sparat' note. Device-only settings like the theme take effect at once, as they do now. Next after #96.

littlefox referenced this issue

2026-10-18 10:11:30 +00:00

HTTPS mode for the Docker image (installable app on the home network) #98

littlefox referenced this issue

2026-10-18 11:41:59 +00:00

Soak: a reconnect once stalled over 30 s at 'Återansluter…' #109

littlefox referenced this issue from a pull request that will close it,

2026-10-18 11:42:29 +00:00

Settings: a screen of their own that saves itself #110

littlefox referenced this issue from a commit

2026-10-18 11:42:31 +00:00

Settings: a screen of their own that saves itself

littlefox closed this issue

2026-10-18 12:01:12 +00:00

littlefox commented

2026-10-18 12:01:13 +00:00

Author

Owner

Merged in #110. Verified: tools/e2e.sh 171 passed (soak once flaky, #109), a new spec for the screen and saving on leave, screenshots on desktop/Android, CI run green.

Rows
Columns

Confusing app settings #97