Skip to content

Conversation

@csillag
Copy link
Contributor

@csillag csillag commented Jul 29, 2025

Both in desktop and in mobile mode, when using the app, we have a button at the top, for launching the layer picker dialog.

Clicking this button brings up this dialog.

For some reason, in the mobile view, even when this dialog was up, the button (for launching the dialog) was still visible.

I think this serves no useful purpose.

  • For opening the dialog, we don't need it since it's open.
  • We also don't need it for closing the dialog, because there is a big cancel button for that.
  • The only marginally useful thing it still does is indicating where we come from (what was the current layer before opening the selector, but is not strictly required, because it's already marked as "active" in the menu.
  • It's presence is not consistent with the desktop mode
  • It's presence is counter intuitive, because we don't expect to see the button when we have already pushed it and it has already served it's purpose.

Therefore I propose removing it.

State Before After Comment
Desktop mode, selector closed image image App in default view, button is visible
Desktop mode, selector open image image Button is now hidden, since we are inside the dialog
Mobile mode, selector closed image image App in default view, button is visible
Mobile mode, selector open, network list image image Changed.
Mobile mode, selector open, layer list image image Changed.
Mobile mode, selector open, layer detaild image image Changed.

@github-actions
Copy link

github-actions bot commented Jul 29, 2025

Deployed to Cloudflare Pages

Latest commit: 605200323fb42a0d32c436a35a6d959da8d56e95
Status:✅ Deploy successful!
Preview URL: https://178cf290.oasis-explorer.pages.dev
Alias: https://pr-2101.oasis-explorer.pages.dev

@csillag csillag force-pushed the csillag/dont-show-layer-picker-button-in-layer-picker-on-mobile branch 2 times, most recently from 526dbe0 to e0d0229 Compare July 29, 2025 21:34
@csillag csillag marked this pull request as ready for review July 29, 2025 21:34
@csillag csillag self-assigned this Jul 29, 2025
</TabletBackButton>
)}
</div>
<MobileNetworkButton
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I expect this was intentional design for visual balance

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe so. I spelled out my rationale in the PR description, and asked @juresobocan for input.

@csillag csillag force-pushed the csillag/dont-show-layer-picker-button-in-layer-picker-on-mobile branch from e0d0229 to 6052003 Compare July 31, 2025 00:20
Copy link
Contributor

@lubej lubej left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would rather see, that we keep it.

@donouwens
Copy link
Contributor

I'm not convinced this is an improvement tbh. I agree that we are missing consistency with desktop, but if anything, we should go the other way around - showing the badge on desktop when the menu is active as well.

My argument would be that we should provide the user with clarity on which network they are on at all times. It's part of the usability heuristics of Nielsen and Norman - basically a fundamental requirement in UX.

I do not believe it hurts the user to show what network they are currently on.

@csillag
Copy link
Contributor Author

csillag commented Aug 11, 2025

I agree that we are missing consistency with desktop, but if anything, we should go the other way around - showing the badge on desktop when the menu is active as well.

OK, let's do that!

@csillag csillag marked this pull request as draft August 11, 2025 16:33
@csillag csillag changed the title Mobile: don't show the layer picker button when already in layer picker Correct mobile vs desktop inconsistency around showing the layer picker button when already in layer picker Aug 12, 2025
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.

5 participants