A briefing you can touch
Every morning at six, the app drops a summary of the day into the inbox: “you have three events today”, then the list, in time order. Until 18 May that summary could be read, or listened to, and that was the end of it. Since then, tapping it opens the card of the first appointment. The same day, the month view of the calendar learned to show the selected day under the grid instead of jumping somewhere else, and an event tapped in the calendar now opens the same card it opens everywhere else. Three gestures, one rule: text that names a thing should lead to that thing.
Six in the morning, one line per appointment
By then the inbox had existed for a little over a week. It collects what the app has to say when you are not talking to it: a reminder that has come due, an event about to start, and a daily briefing, prepared every morning at six by a background job. The briefing is a few lines long. A heading that counts the day's events, then one line per event with its time and, when there is one, its place, sorted from the nearest to the furthest.
It is a good thing to find when you wake up. You open the inbox, you read it, or you ask the app to read it out loud, and you know what the day looks like. The summary does exactly what a summary is for.
The flaw showed up in use, and it is an ordinary one. You read “dentist at a quarter past nine”, you want to check the address, or reread what you noted when you booked, and you tap the line. Nothing happens, or rather, the line flips from unread to read, which is not what you asked for. To reach the dentist's card you had to close the inbox, swipe to the calendar, find the day, find the appointment. Four gestures for something the briefing had just named.
Individual reminders did not have this flaw. For a few days already, a reminder row in the inbox knew which card it was about, and tapping it opened that card straight away. The briefing was the only text in the inbox that named things without knowing where they were.
A summary that knows what it is talking about
The reason is simple, and it is a matter of construction. The briefing was built as text: the morning job read the day's events, composed the lines, saved the result, and threw everything else away. Once written, the summary kept no link to the appointments it described. It could lead nowhere because it no longer knew where it came from.
The change of 18 May is small, and it says something about how this kind of text should be written. The briefing now keeps, next to its content, the list of the appointments it summarises, in the order it cites them. The text itself has not changed by a comma. But it is no longer a loose sheet; it is a table of contents, and a table of contents points to pages.
On the phone, the inbox learned to read that list. A short tap on the briefing opens the card of the first appointment of the day, the one that comes up first. A long press keeps the menu that already existed: mark as read or unread, go to the reminder, delete.
Why the first one, rather than a choice? We considered it, and decided against. The briefing is read on waking, and what you want to check on waking, nine times out of ten, is what is coming right up. Putting a picker between the summary and the card would have added a screen to serve the tenth case. The other appointments of the day are one swipe away, in the calendar, where they are better laid out than they would be in a list of choices anyway. So the tap goes to the nearest one, deliberately: if usage one day shows that this guess is often wrong, the list is there, complete, and a picker could plug into it without redoing anything.
What opens is the real card, the one you would see when opening the appointment from anywhere else, with its address, its notes, its layout. The inbox closes first, then the card appears. That ordering is not a whim: on some phones, two panels opened on top of each other fight for the screen, and we had already paid to learn it.
The month view that ran away
The calendar lives to the right of the conversation screen, one swipe away, ever since a three-page carousel replaced the very idea of tabs. It has four views, year, month, week, day, and the month view was the problem.
It showed a grid with, under each day, up to four coloured dots, one per area of life present that day. It was readable and it looked good. But tapping a day switched the whole thing to the day view. You just wanted to see what was on the 22nd, and you found yourself on another screen, the month gone, with a button to find to get back. To compare two days you made the round trip twice. The month view was only good for leaving the month view.
Since 18 May, tapping a day no longer changes view. The grid stays put, the tapped day is highlighted, and the day's contents appear under the grid: all-day events first, then the others in time order, each with its area colour on the left edge and its place if it has one. You tap the 22nd, you read, you tap the 23rd, you read. The month does not move.
That day section comes in two forms, chosen with two small buttons: as a list, one line per event, or as a timeline, the same one as in the day view, with the hours in the margin and each event placed at its height. The list is quicker when there is little; the timeline shows the gaps and the overlaps when there is a lot.
And because a calendar grid takes room on a phone screen, a chevron in the day bar folds the grid into a single line, the month's name and a small arrow, to give the whole height to the day. Tapping that line unfolds it again. The transition is animated, gently, so the eye can follow what folds and what takes its place. And since the day is now visible in this view, the button that creates a new event, until then reserved for the day and week views, appeared here too.
The title nobody could read
A more modest fix was made in passing, and it deserves a sentence because it illustrates a kind of flaw you only see on phones other than your own. At the top of the panel sat a large “Calendar” title with, under it, a line giving the month or the week on display. On a narrow phone, or with the system font enlarged, that title collided with the view buttons to its right and got cut off. You read “Calen…”.
It was simply removed. You reach this panel with a swipe from the conversation, and a calendar on screen does not need a panel announcing “Calendar” above it. The month on display can be read in the grid itself, or in the folded bar. The freed space went to the filters and the view buttons, which can breathe. It is a principle we have held from the start: an interface that does not show begins by not naming itself.
The card, not the raw record
The third change to the calendar is the one you notice least and that may matter most. Until then, tapping an event in the calendar opened the memory's internal view, at the row of the corresponding record: a technical card, correct, but without the layout, the sections, the image, the checkboxes you get when opening the same thing from the conversation or from the memos and tasks panel.
So there were two ways of seeing the same appointment depending on the door you came in through. That kind of divergence starts small and ends up costing: every improvement to the nice card does not reach the other one, and one day someone reports that “the card doesn't show the same thing depending on where I come from”. On 18 May the calendar was wired to the same path as everything else. An event tapped in the month, week or day view opens the styled card, note or list depending on its kind. One card, whatever the route.
That wiring had one consequence to handle. A styled card lets you delete what it shows. So if you delete an appointment from a card opened through the calendar, the grid behind it has to notice: the coloured dot under the day must disappear, and so must the line in the day section. The calendar now listens for a signal sent on every deletion, drops the row from its own list immediately, then reloads from the server to catch anything else that may have changed in between. You close the card, the day is already clean.
Three things created at once, for the record
The same afternoon settled a third situation, whose story is told in another article, with what it taught the memory. Here, only what the screen shows of it.
When a single sentence creates two cards or more, “remind me about the dentist on Thursday and note that the gate code has changed”, the app used to show only the last card created. The first one was saved, but you did not see it, and nothing said there were two. Since 18 May, in that case, a temporary recap appears instead: as many lines as cards created, with the kind of each and its date. Tapping a line opens the real card. Closing that card does not send you back to an empty screen: you land on the recap again, to open the next one if you want. Closing the recap makes it go away for good; it is stored nowhere, it is a receipt, not a card.
For that receipt to appear at the right moment, a question of ordering had to be settled between what the server sends and what the phone shows. The automatic display of a single card waits two seconds after its creation, so as not to flicker if a second one arrives right behind. The recap, for its part, is sent before the spoken reply, and cancels that wait as soon as the second creation happens. Without this, the single card and the recap could arrive out of order, and the wrong one won. The reader has no need to know any of this; they only need to see the right thing, once.
What these gestures have in common
You could read this day as three small, unrelated interface fixes. A summary you can tap, a grid that stays put, a card that opens the same way from everywhere. They hang, though, on a single rule, which the app took a few weeks to put into words and has applied since: anything that names a thing on screen must let you reach that thing, in one gesture, without changing context.
The briefing named appointments; it now leads to the first. The month view named days; it now shows what they hold without running away. The calendar named events; it now opens their real card. And the recap names creations; each opens, and the receipt waits for you to come back.
The opposite of that rule is the dead-end text: a sentence that talks about something and leads nowhere, or leads somewhere you cannot come back from. A memory that keeps everything you tell it produces a lot of text that names things. Every time one of those texts becomes a door, the app needs a little less in the way of menus. That is how, gesture by gesture, the promise of having no tabs gets kept.