The Problem
Beauty salons and spas run on appointments, staff scheduling, inventory, and payments, yet most management software is either expensive or too generic. BeautySmart targets that gap: a free, self-hosted system for appointment booking, staff commissions, cabin occupation, loyalty points, and point-of-sale operations. The repository is an early-stage Laravel application that sketches this vision but has not delivered most of the promised functionality.
What This Does
BeautySmart is a Laravel 5.x application with a standard MVC scaffold. The custom code lives in app/Http/Controllers/ — AppBeautySmartController.php, CustomersController.php, and ProductsController.php — alongside Blade views under resources/views/BeautySmart/ (index.blade.php, Customers/index.blade.php, Products/index.blade.php). Routes are defined in routes/web.php and routes/api.php.
The README lists roughly 25 intended features (bookable appointments, reminders, staff commissions, cabin management, stock, loyalty points, POS). The actual codebase contains only customer and product listing views and controllers. There are no migrations, models, or database schemas in the repository — the entire data layer is absent. The bundled vendor/ directory (129 files) is standard Laravel framework code, not application logic.
How To Use It
The repository is not currently runnable as a functional application. Setup: composer install would restore dependencies, but no package.json build step is configured for frontend assets beyond the default Laravel scaffold. Configuration: Copy .env.example to .env and set database credentials. No migrations exist, so a fresh database would have no tables. Running it: php artisan serve would start Laravel, but the only functional pages are the default welcome screen and the two index views that render without data.
composer install cp .env.example .env php artisan key:generate php artisan serve
Real-World Use
A salon operator would expect to open the app and see today's appointments, staff schedules, and cabin occupancy. In the current state, the app renders empty customer and product index pages. The intended workflow — a customer books a service, the system assigns a staff member, tracks the commission, and records payment — has no backend implementation. This is a design document with a Laravel shell, not a deployable product.
Code Health & Issues
High — No data layer: No migrations, models, or seeders exist. The application cannot store or retrieve any data. High — Committed dependencies: vendor/ (129 files) is checked into the repository. It should be gitignored and installed via Composer. Med — No CI/CD: No .github/ workflows, Travis config, or build pipeline. Tests exist (tests/Feature/ExampleTest.php, tests/Unit/ExampleTest.php) but are the default Laravel stubs. Med — No license: The README has no license section. The default Laravel MIT license text is present but applies to the framework, not this project. Med — Debug artifact: info.php at the root is a PHP info dump — a security risk if deployed to a public server. Low — Stale scaffold: The README retains the default Laravel template text, and the composer dependencies are consistent with Laravel 5.5-era, now several major versions behind.
The Bottom Line
BeautySmart is an idea with a Laravel skeleton, not a working application. The feature list in the README is ambitious, but the codebase delivers only two empty index pages and no data layer. It is not suitable for any production use; it could serve as a starting point for a developer who wants to build the salon management system from scratch, but there is little here to salvage beyond the controller/view naming conventions.