SDK and Integration Paths

DartStream is built for Dart and Flutter teams. SDK work should connect app and game runtime workflows to DartStream services without forcing teams to hand-roll common production patterns.

Current Integration Paths

Current app and service integration paths include:

  • Firebase-backed user authentication.

  • Backend auth bootstrap through DartStream auth services.

  • Billing and entitlement checks through DartStream billing services.

  • Enterprise requests through platform services.

  • Feature flag and runtime-control workflows coordinated with IntelliToggle.

Dart and Flutter Direction

DartStream SDKs should eventually provide clean clients for:

  • auth context

  • tenant and project context

  • entitlement checks

  • live config

  • feature flag evaluation through IntelliToggle-backed provider workflows

  • realtime events

  • persistence and storage provider adapters

  • game services such as cloud save, inventory, sessions, and telemetry

OpenFeature and IntelliToggle

When a workflow is specifically about feature flag evaluation, use the IntelliToggle OpenFeature provider. DartStream should document that as a supported integration path, not as the whole DartStream product.

Example: Entitlement Check

final response = await http.get(
  Uri.parse('https://apibilling.dartstream.io/api/v1/billing/features/auth_providers/check'),
  headers: {
    'Authorization': 'Bearer $firebaseIdToken',
    'X-Tenant-ID': tenantId,
  },
);

Example: Subscription State

final response = await http.get(
  Uri.parse('https://apibilling.dartstream.io/api/v1/billing/subscription'),
  headers: {
    'Authorization': 'Bearer $firebaseIdToken',
    'X-Tenant-ID': tenantId,
  },
);

Roadmap

Future SDK examples should be added only when the matching backend and app workflow are tested end to end.