> For the complete documentation index, see [llms.txt](https://docs.january.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.january.ai/mobile-sdks/mobile-sdk-overview.md).

# Mobile SDK Overview

Native libraries that wrap the January REST API with typed models and idiomatic async interfaces, so mobile teams work with foods, scans, logs, and predictions instead of raw HTTP.

### Status

Swift is available now as a pre-release development integration — see iOS SDK (Swift) for installation, guides, and reference. Android, React Native, and Flutter are planned; their pages here will fill in as they ship.

### The one rule

A long-lived January API key must never be embedded in an app binary or shipped to a device. Until client-safe short-lived credentials ship, mobile apps authenticate to your backend, and your backend calls January. The SDKs are built around that pattern.

### Same data model everywhere

The SDKs expose the same objects the REST API returns — detections, foods, servings, logs, predictions — so an integration started on the REST API carries over unchanged.