How lucaswithboots/price_track_app works
Project type and purpose
• This is a cross-platform mobile application (“Price Track App”) built with Expo and React Native.
• It tracks item prices locally on the device (no server/backend code present).
• The presence of an android/ folder indicates a native Android wrapper, and the rest of the UI/routes live under src/ using Expo Router’s file-based routing.
File structure
Top-level:
• android/ ← Native Android project (Gradle, manifests, native code)
• app.json ← Expo configuration
• package.json ← JS dependencies & scripts
• babel.config.js ← JS transpilation rules
• metro.config.js ← bundler config for React Native
• src/ ← Application source
– app/ ← Screens & routes (file-based, e.g. index.tsx, [id].tsx, _layout.tsx)
– components/ ← Reusable UI components (Buttons, Forms, Grids, etc.)
– interfaces/ ← TypeScript interfaces (IItem, IItemPrices, etc.)
– services/ ← Business logic & persistence (items-storage.ts)
• assets/, public/ ← Static assets (images, screenshots)
• config files: tsconfig.json, tailwind.config.js, eslint.config.js
README
• Confirms Expo-based React Native project
Final reminder
• Be detailed: break down each layer into its subcomponents (e.g., list out src/app, src/components, items-storage.ts)
• Essential elements: file-based routing, service abstraction, native bridge, local storage
• Do not overpopulate with trivial files—focus on architectural boundaries and data flows