So I've been thinking about how to organize Sync's interface. Because having all these core components is one thing—but how do you actually navigate through them? What do you see when you log in? Where do you click to get things done?
I keep looking at how other tools do this. Fullres has a clean structure: accounts, then sites under each account, with everything else flowing from there. Cal.com organizes around event types, bookings, availability. Simple. Logical.
For Sync, it needs to be even simpler.
The account structure
Like most tools, you create an account with an email. You pay—there's just one pricing level, no free tier. Maybe a 7-14 day trial, but then you pay whatever the amount is.
You get a default Profile. Everything starts there.
Think of Profiles like Fullres's Sites—they're your “organizational unit.” Most solo professionals will just use the default Profile. But if you're a consultant who also teaches yoga on weekends, you might want separate availability Profiles. Different rules for different types of work.
Main navigation: four things
After studying what works, I think the main nav should be dead simple:
Home—Your dashboard. The unified view that shows what's coming up and what needs your attention.
Calendar—Your unified timeline. All events from all connected calendars, merged into one view. This is where the Schedule view component lives—showing conflicts, highlighting issues, letting you see the big picture.
Availability—Where you define and manage your bookable slots. This is the Availability manager and Availability grid working together. Drag to create slots, toggle things on and off, set blackout periods.
Settings—Everything else. Your profile settings, connected calendars, booking tool integrations, notification preferences.
That's it. Four things.
The persistent "New" button
At the top of every page, there's a "New" button. Always there. Always accessible.
From that button, you can:
Add a new calendar connector (Google, Apple, Outlook)
Add a new booking tool connector (Cal.com, Calendly, whatever)
Add a new availability slot
Add a new profile (if you need one)
The idea is you should never hunt for how to connect something new. It's always right there.
What happens in each section
Home pulls from the Schedule view component. Your upcoming events from all calendars. Any conflicts that need resolution. Quick actions for the most common tasks. If you haven't connected anything yet, this is where the Onboarding wizard kicks in.
Calendar is your unified timeline. The Schedule view component in full. Everything from everywhere, merged intelligently. You can see where events came from—whether someone booked through Cal.com or sent you a Teams invite. The Sync engine keeps it all in harmony.
Availability combines the Availability manager and Availability grid. You define your bookable windows here. Set recurrence rules. Create blackout periods. The Availability manager publishes these changes to all your connected booking tools automatically.
Settings is where the Calendar connectors, Booking-tool connectors, and Settings & preferences components live. Connect your Google Calendar. Integrate with Calendly. Set your notification preferences. Manage your conflict resolution rules.
The invisible parts
Some components work behind the scenes. The Sync engine is always listening, always reconciling. The Conflict alerts pop up when they need to. The Notification service sends you updates. The Data store keeps everything persistent.
You don't navigate to these—they just work.
Keeping it simple
I keep coming back to this: Sync isn't trying to be your calendar. It's not trying to be your booking tool. It's trying to keep them in sync.
So the navigation should reflect that. Show you what you need to see. Let you manage what you need to manage. But don't try to replace what already works.
Four main sections. One persistent action button. Everything else happens automatically.
That feels right. That feels like something people could actually use without thinking about it.
Simple. Focused. Useful.
The way navigation should be.