Stephan D
f1cbf64282
Make recipient changes explicit, prioritize verification retry, and label simulated outcomes prominently. Add shared typed analytics with bounded dummy capture, correlated service events and documented PostHog adapter contract. Validate privacy, retries, abandonment, keyboard recovery and accessibility. Related to #12.
SXCHNGE frontend
Home for the consumer application and its Flutter packages. The existing public Astro website lives in ../website/.
The first package, sxchnge_theme, provides installable light/dark Material themes and bundled Onest fonts. Its example/ folder demonstrates installation and component styling. The consumer application in app/ now includes a responsive login/sign-up preview; backend authentication is not connected.
The application will provide consumer registration, sign-in, onboarding and verification screens, exchange flows, and transaction history through the sxchnge backend. Eligibility and remaining limits are projections of Sendico's authoritative decisions.
Flutter is anticipated by the existing website handoff. Optional brand references are in ../website/design/ and ../website/flutter/brand_palette.dart; these do not prescribe the application's component styling.
Define the first customer journey and BFF contract before scaffolding the application. Sendico integration credentials belong in the backend.
Shared authentication: sxchnge_auth provides reusable login/signup providers, service contracts, and dummy implementations for both web and future mobile clients.