Skip to content

Button reorder request #8136

Open
Feature
Open
Button reorder request#8136
Feature

Description

@SalmonSnaked
SalmonSnaked
opened on Oct 27, 2026
  • I checked the existing issues for duplicate feature requests
  • I have ensured my Modrinth App installation is up to date; v0.22.0 on Linux (Flatpak)

Is your suggested feature related to a problem? Please describe.

This is a silly small thing, but I had the time to complain about the cognitive load I experienced every time interacting with these buttons. The artist palette button, which arguably is the most used one, is not in a consistent location... I merely ask for the instance creation button order to move "Customize" to the middle.

Image Image

Activity

  1. SalmonSnaked
    added the
    Feature
    issue type on Oct 27, 2026

  2. Ceebug commented on Oct 27, 2026

    @Ceebug
    Ceebug
    on Oct 27, 2026
    Contributor

    Nice attention to detail

  3. Ceebug commented on Oct 27, 2026

    @Ceebug
    Ceebug
    on Oct 27, 2026
    Contributor

    I think i can make a pr to do this

  4. SalmonSnaked commented on Oct 27, 2026

    @SalmonSnaked
    SalmonSnaked
    on Oct 27, 2026
    Author

    Yeah, even I was able to swap the web elements for these buttons.
    This is probably not seen as a high priority, but all the while, a suggestion couldn't be simpler than this.

    To summarize, I think the most intuitive consistency fix would be changing the instance settings dropdown buttons to Upload, Customize, and Remove (from Replace icon, Edit icon, and Remove icon). This would align with the previously suggested Upload, Customize, and Randomize order of the instance creation screen ;)

  5. Ceebug commented on Oct 28, 2026

    @Ceebug
    Ceebug
    on Oct 28, 2026
    Contributor

    So...

    Instance Creation
    ⬆️ Upload icon
    🎨 Customise icon
    🔄 Randomise icon

    Instance Settings
    ⬆️ Upload icon
    🎨 Customise icon
    🗑 Remove icon

    Is What ur asking for?

  6. SalmonSnaked commented on Oct 28, 2026

    @SalmonSnaked
    SalmonSnaked
    on Oct 28, 2026
    Author

    Exactly! Although it might be better without the repeated "...icon" suffix, for readability.

  7. Ceebug commented on Oct 29, 2026

    @Ceebug
    Ceebug
    on Oct 29, 2026
    Contributor

    I will work on this issue.

    Although I think:

    • Upload vs Replace is intentional.
      One is setting the imge, one is replacing it.

    • Edit vs Customise is also probably intentional.
      One is customising the image before the instance is created, one is then editing the image after you have set it.

    • The button order should be changed.
      Consistency of button order is a really important thing for UX design.

  8. SalmonSnaked commented on Oct 29, 2026

    @SalmonSnaked
    SalmonSnaked
    on Oct 29, 2026
    Author

    Yes, I understand where you're coming from. I'd say we need to prioritize familiarity over accuracy, though.
    Even though the context technically differs, the actions are identical. With this, the most frictionless UX would be to prioritize having familiar words over precise and differing ones across the app. Our brains tend to work better with identical elements shared across different places and can easily bridge potential behavioral differences depending on the context. The differently labeled actions for essentially the same flow only create cognitive load, which is the crux of the issue I'm circling around.

  9. Ceebug commented on Oct 30, 2026

    @Ceebug
    Ceebug
    on Oct 30, 2026 via email
    Contributor

  10. Ceebug commented on Oct 30, 2026

    @Ceebug
    Ceebug
    on Oct 30, 2026 via email
    Contributor

  11. Ceebug commented on Oct 30, 2026

    @Ceebug
    Ceebug
    on Oct 30, 2026 via email
    Contributor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Feature

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions