01Platform reach
Three destinations
One product serves web, iOS, and Android customers.
Founder product evidence
Washday
A mobile-first website platform for laundry businesses went from concept through design, cross-platform implementation, custom backend, and app-store launch.
A complete cross-platform product shipped with Svelte, Capacitor, and a custom Node.js backend.
Situation and responsibility
What was at stake
Laundry businesses need a credible mobile presence but often cannot justify separate web, iOS, and Android product teams.
Washday explored how one focused system could give these businesses a mobile-first site and app presence without creating three disconnected products.
- Evidence
- Founder-owned product
- Platforms
- Web, iOS, and Android
- Stack
- Svelte, Capacitor, and Node.js
- Responsibility
- Concept, design, development, backend, and launch
Diana’s responsibility
- Defined the product and customer scope
- Designed a mobile-first experience
- Built the cross-platform application
- Created the custom backend and shipped to app stores
Important decisions
Judgment made visible
Each response follows from an observed condition. The last column marks the tempting shortcut the work needed to avoid.
| What you notice | What it may mean | A useful response | What to resist |
|---|---|---|---|
| Customers expected web and mobile access. | Separate native builds would add cost without adding product value. | Use one Svelte experience with Capacitor for app distribution. | Do not let platform packaging fragment the interface. |
| Laundry businesses share a category but differ operationally. | The product needed a focused core with configurable presentation. | Separate the reusable platform from business-specific content. | Do not encode one operator's workflow as universal. |
Decisions and delivery
How the work moved
- 01
Define the useful core
Focus the product on the mobile presence a laundry business needs to launch.
- 02
Build once across platforms
Use Svelte and Capacitor with a custom Node.js backend.
- 03
Ship the product
Carry the experience through web delivery and both app stores.
Working through a similar constraint?
Describe the problem →Visual evidence
The product in view
This project has one approved image in the archive. It is shown at full scale without implying a larger undocumented gallery.
Supported outcomes
What the evidence supports
Quantitative claims appear only where the repository provides them. The remaining outcomes are explicitly qualitative, operational, or statements of responsibility.
02Responsibility
End-to-end ownership
Concept, UX, software, backend, and launch stayed connected.
03Product model
Reusable foundation
The platform was designed for a category of service businesses rather than one bespoke site.
Bring me the version that is hard to explain.
If your product needs to reach customers across web and mobile without multiplying the work, describe the core experience.
Describe a similar problem →