Skip to content
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

UI/UX: Pillar type selection is unnecessary when spawning a Pillar #3

Closed
vilkris4 opened this issue May 4, 2023 · 3 comments
Closed
Labels
bug Something isn't working

Comments

@vilkris4
Copy link

vilkris4 commented May 4, 2023

Describe the bug
When spawning a Pillar the user is presented with a Pillar type selection step. Only one Pillar type can be selected, making it an unnecessary step for the user.

To Reproduce
Precondition 1: your account must have enough fused QSR to pass the initial Plasma check

Steps to reproduce the behavior:

  1. Launch Syrius v0.0.6
  2. Navigate to the Pillars tab
  3. Click on the Spawn button in the Create Pillar widget
  4. Plasma check > click Next

Expected behavior
The next step should be QSR management.

Actual behaviour
The next step is Pillar type selection.

Screenshots

Additional details
In the v0.0.6 update the legacy Pillar registration feature was removed which makes the Pillar type selection unnecessary since only the "regular Pillar" type can now be selected.

Desktop

  • Syrius version: v0.0.6
  • OS: any
  • Commit hash: c996cc4
@vilkris4 vilkris4 added the bug Something isn't working label May 4, 2023
vilkris4 pushed a commit that referenced this issue May 4, 2023
@georgezgeorgez
Copy link

Not sure if I would consider this a bug
Maybe need a category for "nice to have"
Definitely want to have good UX/UI and I understand the need for satisfying personal aesthetics
so if it's easy to change go for it

but the pillar registration flow isn't something that is used too often so i wouldn't consider this a priority in any case

@sol-znn
Copy link
Member

sol-znn commented May 6, 2023

should we have an improvement category?

@vilkris4
Copy link
Author

vilkris4 commented May 6, 2023

I'm fine with labeling it as something else, like improvement if it makes more sense to others. UI/UX issues aren't always functional bugs but in my opinion they're still bugs, since it's an end-user facing application. UI/UX shouldn't really be about personal preference but primarily based on generally accepted guidelines for good usability, such as these.

This isn't high priority but it is a quick thing to fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

No branches or pull requests

4 participants