Craig HB got their new app design by running a design contest:
Design a waiters order pad app
Check out Craig HB's App design contest…
Let the waiter take an order on a tablet and send it to the POS. This is a replacement for a waiter’s paper order pad – not a mobile POS. After being sent to the POS, the order is deleted from the POS so the waiter cannot look back at his previous orders (or any orders of the other waiters). If this app was human, it would be a runner taking orders from the waiters and running to the POS where it entered them.
Company website is www.comtrex.co.uk and our web app is http://ent.comtrex.co.uk
Clean, simple, uncluttered design. This app has very few features, but it does them the well. No photos. Function over form: easy to use more important than fancy design This app is going to be used by waiters continuously, so things like photos of food that will look nice to customers will just annoy the waiters after a while. Maybe not on the login page (because they will login once per shift), but definitely on the other screens. To be used on a 7-8 inch Windows tablet The designs that look good have used our company orange colour sparingly -- like the 99 Designs website. Orientation: The orientation should be determined by the Orders screen -- and the other screens should be the same. I would prefer it to be in portrait mode, because it is easier to hold and that is how most waiters hold the paper order pads. But it might have to be landscape because of the way we need the Order screen to work (see Orders screen section). BUT the orientation is not as important as the rest of the design -- because we can change that in the development stage.
NB: The most important screen (by a looong way) is the Orders screen. That the one that will determine the success of this app and the winning design. I would suggest submitting only that screen and afterwards building the Login and Table screens. 1. Login screen Display the restaurant name and the waiters (no photos -- just names). Does not have to be a list -- can by boxes/grid. The waiter logs in by selecting his name and them swiping a pattern lock. 2. Tables List screen Display the restaurant name, the waiter name and the tables. Each table should only have the table name and (on 1 or 2 tables) an icon alerting the waiter that an order has not be sent to the POS (probably because the waiter is out of WiFi range). The waiter clicks on a table to go to the Order screen. 3. Order screen The most important screen! This is where the waiter takes the order and sends it to the POS. You do not see previous orders here -- they have been deleted from the app when they were sent to the POS. This page is divided into: (1) the Menu -- all the items on the menu (2) the Order -- list of menu items ordered And they both need to be seen AT THE SAME TIME. So the waiter can enter items and see them on the order. Like always seeing your shopping basket while you are shopping. The most obvious way to do this (and what everyone in our office has suggested) is to have the screen landscape with the menu on the left and the order on the right. When you pick an item on the left, it appears on the right immediately. That does mean that the size of the menu becomes as small as a phone menu, so it might be a good idea to look at phone apps to see how they navigate through a menu. A number of restaurants have apps that let customers order. Or take-away apps. On the Order section, items on the order can be deleted and their quantities can be changed -- just like most ordering website/apps. When the waiter has finished, he clicks "Send" or "Clear". And he goes back to the Tables page. Tricky Thing #1: Menu hierarchy The Menu that the waiter clicks through can have many different levels. For a pizza, one restaurant might have it here: Pizza/Skinny Pizza Pollo. But another might have it under: Pizza/Skinny Pizzas/Skinny Pizza Pollo. So the design needs to handle a Menu with many different levels. The way our POS handles this is that it just opens a new screen for each new level. Tricky Thing #2: Modifiers Some menu items come with a selection of modifiers. So, a burger could come with "No Lettuce" and "Well Done". A menu item could have zero, one or many modifiers. In a previous version of this brief, I said you could get a modifier on a modifier -- forget that. You can get lots of modifiers, but only on a menu item (for this design at least). The waiter needs to select a modifier from the Menu section and see it on the Order section.
What to avoid
Avoid anything that slows down the waiter. Making the waiter type Showing information not required Anything designed for the customer -- remember, this if for the waiter.
£667 Silver package
Every design category has flexible pricing for all budgets. App design starts at $599.
Full copyright with production-ready files for digital and/or print.
It all began with a design brief.
A quick, interactive guide helped them understand their design style and captured exactly what they needed in their app design.
Designers across the globe delivered design magic.
Craig HB collaborated with designers to refine their ideas
When design entries come in, you can rate them so designers know what you’re looking for in your logo design.
99designs has great collaboration tools so you can pinpoint and capture your ideas
And then… they selected a winner!
Android File Host
Shaan was great to work with. Excellent design skills, very responsive, and quick to incorporate any and all feedback we provided. We would highly recommend him to others, and look forward to working with him for any of our future design needs.
Along the way, they met lots of talented designers…
We think contests are a super fun way to get design.
Recently completed contests:
Koji is a platform that lets anyone remix all kinds of internet things. (https://withkoji.com/) We have a library of hun
The apps shows the iOS home kit devices on an easy to under stable map on the iPad
We are looking for a great design for our bubble shooter game. See demo link. *The game is for web, phones and tablet
An app where restaurants can take orders from a food delivery platform.
We want to develop an easy to use Music, Podcasts and Audiobook app for kids <10 years old, that plays the content avail