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

Introduce smart QR code size handling and remove user options? #187

Open
rugk opened this issue Apr 25, 2019 · 3 comments
Open

Introduce smart QR code size handling and remove user options? #187

rugk opened this issue Apr 25, 2019 · 3 comments
Labels
discuss me invitation to discuss this topic, this may need some more opinions usability/UX

Comments

@rugk
Copy link
Owner

rugk commented Apr 25, 2019

Problems

Solution

@bfred-it suggested in #35 (comment):

Second, I didn't even realize but there are 3 options for the size. I think that instead of asking the user, it should just do it automatically:

  • overflow menu: fill available area
  • mobile screen: fill screen [with some padding]
  • popup: remember the last size

So this would result in the removal of three size options and trying to "intelligently" do what the user might want.

This would also:

  • remove the way to statically define a fixed size of the QR code
  • removal of the option to not remember the QR code size

Analysis of places

Actually, I see it's kinda hard, because the add-on can appear in many places with different restrictions:

Place height width does remembering size make sense?
popup resizable (with max) resizable (with max) yes
overflow resizable (with max) fixed no?
mobile screen fixed fixed (and small!) no
tablet screen fixed fixed yes?

The last column is a hard one, because it's already subjective, but actually, we might even have to remember different sizes, based on whether it is a tablet screen or not…

Questions

  • What use cases could be destroyed when we remove it?
  • Do users actually care/need the three size options or are they really redundant?
  • On fixed size "screens" (mobile + overflow) should there still be a resize button?
  • If we take Adjust QR code size based on QR code content? #90 into account, we would need to have a way more "flexible" generation method for QR codes.
@rugk rugk added usability/UX discuss me invitation to discuss this topic, this may need some more opinions labels Apr 25, 2019
@rugk
Copy link
Owner Author

rugk commented Apr 25, 2019

IMHO…

What use cases could be destroyed when we remove it?

  • As a user, I might want to save my QR code in a fixed size.
  • As a user, I might just not remember the QR code size, because I only have temporary bad conditions or so. (Personally, i sometimes just increase the size up to the limit then, but won't want to see this the next time I open it.)

@rugk rugk changed the title Consider simplifying size handling Introduce smart QR code size size handling and remove user options? Apr 25, 2019
@rugk rugk changed the title Introduce smart QR code size size handling and remove user options? Introduce smart QR code size handling and remove user options? Apr 25, 2019
@rugk
Copy link
Owner Author

rugk commented Apr 25, 2019

So @bfred-it, what i also don't like about your idea is the big removal of all user options. I mean, as the use cases above show, such a "clever" add-on could sometimes not really be efficient for you.

So I'd suggest to possibly still have these options:

  • Automatically adjust size. [if not somehow offer current user the current pixel input]
  • Remember last size.

Note these are checkboxes, so you can check both, none or one at one time. (Both shall be enabled by default.) Both only apply on resizable QR code pages. If fixed sizes are there, we try to automatically determinate a good size.

What I like about these settings is that they are self-explanatory and do not need such a big explanation as the current ones.

IMHO these would satisfy the use cases presented here.


BTW, I hope you see, this is way harder than one might think… 😉

@rugk
Copy link
Owner Author

rugk commented Apr 25, 2019

Oh your avatar always fits… 😜

But no, it's not that simple. Again you dismiss two use cases and completely ignore things like #90.
The correct implementation of this would be quite hard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss me invitation to discuss this topic, this may need some more opinions usability/UX
Projects
None yet
Development

No branches or pull requests

1 participant