App · Bookings and scheduling
Studio Bookings
The app from the Appbricx tutorial. Members sign up, pick a day and book a class; a rule refuses a full class. Instructors get a desk with tomorrow's rosters, check-in and a chart of mats booked, plus a morning digest. It also shows a server function calling a weather API and an AI class finder.
Members sign up and book. Instructors run the schedule.
What's inside
Weekly schedule with one-tap booking. My classes with cancel. Instructor desk with rosters, check-in and a bookings chart.
Tables
membername, email, goalsinstructorname, bio, photosessiontitle, style, level, instructor_id, starts_at, duration_min, capacity, booked, …bookingmember_id, session_id, status, note
Roles
memberMember, consumerinstructorInstructor, staff
Pages
/scheduleSchedule (member)/my-classesMy classes (member)/deskDesk (instructor)/classesClasses (instructor)/bookingsBookings (instructor)/membersMembers (instructor)/teachersTeachers (instructor)/teamTeam (instructor)
Workflows
count-bookingCount the mat and tell instructors. On booking createdfree-mat-on-cancelFree the mat when a booking is cancelled. On booking updatedmorning-digestMorning bookings digest. On schedule daily 07:00 over bookingclass-forecastWeather for a garden class. On server function (member, instructor)
Components
ClassScheduleMember schedule: pick a day, book a class, AI class finder, garden-class forecastMyBookingsA member's upcoming classes with cancel, and their historyStudioDeskInstructor desk: next day's rosters with check-in, and a chart of mats booked
Rules on every write
sessionClasses run 15 to 180 minutes for 1 to 30 people.bookingThat class is full. Try another time.
Use with your coding agent
- Connect the Appbricx MCP server to Claude Code, Cursor or any MCP client (quickstart).
- Paste the prompt. The agent creates the project and builds it.
- It applies to dev. Check it, then deploy when you are happy.
Start a new Appbricx project from the Studio Bookings template (slug "studio-bookings") with use_template. Call it "My Studio Bookings", then sign in as each role, verify it and tell me what to change first.{
"tool": "use_template",
"arguments": {
"slug": "studio-bookings",
"name": "My Studio Bookings"
}
}appbricx templates use studio-bookings --name "My Studio Bookings"Screens
Goes well with
Booking calendar
Block. Bookable time slots with capacity, a day picker, my bookings with cancel, and rules that stop double-booking.
slotreservationSlotPickerMyReservationsreservation-countBooking confirmation and reminder
Workflow. Emails a confirmation when a booking is made and a reminder the day before it starts.
‹booking›.reminder_sent_atbooking-confirmationbooking-reminderTablefor
App. Restaurant reservations with a host floor plan and a live kitchen board.
guesthostchefdishopening_hour