Easy to Use
What if the end user is also the client? Most apps don’t just have a user-facing (by which most developers actually mean ‘customer facing’) side - they also require a Content Management System (CMS).
A CMS allows the operator of the application - in this case the restaurant owners - to access, edit, and create information it contains - hence ‘content.’However, some CMS aren’t particularly intuitive, and the admin user may not feel confident that they can control the way information is displayed to the end user (the customer).
Administrators understandably want to make sure that users see what they want them to see for many reasons, including maintaining consistent formatting, avoiding errors, making sure the app is attractive, and ensuring any messaging is delivered correctly.
For example, if an image of a product that looks good to the admin when it’s uploaded appears pixelated to the end user - even for a few moments before it’s corrected - that can damage the image of the brand.
Alternatively, inaccurate pricing data could cause the customer frustration or disappointment, or even drive away customers if the prices displayed are higher than intended, harming revenue.
To avoid these downsides and give administrators maximum confidence when using the system, we included a preview feature allowing them to see exactly what the user will see before posting a new product (or any other user facing information, such as a daily deal).
The team created and distributed physical advertising, such as posters and pamphlets at participating restaurants, particularly at the point of sale.To further drive uptake, our developers visited restaurant locations, training staff on how to use the app.
This made the process of collecting and spending points smoother for users and had the additional benefit of giving checkout staff the ability to assist customers with the app if necessary.