How stevenpersia/tinder-expo works
Project type and purpose
• This is a mobile client application (no backend code in this repo)
• Built with Expo (managed React Native workflow) and TypeScript
• Four main screens: Explore (Home), Matches, Messages, Profile
• Pure UI focus: card swiping, lists, navigation
A. Application Shell
• App.tsx – initializes the app, wraps everything in Expo/React Navigation
• Navigation Container + Bottom Tab Navigator (tabs for Home, Matches, Messages, Profile)
B. Screens Layer
• Home.tsx
• Matches.tsx
• Messages.tsx
• Profile.tsx
C. UI Components Library
• Each component lives under /components and is imported by one or more screens
D. Assets & Data
• /assets/images, /assets/styles, images.d.ts (types for static assets)
• /assets/data/demo.ts – local stub data for profiles/messages
E. Build & Tooling
• babel.config.js, tsconfig.json, Metro bundler via Expo CLI
• package.json – dependencies: react, react-native, expo, typescript, @react-navigation
External/Platform Services
• Expo SDK (camera, location, push notifications, etc.)
• App Store / Play Store delivery via Expo (or standalone build)
1) User Interaction → TabNavigator → Screen Component
2) Screen Component → imports UI Components → renders with props
3) UI Component requests data from Data Source (demo.ts or remote API)
4) Assets and Styles supply images/CSS-in-JS to Components
5) App Shell manages global state (if added later) and navigation events
Architectural Patterns & Design Principles
• Component-Based UI: All UI is broken into small, reusable React components
• Unidirectional Data Flow: Parent Screen passes props into child components
• Feature-by-Screen Organization: Separation of concerns by screen folder
• Static Typing: TypeScript ensures props/contracts in /types.ts and images.d.ts
Detailed breakdown
• The hierarchy: App → Navigation → Screens → Components
• The data flow: Data Source → Screens/Components → Render
• The assets dependency: Styles & Images → Components
• The external platform: Expo SDK & optional backend