Client deployment

Appointment booking and automatic reminders for a salon

A phone app keeps the client database and sends a reminder an hour before the appointment. It also works after the device restarts and needs no separate server.

Client
Hair and beauty salon
Duration
MVP in a few days
Illustration of the app · sample data

Before

  • Appointments tracked by hand (notebook / memory)
  • No automatic reminders → no-show risk
  • Client data scattered
  • Reminding = manual phone calls, time-consuming

After

  • Client database on the phone (name, phone, e-mail)
  • Automatic e-mail one hour before the appointment
  • Configurable message content and sending account
  • Ready APK + guide + full source code

Source code (GitHub) → Download APK ↓

Starting point

A beauty salon needed a simple tool to keep a client database and remind people about their appointments. Until then, appointments were tracked by hand and reminders — if sent at all — went out manually. Easy to slip up, and easy to lose a client to a no-show who simply forgot.

Goal

A lightweight phone app that does one thing well:

  • client database: name, phone, e-mail,
  • appointment scheduling: client, date, time,
  • automatic e-mail reminder one hour before the appointment.

Solution

I built a native Android app (Kotlin), deliberately minimal — so it's reliable and free to run.

1. Data stored locally in SQLite

Clients and appointments are kept locally in SQLite (a repository layer over SQLiteOpenHelper). No cloud, no subscription — the data stays on the device, which simplifies GDPR and zeroes out fixed costs.

2. Background reminders (WorkManager)

Each appointment schedules a WorkManager job that fires one hour before the time. Jobs survive a phone reboot and run even when the app is closed. I also added a "send now" action to demonstrate the mechanism without waiting an hour.

3. E-mail delivery over SMTP

Notifications go out by e-mail (SMTP, JavaMail) — a free, dependable channel for a salon's client base. The sending account is entered on a settings screen, with no credentials hard-coded. The message body is configurable, with {imie}, {data}, {godzina} placeholders.

4. SMS hook left in the code

I left a prepared spot in the code for future SMS delivery through a gateway (with instructions), so extending it is a matter of plugging in a paid account rather than rebuilding the app.

Result

The client received a ready-to-install APK, a short guide, and the source code. The app keeps a client database and sends reminders on its own, one hour before each appointment — no server, no subscription, on a single phone. Tested on a set of contacts, with reminder delivery confirmed.

Takeaways

For most salons an off-the-shelf booking system is the sensible choice — and that's usually what I'd recommend. This brief was different: a small, self-contained app doing one specific thing, with the full source in the client's hands. The value isn't scale — it's clean execution: local data, reliable background jobs, and no secrets in the code.

Technologies in this project

KotlinAndroidSQLiteWorkManagerSMTP

A similar situation at your company?

Call and tell me what has to work.

You do not need to know the technical terms. The first conversation is free — I will tell you where I would start.

Before you pay, you see how it will work.

A free demo: a working demo, a mock-up, a cost calculation or a repair plan. Then a fixed price in writing and a warranty of at least 30 days on every stage.

If I don’t pick up, I call back the same business day.

← All case studies