Shared libraries

FoodTech SDKs and engineering components

Reusable libraries for signing, networking, offline state, sync, printing, identity, and interface foundations.

6SDKs

Reviewed

foodtech_network

Shared transport layer for HMAC signing, retry/backoff, and fail-closed policy.

Platforms: Flutter · Dart
Responsibility: Standardize transport, signing, and diagnostics without hardcoded secrets.

Reviewed

foodtech_database

High-throughput local state for offline work, outbox/inbox, ledger, idempotency, and conflicts.

Platforms: Flutter · Dart
Responsibility: Persist local intent under independent FoodTech APIs without third-party database branding.

Reviewed

foodtech_sync

Sync, replay, reconciliation, and conflict engine with branch-mesh contracts.

Platforms: Flutter · Dart · Server contracts
Responsibility: Coordinate delivery and receipt with idempotency and auditable diagnostics.

Reviewed

foodtech_printer

USB, BLE, and Wi-Fi discovery and printing with shared renderer and settings.

Platforms: Flutter · Android · iOS
Responsibility: Separate device discovery and rendering from order and payment rules.

Foundation

foodtech_auth

App-agnostic sign-in, recovery, password change, and business identity flows.

Platforms: Flutter · Dart
Responsibility: Standardize UX and contracts without owning application permissions or tenant policy.

Reviewed

foodtech_ui

Shared GetX design system for Arabic, English, RTL, and LTR.

Platforms: Flutter · Dart
Responsibility: Unify visual components without moving business logic into the UI layer.

Installation

Package coordinates are linked only after the publishing repository is certified; undocumented install commands are never invented.