Thank you for being patient! We're working hard on resolving the issue
Lona gives developers a time-shaped model for events, tasks, stickers, formulas, context, and availability.
1 surface for meetings, tasks, context, and availability
0 extra views to read before planning the day
Live availability from the calendar you actually use
The calendar carries the model.
Build on the same calendar your users read — events are real objects, not an opaque feed.
Time-shaped rows are the data model — query the week the way it's displayed.
Create, move, and book through the same actions the app uses, straight from your code.
Build on the surface users see.
Skip the CSV round-trip — the sheet is the live source, not an export that drifts.
What the API writes is what the user sees that instant — no separate sync layer.
Availability and booking ship with the calendar, so you don't rebuild a scheduler.
The value is a week you can read without opening every calendar event, task list, and notes tab.
Start with your real calendar, then add tasks, stickers, rows, availability, formulas, and Spotlight where they help.
Use rows, calendar context, and visual markers as building blocks for calendar logic.