Reviewedv1Tooling & SDKs

FoodTech SDK architecture

Use one library per responsibility and avoid duplicating signing, sync, or storage across applications.

Last reviewed: July 16, 2026
Audience: mobile · backend
Contract state: Reviewed

Responsibility boundaries

foodtech_network: signing, transport, and retry.
foodtech_database: local state and outbox/inbox.
foodtech_sync: engine, reconciliation, and conflict policy.
foodtech_printer: discovery, rendering, and settings.
foodtech_auth: shared identity flows.
foodtech_ui: visual identity and RTL/LTR.

Application ownership

A library provides primitives and contracts while each application owns surface-specific orchestration. Do not place a Plus-only business rule inside a general library.

Releases

Every breaking change needs a major version, migration guide, and compatibility tests. Production applications never depend on a moving branch or local path.