The problem: In financial and booking applications, trusting client-side logic (Flutter) fatally exposes the system to price manipulation, data injection, or cross-user privacy breaches.

The solution: "Zero Trust" architecture. Strict Firestore Rules unconditionally block client write access. Complex transactions (payments, capacity deduction, or refunds) are exclusively delegated to robust Node.js middlemen (Cloud Functions). The backend cryptographically validates every attempt, ensuring fintech-grade security and strict GDPR privacy adherence while completely completely concealing API secrets from the frontend.

The problem: Centralizing student payments to manually schedule payouts to studios generates severe fiscal, legal, and accounting bottlenecks. Furthermore, B2B adoption barriers in management software are steep if immediate payment is strictly demanded.

The solution: Decentralized financial orchestration. Stripe Connect was integrated so B2C revenue flows directly to each studio (delegating fiscal liability to them). Simultaneously, Stripe Billing was layered to manage B2B studio subscriptions (SaaS) and inject aggressive adoption pipelines—like 60-day automated trials and dynamic entry-level pricing for the first clients ("City Pioneers"). This enables scaling to hundreds of studios without congesting Ayogis's core corporate accounting.

The problem: Firebase NoSQL lacks strict data relationships, meaning that concurrent bookings or rapid mass cancellations easily corrupt dynamic class capacity properties. Furthermore, crossing permissions in nested security rules scales cloud read costs exponentially and inevitably leaks private data.

The solution: Synchronized "Dual-Write" architecture mechanism. The backend acts as the sole guardian, atomically isolating and duplicating views: one strictly for the client, one strictly for the studio. This shields maxAttendees numbers against data race conditions, clears bloated Security Rule complexities, and radically cuts monthly cloud database billing.

The problem: Apple and Google strictly enforce a hostile 30% toll over entirely all global mobile in-app payments. Operationally, if an entire class is cancelled by a studio, customer service teams manually reversing dozens of stripe charges creates instantaneous workflow chaos.

The solution: Cleanly decoupling the product stack into exclusively separated apps (B2C booking flows vs B2B analytics metrics CRMs). Following precise documentation, successful negotiation with Apple/Google App Store review boards effectively legally shielded Ayogis as a marketplace selling exclusively 'Local In-Person Physical Services', completely evading the 30% fees completely securely. Operationally: when B2B managers tap cancel class, background workers instantly differentiate internal Class Pack funds from bank card purchases—firing 100% automated and unattended Stripe refunds.