Calendar sets - For mobile

Morgen needs to hire a UX developer with a background in phycology, not another UI/FrontEnd developer.

I am a paying user since last spring. I still cannot make Morgen my daily calendar, and Fantastical still is. Calendar sets are the blocker, and I only learned they existed by finding a feature request board post. I want to be precise, because I do not think this is one missing feature. I think it is one wrong decision that has cascaded.

There is no set object

Per the official guide, you create a set by clicking the "No set" label on an individual calendar and choosing numbers. Membership is an integer tag applied from the calendar's side. There is nowhere that a set exists as a thing you create, name, or inspect.

Everything below follows from that one choice:

• Sets cannot be named, because there is no entity to name. They are 0 through 9, and nothing tells me whether I am looking at Work, Personal, or Family.

• The 10 set limit is not a decision about how many contexts a person has. It is the number of digits on a keyboard row.

• Switching is keyboard only, because the number key is not a shortcut to the feature. It is the feature.

• Pressing a number before anything is configured does nothing, with no feedback. A new user concludes it is broken rather than empty. That happened to me.

Morgen's own copy confirms the framing. The homepage sells this as "customizable calendar shortcuts." The guide is tagged #shortcuts and offers to help me "create shortcuts." The feature is named after its accelerator rather than the thing it organizes.

Discoverability: the feature exists in only one of two places that show calendars

Set assignment lives exclusively in the popover behind the small calendar icon in the toolbar. Edit Preferences also lists my calendars, in a larger and more thorough view, and there is no way to assign sets there at all.

That is the reason I could not find this. I looked in preferences. I looked in system settings. Nothing. I had to watch a video to learn that a toolbar icon, which does not even display the current date, is the one and only entry point. Then I had to infer that the numbers were keyboard shortcuts, and that pressing a number key would change the view. If a feature is reachable from a compact icon menu, it should also be reachable from the full preferences surface. Right now the shortcut path is the only path.

What I can see in my own calendar list, as evidence

I have roughly 30 calendars across an Outlook and a Google account. Screenshots attached.

Sets silently omit calendars, and it is already happening to me. A national holidays calendar, a colleague's work schedule, a shared planning calendar, and about a dozen others are checked and visible right now, and tagged "No set." The instant I press any number key, every one of them disappears. There is no state in which they coexist with a set. The guide's answer is to manually assign every calendar to 0 to construct an "all" view, which means the default is a view that quietly drops events and any calendar I connect later falls out of it with no warning. In a calendar app, a view that silently omits events is worse than one that fails loudly.

Two independent visibility systems share one row. The checkbox controls what is displayed right now. The number controls set membership. Both govern visibility, they interact, and neither explains the other. One of my calendars is unchecked and tagged 9. Is it in set 9 or not? The interface cannot answer that, and neither can I.

Membership is only ever shown per calendar, never per set. To answer "what is in set 2," I scan every row across both accounts and assemble the answer in my head. One calendar displays its membership as "1 9," two tags rendered as a space separated string. Between the two accounts I have two calendars with identical names, two more whose names differ by a single word, and two holiday calendars whose names use the same words in a different order. Verifying a set by eye is not realistic. There is no way to confirm I did not forget one.

The reference implementation

Dan pointed at Fantastical three years ago and it is still the answer. Sets are objects in a list. You create one with a + button and give it a name. The active set name is displayed in the window and clicking it switches. "All Calendars" ships as a default rather than something you assemble by hand. Selecting a set shows its calendars, so you can verify accuracy. Keyboard shortcuts sit on top for people who want them, Control-1 and up. On iOS the current set name is at the bottom of the screen and you tap it to switch.

Notice what that means for this request: mobile parity is not the hard part. Once a set is a named object with a visible active state, the phone UI is a label and a tap. It is hard in Morgen because there is nothing to put in the label.

Asks

1. Make sets first class named objects, created and managed in one place.

2. Show the active set name persistently in the main view, and make clicking it the switcher.

3. Add a per-set view: select a set, see exactly which calendars belong to it.

4. Ship a real "All calendars" default that automatically includes newly connected calendars.

5. Expose set management in Edit Preferences, not only in the toolbar popover.

6. Reconcile the checkbox and the set tag, or make their relationship explicit in the UI.

7. Keep the number keys as an accelerator on top of all of that, not as the only door.

Why I am writing this much

I was roughly 80 percent through the tutorial video before the model clicked, because I was pressing keys as instructed and nothing was happening. The video linked in the mobile feature request thread is also not the one embedded on the current guide page.

I paid for Morgen because of where it is going, and Kai is genuinely interesting. But an AI executive assistant sitting on top of a calendar I cannot organize is worth nothing to me. The basics gate everything above them, and good tools that are poorly communicated do not get used. I would rather see the object model fixed on desktop than see the current model faithfully reproduced on a second platform.