2

I'm working on an app for a volunteer organisation (Scouting group) where users can indicate what he or she had to drink from the bar/fridge. This so an 'admin' can see how much each person had to drink and ask them to pay the drinks every 2 months.

The analog way this is done now, involves a big piece of paper, laid out in columns and rows. Rows indicate everyone in the group of people. The columns indicate drinks. So when a person drinks a Coke, he draws a small line in the box for Coca Cola with his name.

This table illustrates how the paper looks right now:

+----------+-----------+-------+------+
|    X     | Coca Cola | Fanta | Beer |
+----------+-----------+-------+------+
| John Doe | III       | IIII  | I    |
| Jane Doe |           | II    | I    |
| Thomas   |           |       | III  |
+----------+-----------+-------+------+

I've already made an app that uses this pattern:
User chooses a drink → user indicates for every person how much units they 'ordered' for that drink.

This means, when you get drinks for 5 people, whom all had a different drink, you have to do a lot of tapping to input everything. It's very important the users can quickly enter the drinks. Now the app is not used a lot because how slow it can get entering everything.

Is there a known UX pattern to solve this kind of problem? An example of an app doing this would also be convenient. I've tried searching for it. The fact I can't name the problem simply make this a touch hard.

Thanks for the input!

  • Are all the customers on the app or just the person ordering? What's the bar? Is it on a different app? – moot Dec 30 '18 at 17:12
  • The bar is literally a fridge with drinks, people can take drinks and have to enter the drink they took on a big list. Everyone that can take drinks is on the app. – Thomas de Wulf Jan 3 at 13:19
0

Im not sure what is your process exactly (how you take all inputs, and how you use this information further) but for me seems logical to Organize interface around "Drinks" .. So here is quick prototype suggestion

enter image description here

enter image description here

  • Hi, thanks! The current version of the app does something similar. The problem with this is: thera are over 40 people that a drink can be ordered for. This makes it very cumbersome at times to input everything. – Thomas de Wulf Jan 3 at 13:17
  • For searching users you can pleace search functionality / icon in upper right corner. Apart from that this seems to me no more UX than CX or process problem. Can users be logged in the application, and select by themselves what they ordered? – xul Jan 3 at 13:24
0

We found your question and conundrum quite interesting in the department, we came up with this.

The idea being you add or remove users from the patrons list, therefore you constrain the people you need to search to only those present. Secondly, quick access buttons open the relative items and you can tap to add those items and then save, showing the balance on close.

It's not finished and it needs refining, and you can't remove tapping completely, but I think this gets you to the tab scenario pretty quickly.

The item sold out idea is again to constrain the product list so the user doesn't have to bypass items that are not available, finally the product list is presented as card, making the product description, adding and sorting easier.

Primary interface

Adding drinks

  • This looks very good! Right now I'm working on the version for the patrons, where they can order drinks themselves using their smartphone. I don't know how well this concept will work on a smaller screen. But I am definitely going to reference this when starting to plan a tablet app. Thank you! – Thomas de Wulf Jan 3 at 13:15
0

It sounds like the problem is the app makes one user do all the work like a server (human waiter/waitress).

Everybody should use the app and order their own items.

Get more people on the app. It makes ordering faster and easier. Nobody has to be a server or somebody can run it. I don't know physically what it's like but the app can do a lot of the physical work of servers.

The current behavior should be the backup. Users can still do the current behavior and order for other people.

This could take that negative UX that one person has and turn it into a positive UX for everybody. They can order from the app instead of a person.

0

Firstly, I would the question what problem does this solve and is building an application the best way to solve this problem?

If there is good purpose for an app based solution, then I would suggest looking at QR scanning, with a bar code system, which gives each beverage a unique ID.

The user just has to open the app and scan the beer using the camera to create the invoice.

Having the user navigate the screen with a series of screen tapping is not how one enjoys a beer (or any cold beverage of preference). Bad user experience.

0

The barcode scanner is a fast input idea. You could maintain two simple lists on the cooler.

  • List 1 is the list of available consumers
  • List 2 is the list of products.

This is assuming that neither list is overly long, but could still be done with 40 people pretty quickly.

The use would be to scan a consumer's code then scan the product code. You have not added a tally mark to the system.

This can work for a single person getting up and getting drinks for themselves and or others.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.