Rebuilding the Wix Bookings Mobile Calendar
Transforming a high-traffic surface into a clear, scalable scheduling system
Wix · Wix Bookings · Senior Product Designer · 2025
Overview
The Opportunity
The calendar is one of the most critical surfaces in Wix Bookings.
It is used constantly by business owners to manage availability, coordinate appointments, and make real-time decisions, often while actively working with clients.
Despite its central role, the experience no longer supported the complexity of real-world usage.
As usage scaled, gaps in clarity, performance, and usability became more visible, creating friction in high-frequency, time-sensitive workflows where mistakes have immediate impact.
Improving the calendar was not just a UX refinement.
It was a core product investment in how businesses operate day to day
About Wix Bookings
Wix Bookings is a core operational tool for service-based businesses,
allowing them to manage appointments, staff availability, and client information.
The calendar is the main interface where this work happens.
It is where businesses actually run their day.
My Role
I led the redesign of the Wix Bookings mobile calendar from early discovery through implementation.
I worked closely with the Product Manager to define the problem, shape the product direction, and align on priorities throughout the process.
I led the UX work end-to-end, from identifying structural issues to defining the concept, interaction model, and system behavior.
I collaborated closely with engineering and the Mobile Design System, driving alignment, presenting the concept, and negotiating scope.
The problem
From early on, it was clear that the calendar experience was not aligned with how users actually work.
This was not about missing features.
The system did not support real usage patterns.
Switching between views caused disorientation.
The same information behaved differently across contexts.
Dense schedules were difficult to scan.
As a result, instead of supporting fast decisions,
the calendar introduced friction at critical moments.
Users don’t open the calendar to explore.
They open it with a specific question, usually under time pressure.
For example, a salon manager checking availability while a client is already seated
needs to understand within seconds where the next appointment can fit.
In this context, even small friction becomes operational.
This gap was consistently reflected in user feedback:
Understanding the system
To understand the problem deeply, I broke down the calendar into its core components.
I mapped how the system behaves across different views such as day, week, and agenda, focusing on how time is represented, how dense schedules are handled, and how users move between contexts.
I explored edge cases, such as overlapping sessions within limited space, to identify where the experience breaks under real-world conditions.
In parallel, I spoke with users and reviewed competing products to understand how more mature systems handle density and support fast decision-making.
This revealed a fundamental gap.
The calendar was designed as a static representation of time,
while in practice, it needed to function as a decision-making tool under pressure.
Key Insight & Direction
The research revealed a gap between the existing experience and the expectations set by mature calendar systems.
Compared to these products, the calendar lacked clarity, predictability, and efficient scanning patterns.
Users struggled to quickly understand availability, especially in dense scheduling scenarios.
At its core, the problem was structural.
The calendar lacked a consistent mental model.
The same information behaved differently across views, forcing users to constantly re-interpret what they were seeing.
This led to a clear design direction:
The experience needed to be rebuilt around a single, consistent logic that enables fast understanding across all contexts.
In other words, the calendar should not be interpreted.
It should be immediately understood.
Defining the concept
Based on these findings, I took a structural approach, redefining how the calendar works as a system.
Instead of improving individual features, I focused on creating a consistent logic across all views.
Time is represented the same way regardless of context, allowing users to rely on a single mental model.
This directly addressed the core issues.
It reduced disorientation, improved scalability, and enabled faster understanding of availability under time pressure.
I validated this approach through usability testing with experienced users.
Users were able to move between views more intuitively, quickly understand availability, and maintain orientation across contexts.
This confirmed that a consistent system structure significantly reduces cognitive load in high-frequency workflows.
Functionality change:
date selection moved to a dropdown to reduce clutter and free up space
Layout change:
fixed dates for clear time orientation
Time slots are now displayed as clear, structured cards for quicker scanning and improved readability.
The header is clean and consistent across all tabs.
3 days view
Weekly view
Staff view
Scope & alignment
To bring the concept into execution, I worked closely with the Product Manager to define requirements and align on the initial direction.
I translated the concept into a clear product vision and led alignment across key stakeholders, including Bookings mobile engineering, the Mobile Design System team, and leadership.
From there, I helped define ownership and scope across teams, setting the foundation for execution.
Defining scope required continuous prioritization, balancing engineering capacity with system constraints.
I focused on prioritizing what defines the core experience over features that enhance it, ensuring we addressed the fundamental usability issues first.
A key decision point was defining what must be included in phase one.
I strongly advocated for including both Staff View and Weekly View, as they are essential for real-world scheduling workflows and expected industry standards.
Without these views, the system would not support how users actually work.
This required clear trade-offs.
Features like calendar zoom were deprioritized, despite their value, due to higher implementation complexity and lower impact on core usability.
This ensured we built a strong foundation, enabling the system to scale effectively rather than layering features on top of a broken structure.
Solving complexity
Defining a scalable system
Designing the new calendar required handling complex scenarios within the constraints of a mobile interface, especially displaying dense information without losing hierarchy.
I approached this by defining the calendar as a complete system, covering all views, states, and behaviors end-to-end.
This included mapping list, day, three-day, week, and staff views, and defining consistent slot behavior across durations and states.
Defining this upfront ensured consistency and prevented fragmentation as the product evolved.
Handlin dense & complex scenarios
Dense scheduling was one of the main challenges.
Displaying everything created visual overload, while simplifying too much risked hiding critical information.
I defined a structured way to group and represent sessions, allowing users to quickly understand availability without overwhelming the interface.
Interactions transition users from aggregated views into more detailed views, where information becomes clearer and actionable.
Because zoom was not included in phase one, the solution had to work effectively without relying on it, making these trade-offs critical.
Collaborating with design system
This work was developed in close collaboration with the Mobile Design System.
A key tension point was how to use color in the agenda view.
I initially pushed for full background color to maintain consistency across views, but this created scalability and density issues.
Through iteration, it became clear that enforcing the same pattern across all contexts introduced more friction than clarity.
We shifted to a more refined approach, using color as a subtle side indicator, allowing the system to scale while maintaining clarity.
Summary
This project transformed the calendar from a fragmented experience into a consistent and scalable system.
By redefining structure, behavior, and interactions across views, the new design supports faster decision-making, reduces cognitive load, and aligns with industry standards.
The result is a calendar that is easier to scan, more predictable to use, and better suited for real-world scheduling workflows.
Early signals indicated improved clarity and faster interaction in high-frequency use cases.
Adoption
+4.6K
sites adopted Owner Checkout to complete transactions after appointments
Orders
+48K
orders were completed through the Owner Checkout flow
Transaction Volume
+$5M
More than $5M in transaction volume was processed through the checkout experience.
Online Payments
$1.2M
In online payments were processed through the checkout flow, indicating increased usage of owner initiated payments inside Wix.
Checkout Conversion
62%
Of checkout sessions resulted in a successful payment.
Funnel analysis showed strong completion rates across steps:
72% continued to payment
96% selected a payment method
91% completed payment
Reflections
This project showed that the challenge was not improving the calendar, but redefining how it should function as a system.
The key shift was moving from isolated feature improvements to designing a consistent structure across all views.
It reinforced that consistency is not about visual uniformity, but about creating a predictable mental model that enables fast understanding.
It also highlighted that scaling a product requires tradeoffs.
Not every pattern can be applied universally, and knowing when to adapt or let go of a direction is critical.
Ultimately, designing for complex systems means making the right things simple, not making everything simple.