Lido Pro

Commercial operating platform for beach establishments.

LidoPro is a proprietary vertical operating platform for beach establishments. It combines an operator app, protected active Spiaggia layout, parametric Studio, booking and availability engine, customer records, Articoli/catalog pricing, accounts/folios, Registro events, staff, services, customer booking surfaces, and cloud-ready sync/account infrastructure into one connected product.

Gestionale operativo per stabilimenti balneari: Spiaggia, Studio, prenotazioni, clienti, Articoli, conti, Registro, servizi, staff, app cliente, booking web e cloud sync.

LidoPro desktop preview — operator Spiaggia surface, selected place detail, and local booking/account workflow.

Product Overview

LidoPro is designed as a connected operating system for beach establishments. It is not just a beach map: it connects design, daily operations, bookings, customer records, Articoli, folios, Registro events, staff, services, and customer-facing booking surfaces around the active operational layout.

The operator app manages the daily workflow locally and reliably, while the broader platform prepares customer booking, account/sync, cloud backup, AI-assisted setup, and client-facing surfaces around the same operational model.

Studio designs layouts through drafts, previews, verification, and controlled publication. Spiaggia operates the protected active layout. Booking connects customers, availability, period, Articoli/pricing snapshots, Conti/Folio, payments, Registro, dashboard state, and future web/client-facing status.

Cloud / Account / Sync is the planned shared system layer for tenants, accounts, backup, synchronization, APIs, customer booking, storage, and AI gateway. It is not a replacement for the local operational engine.

Usage Modes

Product Areas

Layout and Operations Model

LidoPro separates design work from daily operations. Studio drafts can be edited and reviewed, while Spiaggia remains the protected active operational surface used by staff.

The layout pipeline is:

Studio Project Draft
-> Layout Preview
-> Verification
-> Controlled Publication
-> Active Layout Projection
-> Spiaggia Operational View
-> Booking / Conti / Registro

Studio does not directly mutate operational Spiaggia. Spiaggia consumes the protected activeLayoutProjection, and booking/account flows attach to that active operational layout. Publication is the boundary between design and operation: drafts do not directly mutate customer, reservation, account, or daily workflow data.

Booking Spine

Booking is not a standalone table. It is the operational transaction connecting:

Cliente
-> Booking / Richiesta
-> Disponibilita
-> Posto / Periodo
-> Articoli / Pricing Snapshot
-> Conto / Folio
-> Pagamento
-> Registro
-> Dashboard
-> Web/App cliente

The current implementation includes an evolving domain contract, local-first persistence, availability engine, customer pairing, selected-item operator booking console, lifecycle/change request handling, pricing snapshots, Folio boundary, Registro events, and Booking Inbox. This is not a complete public web booking or client-app runtime yet.

Local-first and Cloud-ready Architecture

LidoPro is designed local-first: the operator app reads and writes locally for reliability on tablet, smartphone, and desktop, including when connectivity is unstable. SQLite/local storage remains the operational engine.

The cloud layer is planned as the system layer for tenant/account, backup, synchronization, APIs, customer booking, storage, multi-device operation, and AI gateway. The product does not require replacing local SQLite with a fully online runtime, and cloud sync is not claimed as live in the current implementation.

AI Integration

AI is planned as an operator-only assistant first. It can prepare booking drafts, customer/import suggestions, Articoli/catalog imports, account/folio draft actions, and Studio layout suggestions.

The rule is: AI proposes, the operator confirms, the system validates, and only then data is written. A local LAN AI adapter and a cloud AI gateway are planned boundaries. AI is not initially exposed to the Client App or Web Booking surfaces, and provider keys must not live inside client mobile apps.

Current Status

Commercial and Repository Status

LidoPro is proprietary commercial software. This repository is public/source-available for transparency, portfolio review, technical review, and evaluation. Repository access does not grant rights to copy, modify, redistribute, host, resell, white-label, deploy, sublicense, or use the application commercially.

