How diivi/swapsta works
Project type and purpose
• This is a cross-platform Flutter client application (Android, iOS, Web, Windows) called “Swapsta.”
• Its primary purpose is to allow users to list “swappables,” browse items, initiate swaps, and manage swap history.
• It relies on external backend services (e.g., Firebase for authentication, data storage, Google Sign-In).
File structure
• Top-level platform folders:
• android/ (native Android wrapper and Gradle builds)
• ios/ (native iOS wrapper, Xcode project, Podfile)
• web/ (static web assets, HTML, CSS, JS)
• windows/ (CMake, native Windows runner)
• Core application code under lib/:
• lib/main.dart – Flutter entry point
• lib/models/ – domain models (Category, Swap, Swappable)
• lib/providers/ – state-management using Provider pattern (Auth, swappables, swaps, UI)
• lib/screens/ – UI pages (home, explore, profile, add item, swap details, auth)
• lib/widgets/ – reusable UI components (cards, lists, headers, dialogs)
• lib/globals.dart – global constants
• Configuration and assets:
• pubspec.yaml/lock – dependencies & assets
• assets/ and img/ – fonts and images
• Test harness: test/widget_test.dart
README for additional insights
• The README only contains a link to a Behance UI mockup. The image demonstrates the intended look & feel but provides no architectural details.
• No server-side code is present, so interactions with backend services must be via Flutter plugins (e.g., cloud_firestore, firebase_auth).