How pelixpng/pastvuapp works
Project type and purpose
• This is a cross-platform mobile application (Android, iOS, watchOS, macOS, visionOS) built in React Native using Expo and TypeScript.
• The app’s sole “backend” is the external PastVu REST API (for historical photos) and mapping APIs (Google Maps on Android/Expo, Apple Maps on iOS/watchOS).
File structure
• Top-level “code/” directory holds everything:
• android/ & ios/ subprojects: native host containers and build scripts
• src/: React-Native TypeScript code – organized by API services, UI components, hooks, navigation, screens (view + view-model), global store, types, utilities
• assets/ & app.json, babel.config.js, metro.config.js, eas.json: Expo configuration and static assets
• targets/: platform-specific Swift code for Apple Watch widget and home-screen widget
• Presence of “.vm.ts” files indicates an MVVM-style pattern (Screen.view ↔ Screen.vm).
• Global store files (Api.store.ts, Map.store.ts, Theme.store.ts) suggest a centralized state management solution.
• No custom backend code—external third-party services only (PastVu API, Google/Apple Maps).
README for additional insights
• Confirms use of TaigaUI components, PastVu API, Google & Apple Maps
• Targets multiple OSes via Expo’s “eas.json” and “expo-target.config.js” in targets/
• Blue for JS layers (UI, VM, Store, Service)
• Green for external services (PastVu API, Map API)
• Orange for native hosts (Android, iOS, watchOS, widget)
• Rectangles for modules/directories
• Clouds for external APIs