Independent concept · Client area, bookings

UMBRAL

A coworking space with two rooms and a client area. The hard part is booking a long meeting when no single room is free the whole time, without asking for anything the space cannot offer.

UMBRAL, desktop view
UMBRAL, mobile view
Type
Client area, bookings
My role
Product design, interface and build
Scope
Marketing site and booking area
Status
Independent concept · fictional brand and data

The challenge

The problem it tries to solve.

Sala Luz (8 people) and Sala Patio (4) do not always have a continuous slot. If the interface only says “unavailable”, people give up or try hour by hour, blind.

The design question: how do you help build a booking from several pieces without losing track of what has been chosen, or what it costs?

Design decisions

Four decisions, in view.

Each one can be checked in the demo.

The two rooms

Present the space with rhythm

The site shows the plan, the two rooms and the rhythm of the day (09:00, 12:00, 16:00) before asking for anything.

Results with availability per room

You can only ask for what is possible

The search disables hours outside opening times (Mon–Fri 08–20, Sat 09–14) and durations that would end after closing, says it is closed on Sundays and caps the group at 8, the real capacity.

“Your selection” panel with the total

Always see what you picked, and its price

“Your selection” shows hours, blocks, room, date, people and the sample total (Sala Luz €30/h, Sala Patio €18/h), with “Confirm booking” and “Clear selection”.

Saved booking with “Add to calendar”

The booking leaves the website

In “My bookings” each booking can be edited, cancelled or added to a calendar with an .ics file. Bookings are stored only in the browser.

What you can try

A four-step walkthrough.

To see the decisions at work, in this order.

  1. Pick a Saturday at 13:00 and see which durations remain.

  2. Combine hours from both rooms in one selection.

  3. Confirm and open “My bookings”.

  4. Add the booking to your calendar.

Behind the interface

Data in the browser

Bookings live only in the browser of whoever tries the demo. There are no accounts or server, and no personal data is collected. Prices are examples.

  • HTML, CSS and JavaScript, no external dependencies.
  • Checked for console errors and horizontal overflow at 1440 and 390 px.
  • Brand, imagery and data are fictional. No figure comes from real users.

With more time

What I would check with people.

These are hypotheses for a test I have not run yet, not results.

  • Can people book a meeting that needs two rooms?
  • Where do they hesitate: in the grid or in the selection panel?

Shall we talk about the role?

I can walk you through how I reached each decision in this concept.