PourSelf
Case study opening
Problem first. Solution beside it.
The starting pointPourSelf was a self-service drink machine and app for which I was the sole developer, covering drink scanning, payments, IoT communication, backend services, admin tooling, and the public website.
01 / Problem
Where value was leaking
Venues wanted to sell more drinks without hiring more staff, but every self-service drink system was too heavy, too pricey, and too complex to bother with.
02 / Solution
How the rebuild closed the gap
PourSelf connected a physical drink machine, customer app, payments, and admin system. I was the sole developer across drink scanning, payment flow, machine communication, backend services, database and APIs, admin tooling, the Barhopp venue tie-in, and the public website.
03 / Result
The machine and software shipped as one working product used by real customers. I owned the software from the drink-scanning app and payments through the backend, admin system, deployments, security, debugging, and maintenance. I also wrote the application that secured ISK 20 million in development funding.
Hardware meets software
One connected product, from phone to machine.
PourSelf joined a physical dispenser, an embedded computer, a customer app, payments, backend services, and an operator admin. I owned the software side and the operational paths between every part.
- ISK 20m
- Grant secured
- 1
- Software developer
- Live
- Physical product
- Remote
- Machine operation
01 / Connected machine
Software reached into the physical device
A small computer inside the dispenser connected the machine to the internet and coordinated actions from the customer app and operator system.
Phone, backend, and device
Built the communication path that moved commands and state between the customer phone, backend services, and embedded computer.
Controlled remote routing
Managed DNS and controlled routing for remote operator access to the device.
Coordinated state
Kept drink scanning, machine responses, and payment state aligned across the live system.
02 / Operations
An admin built to run the business
The operator interface covered the machine itself and the commercial settings around each installation.
Machine control and health
Supported remote on and off controls, operating checks, machine status, and diagnosis when something stopped working.
Products, prices, and discounts
Built workflows for operators to manage products, pricing, discounts, users, and the settings needed for daily operation.
Customer and operator surfaces
Delivered the React Native and Expo app, React and Next.js admin, and public website as one product family.
Backend and monitoring
Built Node.js services, database and APIs, payments, scripts, deployment, Sentry monitoring, debugging, and maintenance.