Business application2026-08-16
Salon appointment manager
The salon keeps agreed appointments in one working view: new entry, schedule overview, editing and an archive of completed records.
- Client
- Private client (name is not published)
- Type
- Internal appointment application
- Users
- Salon staff
- Scope
- Entry, overview, editing, archive and daily totals
- Status
- Active private application
- Technology
- PHP 8.3 · MariaDB · PWA
Problem and context
Appointment entry
Salon staff enter an agreed appointment with the details required for the working day. The form keeps the flow short and creates the record without switching between messages and notes.
Schedule overview
Current appointments appear in one list with date, time, service and status. A daily total provides a quick view of scheduled work.
Editing and completion
An existing appointment can be opened, edited and moved to the appropriate status. Completed records move to the archive, keeping the active schedule clear.
Outcome
Safe public presentation
Portfolio images were captured from an isolated copy of the original interface using test names and appointments. No real customer data from the private salon was copied or published.
In use
A short walkthrough.
Appointment entry, schedule and archive. All displayed data is for demonstration.
Gallery
A closer look at the project.

FAQ
Frequently asked questions
Is this a public self-service booking system?
The demonstrated product is an internal appointment manager for salon staff. Public booking can be a separate module when it is part of the agreed scope.
Does the application retain completed appointments?
Yes. Completed records move to an archive and remain available through the relevant view.
Do the images contain real customers?
No. They were captured from an isolated copy of the interface using test data.
Next step
Have a project that needs to work better?
Send me your goal and current situation. I will reply with a concrete scope proposal.
Start a project