Repository access does not provide production deployment rights, commercial use rights, hosted service access, public app-store distribution, sublicensing, or redistribution rights.

Commercial use, pilots, deployments, partnerships, licensing, reseller activity, agency delivery, hosted operation, or customer evaluation require prior written permission.

See LICENSE.md, COMMERCIAL.md, NOTICE.md, TRADEMARK.md, SECURITY.md, and CONTRIBUTING.md.

Runtime Architecture

The product source lives primarily in src/. Tauri and Capacitor are native shells around the same product application, not separate product codebases.

Quick Start

git clone https://github.com/francescomaiomascio/lido-pro.git
cd lido-pro
nvm install
nvm use
npm install
npm run check
npm run build
npm run app:dev

Development Matrix

npm run app:dev is the canonical local development command. It starts one Vite dev server at http://localhost:5173 and opens LidoPro Desktop through Tauri against that same endpoint. VS Code is the primary editor. Tauri is the main desktop runtime. Android tablet validation should use Android Studio or a physical device before closing UI work.

Responsive Quality Gate

UI changes must be checked across desktop, tablet, and smartphone layouts.

Acceptance: no horizontal overflow, no clipped content, no overlapped text, no controls covering critical content, internal panel scrolling, reachable primary actions, usable map/canvas, and verticalized smartphone layouts.

See docs/platform/responsive-device-matrix.md and docs/platform/ui-responsive-checklist.md.

Repository Layout

lido-pro/
  src/          product application source
  src-tauri/    Tauri desktop shell
  android/      Capacitor Android shell
  public/       static and brand assets
  asset-lab/    asset generation pipeline
  docs/         product, platform, repo, commercial docs
  scripts/      local helper scripts

Generated/local folders such as node_modules/, dist/, src-tauri/target/, android/**/build/, local databases, exports, backups, signing material, and release artifacts must not be committed.

Documentation

• Legal/commercial: LICENSE.md, COMMERCIAL.md, NOTICE.md, TRADEMARK.md, SECURITY.md, CONTRIBUTING.md
• Product/brand: docs/product/product-boundary.md, docs/brand/lidopro-naming.md, docs/commercial/README.md
• Repository policy: docs/repo/language-policy.md, docs/repo/
• Platform: docs/platform/
• Architecture/waves: docs/architecture/, docs/waves/, docs/README.md

Repository Hygiene

Do not commit:

• .env files or local secrets
• real customer, booking, account, payment, or business data
• local SQLite databases with real data
• backups or exports with private data
• API keys, signing material, deployment credentials, or payment credentials
• node_modules/, dist/, or native build outputs
• Android, iOS, Tauri, Linux, or desktop release artifacts

Before making the repository public, run the public release checklist and a manual review for real data, secrets, private assets, and misleading product claims.

Troubleshooting

• Wrong Node version: run node -v, then nvm use.
• Missing Rust/Tauri: install Rust, Cargo, and the Tauri prerequisites for the host platform.
• Linux Wayland/WebKitGTK: use npm run app:dev; the repository launcher applies the local WebKitGTK renderer workaround when needed.
• Port 5173 in use: run lsof -i :5173, stop the old process, then restart npm run app:dev.
• Android Studio path: use npm run cap:open:android; it auto-detects common Linux installs. If needed, set CAPACITOR_ANDROID_STUDIO_PATH=/full/path/to/studio.sh.
• Android validation: Android Studio, Android SDK, and an emulator or physical device are required.
• iOS validation: Xcode and Xcode command line tools are required when iOS is intentionally enabled.
• Browser preview: useful for quick layout checks, but it does not validate native WebView, plugin, SQLite/native storage, package permission, signing, or device-specific behavior.

Commercial Contact

Commercial access, licensing, deployment, private pilots, partnerships, and customer evaluation require written permission from Francesco Maiomascio.

Contact details will be provided through authorized commercial channels.