UX: "Read vs "Extra Actions"

#1

I’ve noticed that with every firmware update, more and more functionality is put into “extra actions” menus:

  • 125 KHz RFID extra actions now has “Read ASK” and “Read PSK”
  • NFC has extra actions now has “MF Classic Keys” and “Unlock NTAG/Ultralight”
  • Sub-GHz has a Read RAW option

etc.

What they all have in common is that they are all actually “Read” - yet from a UX/UI perspective, they are all over the place in the corresponding submenus.

Would it not make more sense to turn “Read” into a submenu, and then offer all different types of “Read” directly there - leaving extra actions for things that are not "Read"s? The current “Read” option could also then be placed in the “Read” submenu, but should be provided with a better title to understand when to use it vs the other options (Read Others?)

Thank you for your consideration.

2 Likes
#2

For me it’s good as is right now…

#3

What are ASK and PSK?

#4

Sounds reasonable.

But as I understand, the ‘Read’ should be a generic ‘Read and Identify’. If this don’t work for any reason, I can go in analysis with ‘Extra Actions’.
So the decision from the Flipper Team makes absolutely sense for me.

1 Like
#5

ASK is Amplitude PSK is Phase (Shift keying).