Skip to main content
Stringboot is built on a robust architecture designed for performance, reliability, and developer experience. Understanding these core concepts will help you get the most out of the platform.

​
Architecture

At its heart, Stringboot is a synchronized state management system for your application’s text content.
1

Dashboard

The command center where you manage strings, languages, and experiments. Changes published here are instantly propagated.
2

Global CDN

A low-latency edge network that distributes your content worldwide, ensuring fast sync times for users everywhere.
3

Client SDK

The intelligent engine running in your app. It handles synchronization, caching, and offline logic transparently.
4

Smart Cache

A multi-layered caching system (Memory + Disk) that guarantees instant string retrieval and offline availability.

​
Offline-First Design

Stringboot is designed to be offline-first, ensuring resilience and performance.

No Blocking Calls

String retrieval is always synchronous (from cache) or non-blocking async.

Resilience

Your app works perfectly even if the Stringboot API is down or the user has no internet.

Background Sync

The SDK handles network operations in the background, updating the cache silently.

​
The Caching Strategy

We use a sophisticated 3-Tier Caching Strategy:

L1: Memory Cache (RAM)

Speed: Instant (< 0.1ms) | Purpose: Serves the most frequently used strings (e.g., UI labels).

L2: Persistent Cache (Disk/DB)

Speed: Fast (< 10ms) | Purpose: Stores the entire string catalog for offline access.

L3: Network (CDN)

Speed: Variable (50ms - 500ms) | Purpose: Source of truth for updates.

​
String-Sync Protocol

Stringboot uses a custom Delta Sync Protocol to minimize data usage:
1

Meta Check

The SDK first checks a lightweight “Meta” endpoint to see if anything changed (using ETags).
2

Delta Download

If changes are detected, it downloads only the strings that have changed since the last sync.
3

Atomic Update

The local cache is updated atomically to ensure consistency.

​
A/B Testing Engine

Stringboot includes a native A/B testing engine.

Assignment

Users are assigned to experiment variants deterministically based on their Device ID.

Sticky

Once assigned, a user sees the same variant until the experiment ends.

Analytics

The SDK emits events that you can send to your analytics provider (e.g., Firebase, Mixpanel).

​
Security

Read-Only Tokens

Client SDKs use read-only API tokens. They cannot modify data on the server.

HTTPS

All communication is encrypted over HTTPS.

Integrity

Responses are signed to prevent tampering.