Nearby people and devices can be found across multiple hops
Even without a central service, nodes can spread discovery data across the mesh so nearby awareness is not limited to a single direct broadcast.
aiTalk is the app for end users, while xTalk is the Mesh SDK for device access and application integration. Both run on the same decentralized network without relying on a central server.
aiTalk focuses on messaging, calls, maps, and group experience for end users. xTalk exposes Mesh, protocol, and SDK capabilities for device vendors and integrators.
The first screen should explain the capabilities clearly, then send users either to the app download flow or into the docs entry points.
Even without a central service, nodes can spread discovery data across the mesh so nearby awareness is not limited to a single direct broadcast.
aiTalk puts live calls, short messages, maps, and groups into one communication flow that can keep working without public internet services.
The developer docs area is already in place, and individual pages will be filled in progressively as they are confirmed.
They are not the same layer: aiTalk is the product, xTalk is the developer-facing capability layer. The information architecture now follows that split.
The iOS and Android clients cover discovery, messaging, maps, calls, and group collaboration.
OpenDocs pages for browser, desktop, and CLI workflows are reserved and will be filled in gradually.
OpenThe xTalk SDK section is already reserved in docs and its pages will be published one by one.
OpenHardware reference pages remain available in docs and are updated alongside the visible SDK documentation.
OpenThe homepage keeps the shortest path to downloads and docs so the first screen remains readable.
The docs structure is already in place. Content will be filled page by page from the overview onward.
Open docs overviewIf your goal is direct product use, start from the download center while the client docs pages are being filled in.
Open download centerSDK, protocol, and hardware pages are already reserved as placeholders and will be filled in progressively.
Open SDK docs