back to all use cases

reformer social club.

a pilates studio needed one place for its classes, credits and agenda.

a dark grey bar with seven round hollows on light paper. black balls sit in the first three; a small red ball waits next to the fourth.

the problem.

who
a pilates studio in ericeira.
what was needed
some classes run on a fixed timetable. others only run if enough people sign up. the studio needed both in one place.

how we thought about it.

  1. one admin for every kind of class.

    because the studio needed one place for its classes.

from sketch to screen.

  1. sketchthe studio's week, on paper.
  2. measureeach screen sized for the studio's desk and the client's phone.
  3. wireframethe admin and the phone view, in grey.
  4. screenthe final screens, built around the studio's own schedule.

what we built.

the studio
one admin for fixed and open classes, with who is signed up for each.
clients
they book on the phone, with credits that expire.
instructors
their agenda, on the phone.
one class and its signed-up students, in portuguese: six of eight places taken, each one confirmed.
real screens in portuguese, fictional data. one class and who is signed up.
the admin's fixed schedules, in portuguese: a table of classes with date, instructor and how many places are taken.
the admin: each class with its date, instructor and places taken.
the client's view of an open class: three signed up, one more needed to confirm.
the admin's open classes, in portuguese: each runs once four people sign up.
the same class, in the admin's list and on the client's phone.
a loop of the admin and the client's phone. no sound.

status.

what
software
status
built

the studio runs its classes from it.

see how we work. see all use cases.

have something like this? tell us.

sending a message doesn't commit you to anything.

send us a message.

next use case

agent-lab.