Age old problem of lengthy and unfair queues at bars or other establishments. Opportunity as our development team is located in Cardiff with a wealth of students and bars. Problem is identified and backed by each member, therefore, we support the decision to commit Ourselves to develop our drinking solution.
To learn more about our solution, please use the table below.
| Application | Purpose | Demo |
|---|---|---|
| Mobile App | Customer app, built for iOS and Android | GIF here |
| Managerial App | Bar manager's interface to customise DrinKing implementation in their bar | GIF here |
| Server | Server | GIF here |
| Terminal | Bar Staff Terminal web app | GIF here |
We are using a Mongo database defined and queried using GraphQL. Our customer react-native Android / iOS App communicates to our database through a Node Js server. We are receiving live data changes by use of GraphQL subscriptions, enabled using an Apollo client.
- Cashless
- Bar equipment is expensive.
- Payment gateway - Stripe - vendor lock in. unprofitable with small charges and no additional fees.
- No use cases / success stories.
- App Deployment
- Server Deployment
- Ingredients schema support
- API protection
- Customer ratings
- Group baskets and payment splitting
- Loyalty Schemes
- Possible gamification features to promote loyalty and rewards
- Functionality to allow users to cancel orders or potentially change orders after placing them
- Out of stock functionality on terminal to alter users who have purchased orders with that particular out of stock ingredient