Description
Overview
The project has two conflicting navigation implementations causing confusion.
Background
The app uses both expo-router (file-based routing) and React Navigation (component-based). app/_layout.tsx imports SwipeableNavigation while App.tsx uses AppNavigator. This creates confusion about which navigation system is being used and adds unnecessary code.
Specifications
- Choose ONE navigation approach
- Recommended: use expo-router (modern Expo approach)
Tasks:
- Choose navigation strategy
- Remove duplicate navigation code
- Consolidate routing
Impacted Files:
- app/_layout.tsx
- app/(tabs)/
- src/navigation/AppNavigator.tsx
- App.tsx
Labels: architecture, priority-high
🙌Contribution Guidelines:
Assignment required before PR submission
Timeframe: 48-72 hours
PR description must include: Close #4
Star the repo⭐
For more context, please refer to the mobile README
Description
Overview
The project has two conflicting navigation implementations causing confusion.
Background
The app uses both expo-router (file-based routing) and React Navigation (component-based). app/_layout.tsx imports SwipeableNavigation while App.tsx uses AppNavigator. This creates confusion about which navigation system is being used and adds unnecessary code.
Specifications
Tasks:
Impacted Files:
Labels: architecture, priority-high
🙌Contribution Guidelines:
Assignment required before PR submission
Timeframe: 48-72 hours
PR description must include: Close #4
Star the repo⭐
For more context, please refer to the mobile README