Repository Structure - Solana App Kit

This document provides a comprehensive overview of how the Solana App Kit codebase is organized. Understanding this structure will help you navigate the project efficiently and know exactly where to make changes for your specific needs.

Root Directory Overview

solana-app-kit/
├── src/                    # Mobile app source code
├── server/                 # Backend server
├── android/                # Android-specific files
├── ios/                    # iOS-specific files
├── docs/                   # Documentation
├── scripts/                # Build and utility scripts
├── App.tsx                 # Main app component
├── package.json            # Dependencies and scripts
└── Configuration files     # Various config files

Monorepo Structure: The kit combines mobile app, backend server, and documentation in a single repository for easier development and maintenance

Mobile App Structure (`src/`)

The mobile application is organized into several key directories, each serving a specific purpose:

src/core/ - Essential app functionality used across multiple screens

src/core/
├── chat/                   # AI chat integration
├── dev-mode/              # Development tools and debugging
├── profile/               # User profile management
├── shared-ui/             # Reusable UI components
└── thread/                # Social feed and threading

Chat

AI chat integration with Solana blockchain interactions

Dev Mode

Development tools for debugging and testing

Profile

User profile management and account settings

Shared UI

Reusable components used throughout the application

Thread

Social feed and threading for community features

Purpose: Core features are central to the app’s functionality and provide shared capabilities across multiple screens and modules.

src/core/ - Essential app functionality used across multiple screens

src/core/
├── chat/                   # AI chat integration
├── dev-mode/              # Development tools and debugging
├── profile/               # User profile management
├── shared-ui/             # Reusable UI components
└── thread/                # Social feed and threading

Chat

AI chat integration with Solana blockchain interactions

Dev Mode

Development tools for debugging and testing

Profile

User profile management and account settings

Shared UI

Reusable components used throughout the application

Thread

Social feed and threading for community features

Purpose: Core features are central to the app’s functionality and provide shared capabilities across multiple screens and modules.

src/modules/ - Independent, protocol-specific integrations

src/modules/
├── data-module/           # Blockchain data fetching
├── meteora/               # Meteora protocol integration
├── moonpay/               # MoonPay fiat on-ramp
├── nft/                   # NFT functionality
├── pump-fun/              # Pump.fun integration
├── raydium/               # Raydium DEX integration
├── solana-agent-kit/      # AI agent integration
├── swap/                  # Token swapping
├── token-mill/            # Token creation and management
└── wallet-providers/      # Wallet connection providers

Data Module

Blockchain data fetching and market information

Meteora

Dynamic Liquidity Markets integration

MoonPay

Fiat on-ramp for purchasing crypto

NFT

NFT functionality with Tensor integration

Pump.fun

Meme token creation and trading

Raydium

Professional token launching platform

Solana Agent Kit

AI agent integration for automated interactions

Swap

Multi-DEX token swapping with optimal routing

Token Mill

Advanced token creation with custom bonding curves

Wallet Providers

Multi-provider wallet connection and management

Purpose: Each module encapsulates a specific protocol or feature, making the codebase modular, maintainable, and allowing you to use only what you need.

src/screens/ - React Native screens organized by feature area

src/screens/
├── Common/                # Shared screens
│   ├── intro-screen/      # App introduction
│   ├── login-screen/      # Authentication
│   └── launch-modules-screen/ # Feature selection
└── sample-ui/             # Example implementations
    ├── chat/              # Chat interface examples
    └── Threads/           # Social feed examples

Common Screens

Shared across features - intro, login, and module selection screens

Sample UI

Example implementations showing how to use core features and modules

Purpose: Screens define the user interface and navigation flow, providing the main entry points for different app features.

src/shared/ - Common utilities and configurations

src/shared/
├── config/                # App configuration
├── context/               # React Context providers
├── hooks/                 # Custom React hooks
├── mocks/                 # Mock data for development
├── navigation/            # Navigation configuration
├── services/              # API and blockchain services
├── state/                 # Redux store and state management
├── types/                 # TypeScript type definitions
└── utils/                 # Utility functions

Configuration

App settings and environment configuration

Context

React Context providers for global state

Hooks

Custom React hooks for reusable logic

Navigation

Navigation setup and routing configuration

State Management

Redux store and state management slices

Types

TypeScript definitions for type safety

Purpose: Shared resources provide common functionality and maintain consistency across the entire application.

src/assets/ - Static resources and design system

src/assets/
├── images/                # Image files
├── svgs/                  # SVG graphics
├── colors.ts              # Color palette
└── typography.ts          # Typography system

Images

Static image files for app branding and UI

SVGs

Scalable vector graphics for icons and illustrations

Colors

Color palette definitions for consistent theming

Typography

Typography system for consistent text styling

Purpose: Centralized asset management and design system definitions ensure visual consistency.

Backend Server Structure (`server/`)

The backend server provides essential API endpoints and services:

Platform-Specific Directories

