How hennyxg/accountabuddy-rn works
Project type and purpose
• Accountabuddy is a full-stack mobile application built with Expo/React Native (TypeScript) for iOS and Android.
• It uses Firebase as its primary backend (Auth, Firestore, Storage, Cloud Messaging) and Cloud Functions (HTTP, triggers, scheduled) to host business logic.
• It integrates with external services: Stripe (payments), OpenAI (proof verification), and FCM for push notifications.
• It implements offline-first sync via a local queue (MMKV + custom offline service).
File structure
• Top-level:
• App.tsx + app/ folder: Expo Router–driven file-based navigation for authentication, tabs, modals, screens.
• functions/: Firebase Cloud Functions (src/http, scheduled, triggers, notifications, utils).
• src/: Shared code for client: components, services, hooks, stores, schemas, types, utils, unistyles.
• config files: firebase.json, firestore.rules, eas.json, .github/workflows/eas-build.yml.
• tests and e2e/maestro: Jest unit tests and Maestro E2E flows.
• docs/: design docs, flows, snapshots.
• Patterns:
• MVVM/Provider pattern: QueryProvider + Zustand stores for state.
• Service layer: src/services abstracts Firebase and external-API calls.
• Offline sync: services/offline and hooks/useOfflineSync.
• Cloud Functions orchestrate payments, verifications, notifications via triggers and scheduled tasks.
README insights
• Minimal (“This is Accountabuddy”), but file tree and docs confirm mission: habit/task accountability, buddy system, proof submission/verification.
Don’t over-complicate
• Every subsystem at a high level
• Payment pipeline
• Proof verification pipeline
• Offline sync pipeline