№ 010 · Case study

Washlava.

The only laundry technology that let residents reserve and pay for machines from a smartphone. Vermillion designed and built the complete platform stack: consumer iOS and Android apps, the property manager dashboard, and the IoT integration layer that connected the physical machines to the apps.

IoTPropTechiOS and AndroidSmart laundry
Book a 15-min Strategy Call

15 minutes. No pitch.

Washlava product

Multi-year IoT deployment

iOS, Android, dashboard, IoT

Profitable operation

Wound down by operator (2024)

The challenge.

Shared laundry was still tuned to coins, guesswork on availability, and trips to the basement with no signal on wait time.

Operators needed fewer truck rolls, clearer revenue, and a resident experience that matched how other building amenities already ran on software.

Washlava needed consumer apps, an operator layer, and machine connectivity that could survive real laundry rooms, not demos.

Our approach.

Product stack

Consumer apps, property dashboards, and the integration layer to machine state and payments, designed as one system instead of three disconnected releases.

IoT integration

Sensors and controllers for live machine status, session boundaries residents could trust, and operator alerts that pointed to a specific asset.

Operational reliability

Infrastructure and release discipline matched to a national footprint: isolation of bad devices, staged rollouts, and observability operators could act on.

Multi-platform delivery

iOS, Android, and web simultaneously so residents and staff could each use the right surface.

The solution.

Mobile reservations and payments

Availability, booking, and contactless payment paths tuned for intermittent connectivity in basements and breezeways.

Washlava mobile experience

Property operations

Web tools for revenue, maintenance signals, and portfolio visibility so a manager could see past a single laundry room.

Machine connectivity

Real-time status, remote start where supported, and service hooks so vendors could reconcile physical visits with what the cloud already knew.

Technology

iOS (Swift)

Native mobile

Android (Java)

Native mobile

JavaScript

Web platform

Node.js

Backend API

Docker

Containers

Kubernetes

Orchestration

Results.

Operational scale

Operated profitably across deployed locations. Multi-year embedded engagement. Consumer iOS and Android apps shipped continuously. Property manager dashboard and IoT layer ran as the operational backbone of the platform.

Field discipline

The stack survived real laundry rooms, not just lab benches: long-running sessions, vendor variance, and staff turnover at properties.

Status

Platform wound down by the operator in 2024 after years of profitable operation across deployed locations.

Next case

Group Home App