Fleviq

Fleviq is really two designs wearing one name: a role-based dashboard (Admin, Distributor, Store Owner) for managing a network of unmanned kiosk terminals, and the industrial design of the kiosk machine itself, plus the on-device software a customer interacts with at the terminal. I designed all three surfaces as client work. This project stays under NDA, so the client and the real product name aren't named here — everything below is about the product and the design work, not who it was for.

Managing a growing network of physical kiosk terminals is really two problems stacked on top of each other: the software side (who can see what, and how do you track a terminal's real-world state) and the hardware side (a machine sitting in public that a stranger has to operate correctly with zero instructions). The client needed both designed together so they'd actually match, not as two disconnected efforts handed to two different teams.

• Designing one dashboard that served three very different roles, Admin, Distributor, Store Owner, without turning it into a maze of permissions each role had to learn to ignore.

• Mirroring the kiosk's real device lifecycle, installed, online, pending approval, active, in the dashboard's own status and approval columns, so support staff could tell a machine's real-world state at a glance.

• Designing a two-step redemption flow a first-time customer could complete alone at a public terminal, with zero staff assistance and zero prior context.

• Keeping three very different surfaces, the internal dashboard software, the on-device kiosk software, and the physical machine itself, reading as one coherent product family instead of three separate design efforts.

• Designed three role-based dashboards from one shared design system, Fleviq's own colour and type system, so each role saw only what mattered to them while the product still felt like one thing.

• Built the dashboard's Status and Approval columns to track the kiosk's actual four-state device lifecycle directly, so a glance at the dashboard told support staff the real state of a machine in the field.

• Designed a two-step "Welcome to Cash Redemption Terminal" flow, scan a QR code, confirm, done, with a status footer (device ID, online or offline, version) always visible for support.

• Used one warm, consistent visual language, Fleviq's own colour, a warmer palette for customer-facing kiosk screens, white and grey for internal dashboards, so software, hardware, and on-device screens all read as the same product. I also vibecoded the dashboard frontend myself, handing developers a working UI to build from instead of a spec to interpret, which shortened the handoff.