Printer Management Platform
Challenge
A multi-store European retailer needed a web interface to manage physical printers across all their locations — covering device overviews, settings, location assignment, and metadata. The project also served as the company's first introduction of Vue into their tech stack.
Solution
We built the web application using Vue 3 and an internal StencilJS-based UI component library, connected to a REST API following OpenAPI Spec 3 with OIDC authentication. We implemented OAuth-compliant auth including audience and permission checks, bridged gaps where the design diverged from the component library, and kept delivery on schedule by using mock data and mock services while the API was still in development. We also onboarded the development team into Vue, coaching best practices in component design and the Vue ecosystem.
Impact
The application launched successfully and became the foundation for future feature extensions. The team was fully onboarded into Vue with a solid understanding of component architecture and ecosystem best practices. Bug fixes contributed back to the shared component library benefited all downstream framework consumers.
Technology Stack
Project Overview
This project, delivered at CAMAO Tec (later rebranded to mmmake), involved building a printer management web application for a multi-store European retailer. The goal was to give operations teams a clear overview of all physical printer devices across their European store network, including device settings, physical locations, and associated metadata.
Key Features
- Device overview dashboard across all store locations
- CRUD operations for printer devices, settings, and metadata
- OIDC/OAuth authentication with audience validation and permission-based access control
- Integration with an internal StencilJS UI component library
- Mock-data layer to maintain delivery pace during API development
Technical Highlights
The application was built on Vue 3, marking the company's first adoption of the framework. The REST API followed OpenAPI Spec 3 and required implementing a full OIDC authentication flow against an internal identity provider. Where the product design diverged from the component library, we worked directly with the library owners to identify and resolve issues — fixes that propagated to all framework consumers of the library, including native web components.
Ready to Create Something Extraordinary?
Let's discuss how we can help solve your challenges and build something that drives real business value.
Get in touch