yonko-sid/quantsync_website

Purpose and Entry Points

QuantSync is a Flutter multi-platform client presenting an institutional crypto advisory and algorithmic-trading product suite. The implemented repository appears primarily to be a marketing/home experience with authentication/access UI and a dashboard route, rather than the exchange-ingestion or execution backend described in the README.

Flutter starts at lib/main.dart, which composes the application root in lib/src/app.dart. Native launchers host the same Flutter runtime on Android (android/app/src/main/kotlin/com/example/quantsync/MainActivity.kt), iOS (ios/Runner/AppDelegate.swift), desktop, and web (web/index.html).

Application Shell and Design System

lib/src/app.dart is the likely composition boundary for routing, theme selection, and top-level providers. Shared visual primitives are centralized in lib/src/config/styles/app_themes.dart, lib/src/config/styles/app_colors.dart, and lib/src/config/styles/app_spacing.dart; feature UI should consume these rather than define independent styling systems.

Home Experience and Navigation

The home feature organizes the public product experience. lib/src/features/home/screens/home_screen.dart likely owns the page-level layout/navigation, while lib/src/features/home/screens/sections/header_section.dart and lib/src/features/home/screens/sections/hero_section.dart establish the primary entry actions. Product and platform messaging is decomposed into independently composable sections such as lib/src/features/home/screens/sections/products_showcase_section.dart and lib/src/features/home/screens/sections/integrations_section.dart.

Interactive branding/visualization is isolated in lib/src/features/home/widgets/hero_3d_graphic.dart; the standalone infinity-animation_3d.html may support or prototype this presentation asset.

Authentication and Access Boundary

Authentication UI is separated from home content through lib/src/features/auth/widgets/auth_modal.dart and lib/src/features/home/widgets/access_modal.dart. Their backend boundary is lib/src/repositories/auth_repository.dart, with session/auth state exposed via lib/src/state/auth_provider.dart. This separation permits demo-mode UI when backend configuration is unavailable and keeps Supabase calls out of presentation components.

Backend, Runtime State, and Product Services

Supabase is the declared external backend and is encapsulated by lib/src/services/supabase_service.dart. Its URL and anonymous key are supplied at runtime using Dart defines; absent configuration should preserve demo behavior rather than fail application startup.

Cross-cutting client state is partitioned by concern: lib/src/state/app_state_provider.dart for app-wide state, lib/src/state/theme_provider.dart for appearance, and lib/src/state/device_info_provider.dart for platform/device adaptation. Service boundaries include analytics (lib/src/services/analytics_service.dart), remotely controlled capability decisions (lib/src/services/feature_flag_service.dart), and downloads (lib/src/service/download_service.dart).

Dashboard and Domain Presentation

Authenticated or product-facing dashboard UI resides in lib/src/features/home/screens/dashboard_screen.dart. Domain display data is modeled independently in lib/src/models/product_model.dart, allowing product showcase/dashboard components to render structured product metadata without coupling to transport or authentication concerns.

Deployment Surface

The primary documented runtime is Flutter Web on Chrome/Chromium, hosted from web/index.html with web metadata in web/manifest.json. The repository also ships Flutter-generated platform hosts for Android, iOS, macOS, Linux, and Windows, making the Dart application layer portable while platform-specific build and launch responsibilities remain under their respective top-level directories.