Web · Desktop · Mobile
CliniClic
Multi-client clinic management project with a Symfony web platform, JavaFX desktop application and Java Codename One mobile application.
- Symfony 7.4
- PHP
- Java
- JavaFX
- Codename One
- MySQL
- Doctrine
- JDBC

01
Context
Each client addresses a different part of the clinic domain: advanced clinical workflows on the web, operational administration on desktop and selected user-facing services on mobile.
02
Platform Scope
- Client applications
- 3
- Repository branches
- 3
- Web roles
- 4
- 01Symfony web platform for four roles, appointments, availability, consultations, prescriptions, inventory and events
- 02JavaFX desktop client for users, authentication, appointments, events, complaints and administrative exports
- 03Codename One mobile client for authentication, profiles, events, categories, articles and complaints
03
Three Client Branches
Web
Symfony 7.4
agent/web-symfony-modernization
Desktop
JavaFX · FXML · JDBC
agent-desktop-java-pidev
Mobile
Java · Codename One
agent/mobile-codenameone
04
Multi-Client Experience
The web, desktop and mobile clients expose different workflows while keeping the same CliniClic product identity.

Public experience
1Clinic presentation, services and entry points for account creation and sign-in.

Desktop application
1JavaFX administration client for users, roles, appointments, events, complaints and operational tools.

Mobile application
1Java Codename One client for authentication, profiles, events, categories, articles and complaints.

Administration
6Operational overview, users, appointments, configuration and event publishing.

Doctor workspace
1Role-specific access to appointments, availability and medical workflows.

Patient workspace
1Appointments, medical record entry point, events and profile actions.
05
Interface Evidence
Screens are grouped by client and role so the three applications remain understandable without creating an endless gallery.
Public experience1 screen
Desktop application1 screen
Mobile application1 screen
Administration6 screens
Operational overview, users, appointments, configuration and event publishing. Select an image to view it full size.
Doctor workspace1 screen
06
Technical Approach
- 01Symfony 7.4, Doctrine, Twig and Bootstrap for the web branch
- 02JavaFX/FXML, JDBC and MySQL in the desktop branch
- 03Java 8 source level, Codename One and Symfony API access in the mobile branch
- 04Separate branches preserve each client’s build system and modernization path
07
Engineering Decisions
- 01Kept web, desktop and mobile implementations isolated in dedicated branches.
- 02Enforced medical access, appointment conflicts and availability rules in the Symfony application.
- 03Kept mobile network access behind service classes and the desktop UI organized around FXML controllers and services.
08
Web Demonstration
The recording documents the Symfony web application: registration, patient workspace, role-aware navigation and the public clinic experience.
09
Limitations
- 01Academic demonstration using fictional accounts and data.
- 02The desktop and mobile branches retain legacy Ant-based project structures.
- 03The mobile API contract and role model still need alignment with the modernized Symfony backend.
10




