/ Project
Digital signing Parpas
Commit
Release
Bugfix
Task
Mobile app and backend/API
Machine tools and industrial technical services
/ What
The project moved the service report signing flow into a mobile experience designed for technicians. Login, assigned reports, intervention detail and signature capture become part of a single path. Work on operational issues also highlighted concrete aspects such as screen space for signatures, ticket code validation, logout and technician data management, reducing manual steps and ambiguity when information returns to the system.
/ How
Kuama built a Flutter app connected to an ASP.NET Core backend on .NET 8 with PostgreSQL. The app manages authentication, service report consultation and signing; the API organizes users, roles, badges, devices, MAC addresses, company groups, tickets and signature files. This separation allows technicians to work from mobile while administrators keep rules and data in a more stable system.
/ The_result
Parpas now has a more controllable digital flow for signing service reports: the technician finds the report, collects the signature and sends it to the system; the backend stores information in a structured way and makes the relationship between intervention, user, device, badge and signature clearer.
/ Contributions
Centralized rules, simple signing in the field
The key technical point was moving critical logic out of the mobile app alone, modeling signatures, service reports, badges and devices as separate API domains. This keeps the field experience simple, while operational rules remain centralized, verifiable and easier to evolve.
A web configurator to guide the selection, measurements and variants of Schueco windows, doors and sliding systems.
A desktop management system to make orders, availability, sizes, barcodes, picking and labels more controllable in fashion retail warehouses.