Team · Backend
Easy Klin
Laundry platform for multi-branch businesses. I built parts of the NestJS API.
Team project · code private
- 4
- user roles
- 3
- apps: mobile, web, API
Overview
My role
Backend developer in a team, on the NestJS API (ek-api). Team project: I did not build the whole platform.
Problem
Laundry businesses with several branches cannot follow orders, staff and prices across branches.
Solution
A mobile app, a web admin and an API with 4 roles: customer, agency staff, agency manager and administrator.
Result
My tickets shipped with tests: customer profile with addresses, catalogue service combinations, sales counting. Quality gates stayed green.
Stack
NestJSNext.jsFlutterGitLab (self-hosted)CI/CDSonarQube
Architecture
- Flutter app
- Next.js admin
- NestJS API
- Database
- GitLab CI
- SonarQube
Highlights
- 01 Ticket-based sprints on a self-hosted GitLab
- 02 Rebase, then merge request, then review
- 03 CI pipelines and a SonarQube quality gate
- 04 Tests written with every feature
Learning
A strict process taught me small changes, rebase before review, and trust in the pipeline.