Flutter · colveor

Overview

colveor is the full application foundation. It re-exports colveor_ui and adds everything an app needs to talk to a Colveor Core backend.

What it adds

  • Bootstrap — VoBootstrap.initialize wires Firebase, the Dio client and the auth session before runApp.
  • Configuration — A VoConfig that extends the colveor_ui config with API, Firebase and DPoP settings.
  • Networking — A Dio client with request headers, logging, token refresh and pluggable interceptors.
  • DPoP — RFC 9449 proof-of-possession on every authenticated request, enabled by default.
  • Authentication — Phone/OTP and email/password flows, session restore and ready-made auth screens.
  • Notifications — Firebase Cloud Messaging setup, permission prompt and device registration.

Import paths

Import only from package:colveor/.... Every colveor_ui entry point is re-exported, so importing package:colveor_ui alongside it causes VoConfig and VoBootstrap name clashes.

NameDescription
colveor.dartColveorApp, ColveorRef, VoBootstrap, VoConfig, base screens, routing and the UI context extensions.
config.dartVoConfig, Environment, VoRoutingConfig, VoFeedbackConfig, VoFirebaseConfig and VoInterceptorHooks.
auth.dartAuthController, AuthSession, AuthState, User, Profile, the auth flow controller, services and auth screens.
notifications.dartVoNotificationController, notification state and storage, and requestNotificationPermission.
extensions.dartcolveor_ui extensions plus context.currentUser, context.logout() and context.voControllers.
routing.dart, theme.dart, utils.dartDirect re-exports of the matching colveor_ui entry points.
widgets/*.dartbuttons, dashboard, display, feedback, inputs, layout, overlay and page_flow — re-exported from colveor_ui.

Relationship to colveor_ui

colveor adds no widgets, theme or routing code of its own; those come from colveor_ui. Use colveor_ui on its own when you only need the UI layer, and colveor when your app talks to a Colveor Core backend.