> For the complete documentation index, see [llms.txt](https://cryptic-documentation.gitbook.io/cryptic-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cryptic-documentation.gitbook.io/cryptic-documentation/user-experience/3.-user-experience-overview/3.1-getting-started.md).

# 3.1 Getting Started

Cryptic is designed to give users, teams, developers, wallets, applications, and future AI agents a secure way to communicate, verify identity, manage wallets, approve actions, move value, and interact through cryptographic rails.

The getting started experience depends on which layer of the Cryptic stack a user enters through: **Mobile**, **Desktop**, or **SDK infrastructure**.

Cryptic Mobile is the consumer entry point.\
Cryptic Desktop is the secure command layer.\
Cryptic SDK is the developer and agent infrastructure layer.

Together, these surfaces connect secure communication, cryptographic identity, wallet functionality, encrypted data transfer, payment rails, and future agentic workflows into one product ecosystem.

#### Mobile: Account Creation and Wallet Setup

Cryptic Mobile gives users a simple entry point into the Cryptic ecosystem.

Users can install the Cryptic mobile application on iOS or Android, create an account, and generate or import a non-custodial wallet where supported.

During account creation, the user begins forming their Cryptic identity. This identity is designed to support secure communication, wallet functionality, encrypted data transfer, payment coordination, approvals, and future agent-based workflows.

Where supported, keys are stored using platform-native secure storage. Optional encrypted backup and recovery flows may also be available depending on the user’s setup, operating system, and product version.

The goal is to keep onboarding simple while giving users access to secure cryptographic infrastructure without exposing unnecessary complexity.

#### Mobile: First Communication and Payment

Once the account is created, users can begin using Cryptic Mobile for secure communication and crypto-native payments.

A user can add or select a contact, send a secure communication, initiate a contact-based payment or wallet transfer where supported, and view transaction status or confirmation feedback inside the app experience.

This creates a simple consumer flow:

**Communicate. Pay. Spend.**

Behind that simple experience is Cryptic’s broader infrastructure layer: cryptographic identity, wallet functionality, encrypted data transfer, and native payment rails working together in one product environment.

#### Desktop: Secure Workspace Setup

Cryptic Desktop expands the user experience from mobile access into a secure command layer for deeper workflows.

When available, users can install Cryptic Desktop on macOS or Windows, create or import an account, and connect the Desktop experience to secure communication, wallet management, encrypted notes, vault storage, confidential AI workflows, and supported ecosystem integrations.

Desktop is designed for power users, teams, and crypto-native operators who need more than a simple mobile interface.

Supported Desktop workflows may include:

* Wallet management
* Secure communication
* Swaps
* Lending and DeFi activity
* Encrypted notes
* Encrypted storage
* Confidential AI workflows
* Private coordination
* Ecosystem integrations

Desktop turns Cryptic into a secure workspace where communication, identity, wallet actions, encrypted data, and financial workflows can operate through one cryptographic identity layer.

#### Developers and Partners: SDK Integration Path

Cryptic SDK gives developers, applications, wallets, teams, and agent frameworks access to Cryptic’s secure infrastructure layer.

Developers and partners can review the Cryptic SDK documentation, understand supported environments, generate or connect cryptographic identity infrastructure, and integrate Cryptic rails into their own products.

The SDK is designed to support:

* Encrypted communication
* Cryptographic identity
* Key management
* Encrypted data transfer
* Payment rails
* Application and protocol integrations
* Future human-to-agent and agent-to-agent systems

Through the SDK, builders can bring secure communication, identity, encrypted data transfer, and payment coordination into existing applications, protocols, team workflows, wallet environments, or future agent-based systems.

#### Getting Started Summary

Cryptic is built to make advanced cryptographic infrastructure usable across three levels:

**Mobile** gives users simple access to secure communication, wallet functionality, crypto-native payments, and everyday use.

**Desktop** gives power users and teams a secure command layer for wallet management, DeFi workflows, encrypted storage, confidential AI workflows, and ecosystem integrations.

**SDK infrastructure** gives developers and partners programmable access to encrypted communication, cryptographic identity, key management, payment rails, and future agentic systems.

The result is one connected stack where users, teams, wallets, applications, and AI agents can communicate, coordinate, approve actions, move value, and operate through secure cryptographic rails.

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://cryptic-documentation.gitbook.io/cryptic-documentation/user-experience/3.-user-experience-overview/3.1-getting-started.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.