Start with the appointment
I connected the calendar to client records and visit history, including notes, photos and products used. Deposit status, stock and invoices sit alongside that workflow rather than in unrelated tools.
Pazy
Keep the salon's administration close to the appointment, so the stylist can follow one workflow through the day.
The problem
Appointment details, previous treatments, deposits and product stock belong to the same job, but are easy to scatter across messages and notes. A mobile product also needs to handle connection gaps without silently losing the stylist's work.
My part
Product design and engineering. The cover shows the public website's hard-coded demonstration interface, not customer records. Production adoption and commercial results have not been verified.
What this shows
I can turn the details of a small service business into a focused product, then carry the workflow across web, mobile and backend systems.
Where it started
Pazy is a salon-management product for nail professionals working independently. It combines a public booking route with a web panel and native mobile implementations. The public website is available; the product is presented here as a prototype.
Interface preview
The decisions behind the product
Connect public booking to the panel
The booking endpoint checks for a conflicting appointment, matches or creates the client and writes the appointment in a transaction. It applies the salon's deposit policy and schedules reminder records.
Account for an unreliable connection
I built native iOS and Android clients with cached data and an outbox for supported changes. Synchronization retries queued work and exposes failed operations, with idempotency keys on API requests.
What came out of the work
One product model for the working day
The prototype links a booking to the client, appointment, visit record and salon operations. The same service is available through a web panel and native mobile implementations.
Work can survive a connection gap
The mobile implementations keep supported changes in a local queue until they can be synchronized. Pending and failed work is visible in the interface.
Inside the implementation
Explore the features, architecture and quality checks
What I built
- A public website and salon panel connecting the calendar, client records, visit history, products, deposits and invoices
- Public booking that checks appointment conflicts, creates the client and appointment together, and schedules reminders
- Native iOS and Android clients with cached data, queued changes and synchronization after the connection returns
- A visit workflow for notes, photos, used products and client history
- A demo-account flow populated with synthetic salon data
How it works
- BookA client chooses an available appointment; the salon's policy determines whether a deposit is requested.
- PrepareThe calendar and client record bring the appointment, previous visit and relevant notes together.
- Record the visitThe stylist adds notes, photos and used products to the same history.
- Keep workingMobile clients can queue supported changes while offline and synchronize when the connection returns.
Quality and reliability
- Booking writes use transactions and conflict checks; API idempotency keys support safe retries of mobile operations
- Mobile synchronization tracks pending and failed changes instead of treating every request as successfully saved
- The current deposit workflow uses manual payment confirmation; Przelewy24 payments and real KSeF submission remain unfinished integrations
- SMS delivery depends on a configured provider; the development provider logs messages instead of sending them
Technology
Explore another problem I worked on
- Sztuka HarmoniiConnected four booking platforms into one calendar, with patient booking and practice operations around it.
- Wielki DzieńBuilt an inquiry-response engine and studio CRM alongside the couples’ planner, connecting AI-drafted replies, offers, RSVPs, seating and budgets.
- EEG biofeedback demoMade recorded EEG signals explorable in the browser, with local file analysis that keeps the recording on the device.