Wandering Devs
Selected studio work / Product case study
Studio case study

Pool Boy

Pool Boy is a separate product from Wandering Interest, built from the day-to-day work of a pool service business. It is an example of designing software around a field workflow rather than a list of features.

Pool Boy website from the original project gallery
Pool Boy website from the original project gallery
Scope

Independent product · Web and Android · Separate Pool Boy brand

What went into it

Background · decisions · delivery
The context

A scheduled service stop, an open repair, and the customer’s history have to stay connected without becoming interchangeable. That distinction drives the app’s structure: what shows up on a route, what a technician records at a visit, and what stays open until a repair is resolved.

Design from the route outward

Start with a technician’s day. They need a list of stops, a way to get to the right pool, and the background for the visit. A repair needs its own owner, status, and completion path instead of disappearing into a service note.

Make conversational actions inspectable

The assistant can create and update service tickets. The product design question is how to get from a short request to an actual record without confusing a generated answer with a completed action. The useful demo ends with the ticket visible in the app.

A standalone product with a separate launch

The portfolio capture shows earlier product branding. It’s an archive image, not a representation of the current release. The Pool Boy site owns the feature, availability, and signup information.

Have something similar in mind?