Summary
As a Roblox developer, it is terrifying to pay out large chunks of R$ to development members because the interface is too small, minimal information is listed on selected group members, there is no suggested list of members to select from (i.e. based on join date, rank, permissions or previous payouts), numbers are not displayed with sufficient formatting, and there is no confirm receipt dialog.
It is critical that this interface is highly usable and that the design of the page is not prone to causing user error, since thousands of dollars worth of R$ may be moved between group funds and user accounts through this feature in a transaction at once.
The window is too small
The popup window does not resize to fit your screen and only occupies a very small portion of the screen. When the list contains more than 2 members, the third one and onward are hidden, which significantly reduces the usability of the popup, since development teams usually surpass 2 members nowadays. The image below has 3 members shown in the list, yet only 2 items can be viewed at once.
The window should either become a first class citizen and be embedded on the payout page rather than being a separate popup window, or the window should resize itself to fit the contents of the payout list, since I want to be able to have a full overview of what I am paying out to who without having to scroll constantly.
Not enough information displayed on members that are in the payout list
Suppose a random account joined the group that had a name like “Beeeism” and looked exactly like “Beeism”, and suppose I am not as attentive of a person and accidentally type “Beeeism” and add it to the list. I could accidentally pay out a huge sum of R$ to a random account that was intended for a developer. This is a terrifying thought and this makes me double-triple check the list myself 3-5 times before I press pay, which I shouldn’t have to do that many times.
If the rank was displayed together with the username and amount, such as “Developer” underneath it (if my rank was named Developer), I would be able to spot these mistakes much easier, and I wouldn’t have to open their profile through the headshot first to confirm that they are the right user.
Moreover, these windows should really show the full usernames, and not shorten them after so many characters with an ellipsis. There is plenty of space on my screen for the window to be wider and show all the usernames fully that way, usernames are only 20 characters max after all.
No receipt window
When pressing Pay, a confirm dialog should pop up with a read-only receipt of the information I just filled out. The dialog should tell me to closely inspect the information before pressing continue, such that I can take my time reading through the information I filled out without the visual clutter of buttons, text boxes, selection lists, etc. This allows for the person that is paying out to eliminate the possibility of mistakes much easier than performing the same task in the editable view listed in the screenshot above.
Numbers are not formatted well enough
Consider the following screenshot:
I would like the amount to be displayed with spaces or some other delimiter between the thousand terms, such that I can easily see at one glance that I am paying myself “50 000” rather than accidentally paying myself “500 000” or “5 000”. This would especially be a problem for people with a reading deficiency or disorders like dyslexia.
The “Available R$” entry on this popup is already formatted with commas, so this change would only make things more consistent, less prone to user error, and more accessible overall.
“Add Group Members” should suggest members and have a rank filter
Right now, we can only add members by first typing their usernames:
This is prone to user error and it shouldn’t require me to fill out the usernames. This frame should allow me to view a list of group members in order of reverse rank (first the group owner, then the people in the rank under that, etc) with a way to advance pages, or maybe it should suggest people based on their permissions (i.e. people with more permissions are listed earlier on), or sorted by how much R$ has been paid out previously to their accounts (that way, repeat payouts would be easier, since the developers would already be suggested at the top of the list). Either way, any kind of suggestion of members to add would be useful here, rather than starting out with an empty list and having to type usernames.
Moreover, it should also allow filtering by rank, such that I can filter the sort to only include the people in the Developer rank that I want to pay out to, and not accidentally select other users that are part of the group if they have a similar appearance/username.
By implementing the above, this search feature becomes on par with the member search feature under the “Members” tab, and it really should be on par or be even more refined than that element, since we’re talking about distribution of money here rather than the rather less inconsequential task of searching for members and viewing/changing their ranks.
Note also that currently, the list of results can only ever have 1 element, because it is not possible for 2 users to have the same username. So the only way in which this design lets you eliminate errors is by letting you check the appearance of the user before adding it, but it could be so much better in doing so by letting you search members like you can on the Members tab of group management.
Secondly, note that there is a link attached to the icon in the result (i.e. my profile link), but this is not actually usable without extra mouse click, since clicking the user icon just results in them being added to the list, not going to their profile.
Resulting behavior due to missing features
Due to the missing features, it is not comfortable for developers to pay out large amounts to many contractors at once. I personally have to resort to changing the markup on the page to make the window taller, such that it can fit all of the payout list on screen at once without scrolling, or by paying out each member individually and carefully checking that the profile link matches the user that I expect to be paying out to. Moreover, I have to carefully check that I am filling out the right amount, and not accidentally including a 0 more or less.
Conclusion
If Roblox is able to refine this payout window/feature as described, it would greatly improve the experience of paying out R$ from group revenue to development members, because less time would be needed to spot user errors, user error would be easier to spot altogether since less information is hidden/obfuscated. Paying out users would be less of a terrifying experience for developers this way, since the potential for error is reduced by improved page design.