ios/ - iOS-specific configuration and native code

ios/
├── SolanaAppKit/          # Main iOS project
│   ├── Info.plist         # iOS app configuration
│   ├── AppDelegate.mm     # iOS app delegate
│   └── Images.xcassets/   # iOS app icons and images
├── Podfile                # CocoaPods dependencies
└── SolanaAppKit.xcworkspace # Xcode workspace

iOS Development: Requires macOS and Xcode for building and testing on iOS devices

ios/ - iOS-specific configuration and native code

ios/
├── SolanaAppKit/          # Main iOS project
│   ├── Info.plist         # iOS app configuration
│   ├── AppDelegate.mm     # iOS app delegate
│   └── Images.xcassets/   # iOS app icons and images
├── Podfile                # CocoaPods dependencies
└── SolanaAppKit.xcworkspace # Xcode workspace

iOS Development: Requires macOS and Xcode for building and testing on iOS devices

android/ - Android-specific configuration and native code

android/
├── app/
│   ├── src/main/          # Main Android source
│   ├── build.gradle       # App-level build configuration
│   └── proguard-rules.pro # Code obfuscation rules
├── gradle/                # Gradle wrapper
└── build.gradle           # Project-level build configuration

Android Development: Works on any platform with Android Studio and Java/Kotlin support

Configuration Files

Key configuration files in the root directory:

App.tsx

Main React Native component and app initialization entry point

package.json

Project dependencies, scripts, and metadata configuration

app.config.js

Expo configuration for builds, deployment, and app settings

babel.config.js

JavaScript compilation configuration and plugin setup

metro.config.js

Metro bundler configuration for React Native builds

tsconfig.json

TypeScript compiler configuration and type checking rules

.env.local

Environment variables (not in repo, created during setup)

mint.json

Documentation configuration for this documentation site

Module Architecture Pattern

Each module follows a consistent, well-defined structure:

module-name/
├── components/            # UI components specific to this module
├── hooks/                 # Custom hooks for module functionality
├── screens/               # Screens specific to this module
├── services/              # API and blockchain services
├── types/                 # TypeScript interfaces
├── utils/                 # Utility functions
├── index.ts               # Public API exports
└── README.md              # Module documentation

This pattern ensures:

Consistency

Similar organization across all modules makes navigation predictable

Encapsulation

Module internals are contained with clean public interfaces

Reusability

Clean public APIs make modules easy to integrate and reuse

Maintainability

Easy to understand and modify with clear separation of concerns

Data Flow Architecture

Understanding how components connect and data flows through the application:

Component Hierarchy

Screens import and use Components from modules for UI composition

State Management

Components use Hooks for state management and business logic

External Operations

Hooks call Services for API interactions and blockchain operations

Utility Functions

Services use Utils for common operations and data processing

Type Safety

Everything uses Types for TypeScript type safety and IntelliSense

Data Flow Diagram

Development Workflow

Understanding the structure helps with common development tasks:

Best Practices

Module Independence

Keep modules loosely coupled to maintain modularity and testability

Shared Code

Put common functionality in src/shared/ for reusability across modules

Type Safety

Define interfaces in module types/ directories for better developer experience

Export Consistency

Use index.ts files for clean public APIs and easier imports

Documentation

Update module READMEs when making changes to keep docs current

Testing

Write tests for critical business logic in services and hooks

Next Steps

Now that you understand the repository structure, explore these guides:

Assets Guide

Learn about the design system and asset management for consistent UI

Components Guide

Understand component architecture and reusable UI patterns

Configuration Guide

Configure the app and understand environment settings

Introduction

Getting Started

Modules

Server

​Root Directory Overview

​Mobile App Structure (src/)

Chat

Dev Mode

Profile

Shared UI

Thread

Chat

Dev Mode

Profile

Shared UI

Thread

Data Module

Meteora

MoonPay

NFT

Pump.fun

Raydium

Solana Agent Kit

Swap

Token Mill

Wallet Providers

Common Screens

Sample UI

Configuration

Context

Hooks

Navigation

State Management

Types

Images

SVGs

Colors

Typography

​Backend Server Structure (server/)

​Platform-Specific Directories

​Configuration Files

App.tsx

package.json

app.config.js

babel.config.js

metro.config.js

tsconfig.json

.env.local

mint.json

​Module Architecture Pattern

Consistency

Encapsulation

Reusability

Maintainability

​Data Flow Architecture

​Data Flow Diagram

​Development Workflow

​Best Practices

Module Independence

Shared Code

Type Safety

Export Consistency

Documentation

Testing

​Next Steps

Assets Guide

Components Guide

Configuration Guide

Root Directory Overview

Mobile App Structure (`src/`)

Backend Server Structure (`server/`)

Platform-Specific Directories

Configuration Files

Module Architecture Pattern

Data Flow Architecture

Data Flow Diagram

Development Workflow

Best Practices

Next Steps