An inbox is a list sorted by arrival time. Work rarely happens in that order.
A message from this morning may need no action. A thread from last Tuesday may be holding up a launch. A meeting invite can create three jobs before the meeting even begins. The inbox puts all of it in one stream and asks you to remember the difference.
The earliest Avalon put email into Kanban columns. The responsibility model was already visible, but the product still felt like a classified inbox.
That mismatch shaped Avalon's first major redesign. We turned email into Flowboard, a place where messages could become responsibilities instead of sitting in a pile. People could see what was On You, what was On Them, and what had already been Resolved.
It worked. It also showed us every place where Avalon still behaved like a collection of tools. The board had one language. The inbox had another. Calendar work lived somewhere else. The assistant could help, but it often arrived after you had already done the work of gathering context.
The second redesign starts there.
The first redesign introduced Flowboard, Pulse, and the On You, On Them, and Resolved language. It also brought more chrome and more competing signals.
The inbox stopped being the home screen
Arrival time still matters, so the inbox remains close. It simply no longer decides the order of your day.
Flowboard now gives each active thread a clear home:
- On You contains work you can move forward now.
- On Them keeps track of the replies, approvals, and decisions you are waiting for.
- Resolved holds work that reached a real ending.
- No Action keeps useful mail without turning it into a task.
These names sound obvious because they describe the question people already ask when they open a thread: who has the next move?
Arrival time is useful for mail servers. It is a poor way to decide what deserves your attention.
The redesign makes that question visible everywhere. Open a thread and you can see its current state. Move it, and the board updates. Reply to the person you were waiting on, and Avalon can bring the responsibility back to you. The system follows the work instead of asking you to maintain a second task list by hand.
One language across the product
Email creates work in more places than the inbox. A calendar invite needs preparation. A long thread needs a summary before a meeting. A promise made in a reply needs a follow-up next week.
The second redesign brings those moments into the same system. Meeting briefs show the threads, decisions, and open questions connected to the people in the room. Calendar views keep availability and preparation close to the event. Avalon AI can work with the thread you are reading instead of asking you to copy it into a separate chat.
Gmail and Outlook follow the same product rules. Provider-specific details still matter, especially around folders, labels, and calendar behavior, but the responsibility model stays consistent. Switching accounts should not mean learning Avalon again.
Avalon AI moved closer to the decision
An assistant is useful when it understands the work in front of you.
In the redesigned Avalon, the assistant sits beside the thread, meeting, or board state that gives a request meaning. You can ask what changed, find the unanswered question, draft a reply, or prepare a follow-up without rebuilding the context from scratch.
The action remains visible. A proposed reply is still a draft. A suggested state change tells you what will move and why. When Avalon is uncertain, the interface leaves room for correction instead of hiding the guess behind a confident sentence.
That distinction matters. Email contains commitments, customer information, contracts, and private conversations. Speed helps. Control matters more.
Quieter on purpose
The old interface gave too many elements the same visual weight. A secondary action could look as important as sending a reply. Empty space became decoration instead of helping the eye find the next step.
The new system uses neutral backgrounds, white surfaces, fine borders, and compact type. Blue marks the primary action. Peach, mint, and softer blues appear when they carry meaning, such as a state, warning, or confirmation.
Most screens now begin with content. Containers appear when they clarify a group or boundary. Buttons state the action they perform. The result feels calmer because fewer things are asking to be noticed at once.
The second redesign keeps the responsibility model and removes weight around it. The board is denser, quieter, and easier to scan.
The hard parts stayed hard
Avalon still has to interpret messy human communication. A thread can change direction halfway through. Someone can answer one question and ignore another. A message that looks resolved may reopen two days later.
The redesign does not pretend those cases disappeared. It gives them a clearer place to land. You can correct a state, see why something moved, and keep an important thread visible even when automation would normally set it aside.
We are also continuing to tighten the parts people feel before they can name them: faster first paint, better keyboard movement, clearer focus states, fewer layout shifts, and mobile screens that do not turn real work into horizontal swiping.
What the second redesign changes
Avalon now begins with responsibility. Email, calendar, meeting preparation, cleanup, and the assistant all connect back to the same question: what needs to happen next, and who owns it?
That gives the product a center. It also gives us a harder standard. Every new feature has to make the work clearer, reduce maintenance, or help someone act with better context. If it does none of those things, it does not belong on the screen.
There will always be more email. The redesign helps make sure there is less to remember.