Why it matters
Mobile app gives ForkMesh a concrete mechanism for a native pocket surface for repository activity and chat. Carry the mesh in your pocket: browse repositories, follow activity, chat, and get notifications from a native mobile app.
A distributed forge still needs clean entry points for readers, contributors, mobile users, and editor workflows. In ForkMesh, mobile app addresses that need at the feature level, keeping the behavior close to the repository instead of buried in a detached hosted layer.
How ForkMesh handles it
ForkMesh handles mobile app through the same split it uses across the product: ForkMesh exposes web, mobile, editor, docs, status, and clean URL surfaces on top of the desktop-node and mainnode model.
The behavior is intentionally narrow: Carry the mesh in your pocket: browse repositories, follow activity, chat, and get notifications from a native mobile app. Those surfaces route to live or mirrored data; they are access layers, not the canonical Git store.
Where it fits
Use mobile app when people need to browse, contribute, learn, and receive updates outside the main desktop window.
It pairs with the rest of Mobile, web & IDE because Mobile app keeps a native pocket surface for repository activity and chat connected to the repository, its signatures, and the nodes that serve it.