01 / Property operations · Mobile
RoomQu
A connected workflow for rooms, guests and operations teams.
Connects Host, Front Office, House Keeping and Technician roles so unit status and handoffs are easier to follow. Designed for mobile use.
01 / CONTEXT
Why I built it
Property operations involve constant handoffs: a room becomes available, a guest arrives, cleaning is needed and an issue needs attention. I built RoomQu to explore how an application can connect those tasks through clear roles and responsibilities.
What it does
- Four role-based workspaces.
- Daily or hourly check-in, check-out and unit status tracking.
- Cleaning documentation, Host approval and technician issue reports.
- Staff, agent and unit management, attendance and Excel export.
Strengths
- Cross-role workflows connect to original business handlers and database schema.
- A mobile-first approach keeps core tasks accessible on smaller screens.
- The PGlite file demo preserves data across restarts.
Current limitations
- Tauri packaging is planned, not implemented.
- External PostgreSQL, live Cloudinary and production load remain unverified.
- The approved new frontend does not yet reproduce every legacy UI feature.
02 / PROCESS
Challenges & lessons
The key challenge was keeping permissions, booking times and unit status consistent. Testing exposed a timezone mismatch that made hourly bookings appear available immediately. Timestamp comparisons were corrected and retested so the unit stays occupied for the booked duration.
Evidence & demo status
52 HTTP integration checks passed. Svelte checks and build succeeded. Browser check-in saved to the original backend, with data persisting after restart. These screenshots show the latest integrated mobile UI with dummy data.
03 / DOCUMENTATION
Inside the application
What comes next
Prepare Tauri packaging, improve feature parity and validate deployment and external integrations.
Contribution & process +
I independently developed the original application, from its logic to its interface. Codex assisted with recent refinements, testing and portfolio demo preparation. Documentation uses sample data. The initial mobile UI is backed up. With my approval, Codex helped implement the current frontend and integration adapters while retaining original business handlers and schema.