Projects and Apps

Projects and app connections are the boundaries DartStream uses to organize Flutter apps, Flame games, environments, providers, and runtime capabilities.

Current App Surface

The current app navigation includes project-oriented runtime areas such as Authentication, Cloud Storage, Database, Feature Flags, Data Streaming, Billing, and Settings.

Some provider connection screens are still being completed. Treat those as launch surfaces unless the workflow is explicitly wired to a backend provider endpoint.

Project Model

A DartStream project should capture:

  • name and description

  • application type, such as Flutter app, Flame game, internal tool, or live-ops service

  • environments, such as development, staging, and production

  • connected providers for auth, storage, data, telemetry, and runtime config

  • plan limits and entitlement state

Provider Connections

DartStream is designed to provide a consistent Dart-facing layer over vendors such as Firebase, Supabase, AWS, cloud storage, telemetry providers, and future game or AI services.

Provider screens should not be considered complete until they support:

  • credential capture or secret reference

  • validation

  • tenant and environment scoping

  • entitlement enforcement

  • audit history

  • tested runtime behavior

Related