See where your posts come from,
and where they go.

I am building Postmob as an alternative timeline interface. Not because time is irrelevant, but because time alone has become too weak as the primary structure for reading what people think.

A timeline is useful when the question is what happened next. It becomes less useful when the question is what this is connected to, what changed, what it depends on, or what someone is trying to continue.

Before Postmob, I worked on Flint, a startup built around a similar conviction. Flint did not survive as a company, but the problem stayed alive. The interface was never just about arranging posts. It was about whether relation could become something a person could actually read.

Postmob starts from the smaller claim that posts should not only appear after one another. They should be able to point, answer, branch, return, and still remain legible on a screen.

The hard part is not drawing a graph. The hard part is making structure feel ordinary enough that people can use it before they have to explain why it matters.

Postmob is currently in closed beta. If this is a problem you already feel in feeds, threads, notes, or research, write to hello@postmob.net.

Postmob is a graph-native social network built on bidirectional threading. The graph is not the interface. It is what naturally forms underneath. And naturally, it becomes complex.

Graph-structured information may be natural for AI agents. Human thought branches like a graph, but our sensory system is built to take in information sequentially, one thing after another. For them, it is a native medium. For us, it is already close to the highest level of complexity we can still meaningfully understand and work with.

The problem is not graph structure itself, but whether people can read it without cognitive overload. A graph can preserve structure and still fail the moment it becomes too demanding to read. The real task is to make graph navigation intuitive enough that a person can follow what matters, trace what changed, and move through structure without losing the path of thought.

An earlier startup built around this direction did not survive, but the underlying conviction did. My cofounder and I believed that what made information useful was not just the information itself, but the context around it. We could feel that before we could measure it, and before we could explain it convincingly to anyone else. Like many new ideas, it had to be used before it could be believed.

This idea did not appear all at once. It moved slowly with me from Seoul to NYC to LA to Austin. What remained was how to preserve context without making it harder to read or build on. Postmob is my answer so far. The name carries the sense of a crowd in motion. Posts collect, collide, drift, and return. Postmob is an attempt to make that motion legible.

The work is still ongoing. If you want to follow it or respond to it, write to hello@postmob.net.