SteamIt Cy turns a location-based car-wash service into a connected mobile operation. Customers select where the service is required, register their vehicles, choose services priced for the vehicle class, and complete the booking through the application while the operational team manages routing and delivery through a responsive backoffice.
Product teamwork from concept to delivery
Panayiotis Hiripis produced the initial product and solution design. Renos Hiripis implemented the mobile and backend systems, refined and polished the interface and workflows, tested the integrated platform, and carried the project through delivery. Both remained involved in the decisions that shaped the finished product.
Customer booking experience
Location-based booking
Customers pinpoint or search for the service address through a map-driven flow.
Vehicle-aware pricing
Available wash and detailing services are calculated according to vehicle classification and service tier.
Multiple vehicles and plans
The product supports multiple registered cars, flexible service combinations, and membership-style offerings.
Embedded checkout
Stripe card payment is completed inside the Flutter screens without an external web redirect.
Registration and communication
- Phone-number registration using Firebase OTP verification
- Email registration with a six-digit verification message
- Sign in with Apple and Google
- Google Maps location services
- Firebase notifications for booking and order updates
- Multi-language application text managed from the backoffice
Operational backoffice
A Laravel and PostgreSQL backoffice manages service definitions, vehicle classes, pricing, customer orders, driver assignment, routing, and administration. The backoffice is mobile-responsive and can receive real-time web notifications when a new booking is created or its operational assignment changes.
Current delivery note: Official iOS and Android listings remain available. The newer major-generation functionality described here has continued through a stress-testing period, so the public store builds may not yet represent every newer workflow or behave exactly like the current test build.
