Scobe ecosystem · Windows application

A Windows application for appointment management.

A local-first Windows product that brings appointment and business workflows to service businesses without a website.

Scobe Desktop Windows application showing a demo salon’s service catalog and business navigation.
Scobe Desktop · Services Center · existing demo screenshot. Service prices are demonstration data.

The operational problem

Not every salon, clinic or studio wants to maintain a website just to manage daily operations. A desktop product needs to be installable, keep business data local and provide a practical recovery path.

Scobe Desktop packages the Scobe workflow into a Windows application with local data storage, built-in backup and restore, and managed software updates.

What the product does

  • Appointment, customer, staff, service and package workflows powered by Booking Pro.
  • Local business data and built-in backup/restore, including a replacement-computer path.
  • A Windows application designed around a single computer.
  1. 01
    Windows shellApplication lifecycle
  2. 02
    Local runtimeBooking Pro + WordPress
  3. 03
    Business dataLocal storage + backups

Engineering decisions

Reuse the product, own the lifecycle

A Rust/Tauri shell supervises a bundled PHP, MariaDB and WordPress runtime. The existing business application stays consistent while the shell handles the desktop lifecycle.

Separate data from replaceable software

Business data lives separately from the runtime’s replaceable slots. Updating application code and preserving the salon’s records are different responsibilities.

Design for interrupted updates

Release work includes installer/runtime compatibility, package verification and rollback paths. Boot and adoption checks account for incomplete or invalid staged updates.

Reliability and maintenance

  • Signed manifests and package integrity checks before applying updates.
  • Backup, restore, replacement-PC and upgrade smoke coverage.
  • Release gates and regression cases for runtime adoption and startup behavior.

Testing and delivery

The release workflow distinguishes the Windows installer from runtime updates. Rust tests, PowerShell release checks and Playwright regressions cover different parts of the customer journey, with retained rollback artifacts and documented release procedures.

Next case study / 03

Scobe License Server

Continue exploring

05Contact

Get in touch

For questions about my work or to discuss a project, you can reach me by email.

ozgurbariserol34@gmail.com

github.com/ozgurbariserol