PazarB2B is an advanced mobile application engineered to streamline Business-to-Business (B2B) trade and intelligently manage surplus inventory. Designed with modern mobile architecture, it empowers enterprises to minimize waste, discover new wholesale partners, and optimize supply chain operations through a seamless digital experience.
- 📦 Surplus Inventory Management: Effortlessly list, track, and monetize excess goods.
- 🤝 B2B Networking: Quickly establish connections with verified industry partners.
- 🔔 Real-Time Notifications: Stay updated on orders, inquiries, and market trends.
- 🎨 Modern UI/UX: A highly responsive, intuitive interface built with Expo Router.
- 🔒 Enterprise-Grade Security: Robust data protection for user information and trade transactions.
We leverage a cutting-edge mobile development stack to ensure high performance, maintainability, and exceptional user experience:
- Core: React Native, Expo, TypeScript
- Routing: Expo Router (File-based navigation)
- Database & ORM: Drizzle ORM (Type-safe database interactions)
- State & Data Fetching: React Query
- Styling: Custom StyleSheet / NativeWind
- CI/CD & Builds: Expo Application Services (EAS)
Follow these instructions to set up the project locally.
- Node.js (v18 or higher)
- npm or yarn
- Expo Go app on your physical device (or iOS Simulator / Android Emulator)
-
Clone the repository:
git clone https://github.com/Amertos/PazarB2B.git
-
Navigate to the project directory & install dependencies:
cd PazarB2B npm install -
Start the development server:
npx expo start
-
Scan the generated QR code using your Expo Go app to view it on your mobile device.
This project is configured with EAS (Expo Application Services) for automated cloud builds.
To generate standalone production binaries:
- Android (APK):
eas build --platform android --profile production
- iOS (IPA):
eas build --platform ios --profile production
Note: Build artifacts are deliberately ignored via .gitignore to maintain a clean and secure repository.
This repository strictly adheres to security best practices:
- No API Keys or Database Credentials are exposed.
.envfiles and local environment configurations are securely ignored.