Overview
d-sports-engage-native (package name:engage-native) is the native mobile app for D-Sports. It mirrors the core PWA experience on iOS and Android: wallet, shop, leaderboard, locker room, and profile.
- Run:
bunx expo startorbun run start— then pressafor Android orifor iOS, or scan the QR code with Expo Go.
Tech stack
| Category | Technology |
|---|---|
| Framework | Expo 54, React Native 0.81, React 19 |
| Auth | Clerk (Expo) |
| Payments | RevenueCat (react-native-purchases) |
| Web3 | Thirdweb |
| State | Zustand |
| Storage | MMKV |
| UI | Lucide React Native |
| Navigation | Expo Router |
| Package | Bun |
Features
- Wallet — Tokens, holdings, pack opening, crypto checkout (via PWA backend)
- Shop — Collectibles, cart, coin bundles, checkout
- Leaderboard — Rankings and filters
- Locker room — Social feed and engagement
- Profile — User profile and settings
- Theme — Dark/light mode (default dark)
Getting started
- Clone the repository and run
bun install. - Configure environment (Clerk, RevenueCat, Thirdweb, API base URL) per repo README.
- Run
bunx expo start. - For development builds:
bun run build:dev(EAS) or run with Expo dev client.
EAS builds
Expo Application Services (EAS) handles native builds, OTA updates, and store submissions. All EAS CLI commands usebunx eas-cli via npm scripts.
Development builds
Development builds includeexpo-dev-client for dev menu, fast refresh, and JS updates without rebuilding native binaries.
Preview builds
Preview builds are release-mode binaries for internal QA and stakeholder testing.Production builds
Production builds are store-ready with auto-incrementing build numbers.OTA updates
Push JS/asset changes to existing installs without a new store build:OTA updates only work if JS is compatible with the installed native binary. If you add or change native modules, do a full build first.
Store submission
Ecosystem overview
See how the native app fits with the PWA, site, and Mic’d Up.
