Reading it tonight. First reaction to the framing: yes. It matches how the demo actually feels.
For that paragraph, keep it to one idea: we load what a person is about to look at, and nothing they are not. The rest is implementation and belongs in the docs, not the post.
Mara Lindqvist
to Leo, Sofie
Leo Marchetti
to Mara, Sofie
Draft of the launch post is ready for a technical read. I kept it short, three sections, one code sample each.
The framing I landed on is "the inbox that never shows you a spinner for the part you already know". Open a conversation and the newest message is simply there; the older ones follow. It is honest about what is fast and what is not, which I think readers appreciate more than a blanket "instant".
The screenshots are from the current build, so if the reading pane changes again before launch I will need new ones.
Can you check the paragraph on how we decide what to load before the click? I want it precise without turning into an engineering blog post.