Flow/FPT/PTR UI/UX clutter and naming consistency

Is it just me, or does anyone else find the excessively long name “Flow Production Tracking” to be a UX anti-pattern ?

image

  • it’s not immediately clear that the menu item is a single menu item or three. Menu items should be a single word ideally, or 2 at most.

  • it takes up the same space of around 3 other menus!

  • The dropdown menu is now stretched excessively wide.

  • I have to read “Flow Production Tracking” on two menu items before I read the word that tells me what the menu item is… sigh.

These may seem like a trivial criticisms, but screen real-estate is a precious resource not to be wasted and ease of reading is critical for a positive user experience. For users with lower screen resolutions, this will cause menus to overspill the available space.

Can Autodesk please settle on a standard acronym for Flow Production Tracking and use that for UI elements? Why not have a FPT or “Flow” main menu, and use a prefix for loader and workfiles menu items : “FPT Loader”, “FPT Workfiles”. In fact, why do we need the prefix at all given the use has just clicked a “FPT” menu in any-case.

I appreciate the rebranding exercise was simply a case of doing a string-replace across the code-base, but it points to a worrying lack of consideration for the end user that no-one thought about how this might impact the UX.

On that note, there seems to be no consistency on how this brand update has been handled; we see the product labelled “Flow Production Tracking” applied across the entire ecosystem, so it would be logical to assume the acronym for this would be FPT, but it appears that the rebranded codebase uses the abbreviation PTR. So which is it?

PTR is the standard code abbreviation for “Pointer”, so any web searches for PTR are likely to be useless. PTR doesn’t include any reference to the word “flow” which is the obvious human-friendly name the product will be given.

Someone’s got to say it…

7 Likes

+1

I filed a support case to ask to reconsider the renaming. Perhaps other will join me against our beloved Autodesk ?

:slight_smile:

4 Likes

I think the menu name should just be Flow.

Same for Flow Production Track Workfiles.

Just call it Flow Workfiles

5 Likes

So… we have PTR being used in the code-base as the acronym for FPT, but I’ve just noticed on this forum, the tags for “sg” have been updated to “fptr”!?

Please don’t tell me this means the decision has been made to update the codebase to use fptr as the prefix? What does the “R” stand for? or is it FPTr ?

:person_shrugging:

Can I suggest, if we must replace the prefix in the codebase, keep it to two characters. eg “fp” or “pt”.

image

1 Like

Seriously guys? “Flow Production Tracking Application Session Launcher”? Would you consider please renaming the “Flow Production Tracking Application Session Launcher”, to something more concisely meaningful like “Log In” so our artists don’t have to try to parse “Flow Production Tracking Application Session Launcher” to understand the implications of approving the launch of a Flow Production Tracking Application’s Flow Production Tracking session. It’s kinda Flow Production Tracking annoying. :rage:

3 Likes

I noticed tk-maya has a the option to set the default menu name to “sgtk” instead of “Flow Production Tracking”.
There’s also this PR which allows any custom name : SG-35286 - Add new setting to customice the menu name by emunoz-hampa · Pull Request #110 · shotgunsoftware/tk-maya (github.com)

2 Likes

Thank you for showing off that PR, will be implementing that today. Really tired of explaining to my users that Autodesk have renamed it again to something even more absurd.

3 Likes