Skip to main content
aiTalk App · xTalk SDK

Use aiTalk to communicate. Use xTalk to integrate.

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.

NetworkDecentralized MeshSelf-organized nodes, no central server
User productaiTalk AppBuilt for end-user communication without network coverage
Developer layerxTalk SDKBuilt for device access and app integration
No central server
Voice + Text + Map
Mesh SDK
aiTalkxTalk SDK
13 km discovery7 km call
4 devices discovered, 2 contacts online
Start a live call and switch to the Mesh path
Location synced, group relay enabled
Chat
Call
Map
Mesh
App + SDK

aiTalk is the app. xTalk is the SDK.

aiTalk focuses on messaging, calls, maps, and group experience for end users. xTalk exposes Mesh, protocol, and SDK capabilities for device vendors and integrators.

Why it matters

Start with what the network can do

The first screen should explain the capabilities clearly, then send users either to the app download flow or into the docs entry points.

Discover

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.

Communicate

Text, voice, and location sharing run on the same network

aiTalk puts live calls, short messages, maps, and groups into one communication flow that can keep working without public internet services.

Integrate

xTalk packages the lower layers as an SDK

The developer docs area is already in place, and individual pages will be filled in progressively as they are confirmed.

Surfaces

aiTalk is for users, xTalk is for integration

They are not the same layer: aiTalk is the product, xTalk is the developer-facing capability layer. The information architecture now follows that split.

App

aiTalk mobile

The iOS and Android clients cover discovery, messaging, maps, calls, and group collaboration.

Open Open
Placeholder

Web / desktop / CLI

Docs pages for browser, desktop, and CLI workflows are reserved and will be filled in gradually.

Open Open
Placeholder

xTalk SDK

The xTalk SDK section is already reserved in docs and its pages will be published one by one.

Open Open
Docs

Hardware references

Hardware reference pages remain available in docs and are updated alongside the visible SDK documentation.

Open Open
Flow

First time here? Follow three steps

The homepage keeps the shortest path to downloads and docs so the first screen remains readable.

01

Start from the docs entry page

The docs structure is already in place. Content will be filled page by page from the overview onward.

Open docs overview Open
02

Download the app or check client options

If your goal is direct product use, start from the download center while the client docs pages are being filled in.

Open download center Open
03

Enter the developer docs area

SDK, protocol, and hardware pages are already reserved as placeholders and will be filled in progressively.

Open SDK docs Open