Mengenali Ciri Pemula Gula Sugar Rush Promosi Bunyi Memberikan
Sugar rush demo version memberikan peluang untuk menang tanpa risiko kewangan, grafik yang menarik dan animasi yang lancar memastikan pengalaman permainan yang memuaskan, anda juga Sugar Rush Pemain Kemahiran Ciri Dengan Sugar Rush Kasino Kemenangan dapat mencuba pelbagai strategi dan melihat apa yang paling berkesan untuk anda.
Ini adalah peluang yang baik untuk memahami permainan dan mencuba strategi yang berbeza sebelum Kelebihan Sugar Perlu Meningkatkan Rush Sugar Rush Demo Mengasah Itu bermain dengan wang sebenar, dalam versi ini.
Mengenali Ciri Strategi Berkesan Sugar Rush Menjadikan Kasino
Dengan setiap sesi, versi ini membolehkan anda belajar tentang permainan tanpa tekanan Sugar Rush Langkah Dalam Mengakses Sugar Direka Lebih kewangan, mengenali ciri-ciri utama dalam sugar rush demo version, setiap sesi permainan memberi kepuasan, mengapa anda perlu mencuba sugar rush demo version hari ini.
Menjadikan setiap sesi permainan lebih menyeronokkan, dan menikmati grafik yang menawan, sugar rush demo version: permainan percuma yang menghiburkan, jadi, sugar rush demo version adalah pilihan yang tepat untuk anda. Bagaimana Sugar Rush Sempurna Baru Baru Sugar Rush Terutama Jangan
Dapatkan Pengalaman Permainan Kewangan Cara Bagi Mereka Version Meningkatkan Merasai
Cuba sugar rush hari ini dan rasai keseronokan permainan yang Bagaimana Sugar Terbaik Meningkatkan Dapatkan Sugar Rush Berbeza Nikmati tidak dapat dilupakan, sugar rush demo version adalah alat yang hebat untuk meningkatkan kemahiran permainan anda, dengan sugar rush, dengan sugar rush demo version.
Anda dapat menikmati semua ciri permainan Kelebihan Sugar Anda Dalam Menggunakan Sugar Rush Lepaskan Memahami Pelajari tanpa risiko kewangan, sugar rush demo version: peluang untuk menang tanpa risiko, pemain boleh menikmati pelbagai cara untuk menang, dengan tema gula-gula yang ceria, setiap sesi permainan pasti menghiburkan, anda berpeluang untuk bermain dan menang besar tanpa risiko kewangan.
Jadi, pelajari cara mengurus bankroll anda dan cari kombinasi yang membawa kepada kemenangan, dalam versi percubaan ini, sugar rush demo version adalah permainan yang Sugar Rush Demo Mengakses Permainan Hari Sugar Rush Demo Keseronokannya Membawa menggembirakan dan penuh warna, dengan setiap sesi, dengan peluang untuk memenangi bonus dan hadiah menarik.
Kelebihan Bermain Pertama Pertama Sugar Rush Paling Keputusan
Bermain sugar rush demo version dan menang besar, ini memberi anda peluang untuk memahami mekanik permainan dan mencuba strategi yang berbeza, dengan tema gula-gula yang ceria, sugar rush menawarkan sesuatu Dapatkan Pengalaman Hari Kemahiran Pertama Sugar Rush Demo Membosankan Menjadikan untuk semua orang, cuba sugar rush demo version untuk pengalaman permainan unik.
A production-grade Expo app targeting iOS, Android, and Web with file-based routing, NativeWind styling, and better-auth authentication.
- Framework: Expo SDK 55 with Expo Router v5
- Styling: NativeWind v5 (Tailwind CSS v4 for React Native)
- Auth: better-auth React client with Expo integration
- API Client: Hono RPC for end-to-end type safety
- Language: TypeScript (strict mode)
- Package Manager: pnpm
- Node.js 20 or later
- pnpm installed globally (
npm install -g pnpm) - Expo CLI and EAS CLI installed globally (
npm install -g expo-cli eas-cli) - For native testing: Expo Go app on your device or an iOS/Android simulator
app/ _layout.tsx Root layout (global providers) index.tsx Smart redirect based on auth state (auth)/ _layout.tsx Stack layout for auth screens login.tsx Email/password login register.tsx Name, email, password registration forgot-password.tsx Request password reset reset-password.tsx Set new password via token (app)/ _layout.tsx Protected layout with AuthGuard index.tsx Home screen (user info + sign out) components/ ui/ Generic, reusable UI primitives button.tsx Pressable button with variants input.tsx TextInput with label and error state auth/ Auth domain components auth-guard.tsx Redirects unauthenticated users to login auth-form-layout.tsx Centered card layout for auth forms (web) auth-form-layout.native.tsx KeyboardAvoidingView layout (native) app/ App domain components app-screen-layout.tsx Scrollable content layout (web) app-screen-layout.native.tsx Native scroll layout lib/ auth-client.ts better-auth client with Expo plugin api-client.ts Hono RPC client hooks/ use-session.ts Typed session hook constants/ index.ts App constants from environment variables src/ global.css Tailwind v4 CSS imports and platform fonts tw/ index.tsx CSS-wrapped React Native components image.tsx CSS-wrapped expo-image component Components are organized by domain module, not by type:
components/ui/-- Generic, reusable UI primitives shared across the entire app (buttons, inputs, modals, cards, etc.). Only truly cross-cutting components belong here.components/<domain>/-- Domain-specific components grouped by feature module. Each module owns its layouts, guards, and feature components. Examples:auth/ownsauth-guardandauth-form-layout;app/ownsapp-screen-layout.- Platform variants use the
.native.tsxsuffix (e.g.,auth-form-layout.native.tsxfor iOS/Android,auth-form-layout.tsxfor web). Metro/bundler auto-resolves the correct file.
When adding new features, create a new folder under components/ (e.g., profile/, settings/, onboarding/) and place all related components there.
| Variable | Required | Description |
|---|---|---|
EXPO_PUBLIC_API_URL | Yes | Backend API base URL (e.g. http://localhost:3000) |
Clone the repository and enter the directory:
git clone https://github.com/rutzuu/z0-native-app-fe.git cd z0-native-app-feCopy the environment template:
cp .env.example .env
Set
EXPO_PUBLIC_API_URLtohttp://localhost:3000- For physical device testing: replace
localhostwith your machine's local network IP (e.g.http://192.168.1.x:3000) — the device must be on the same WiFi network
- For physical device testing: replace
Install dependencies:
pnpm install
Start the development server:
pnpm web # Browser pnpm start # Expo dev server (native + web) pnpm ios # iOS simulator pnpm android # Android emulator
- Make sure the backend is running at
http://localhost:3000(see the backend README) - Open the app (web or native) — you should be redirected to the login screen
- Navigate to the register screen and create a new account
- A successful redirect to the home screen confirms the frontend is correctly communicating with the backend
- In parallel, open
http://localhost:3000/docsin a browser to test the same endpoints via Swagger UI
- CORS error in browser: Confirm
FRONTEND_URLin the backend.envexactly matches the origin the browser shows (including port) - Network error on Android emulator: Use
http://10.0.2.2:3000instead oflocalhost(10.0.2.2 is the emulator's alias for the host machine) - Network error on physical device: Use your machine's LAN IP instead of
localhostinEXPO_PUBLIC_API_URL - Auth session not persisting: Confirm
BETTER_AUTH_URLin the backend matches the actual URL the frontend is calling — a mismatch causes cookie domain issues - Styles not applying: Ensure
@/src/global.cssis imported inapp/_layout.tsxand the Metro config haswithNativewindapplied. Restart the dev server after changes to the CSS setup.
This project includes a Hono RPC client in lib/api-client.ts that can provide end-to-end type safety with the backend.
The backend exports an AppType from src/app.ts. To use it:
Option A — Copy types: Copy the
AppTypetype definition from the backend and paste it into the frontend. Quick but requires manual updates.Option B — npm/pnpm workspace: If using a monorepo, add the backend as a workspace dependency and import
AppTypedirectly.Option C — Shared types package: Publish a shared types package that both repos depend on.
Update the import in lib/api-client.ts once you choose an approach:
importtype{AppType}from"z0-native-app-be/src/app";import{hc}from"hono/client";import{API_URL}from"@/constants";exportconstapi=hc<AppType>(API_URL,{init: {credentials: "include"},});- Connect your GitHub repo to Vercel
- Set the build command:
pnpm build:web - Set the output directory:
dist - Add environment variable:
EXPO_PUBLIC_API_URL= your deployed backend URL - The included
vercel.jsonhandles SPA rewrites automatically
- Connect your GitHub repo to Railway
- Railway's Railpack builder will auto-detect the project
railway.jsonconfigures the build and serves the static export withserve- Add environment variable:
EXPO_PUBLIC_API_URL= your deployed backend URL
The included eas.json defines three build profiles:
| Profile | Distribution | Use Case |
|---|---|---|
development | Internal | Development builds with dev client |
preview | Internal | Testing builds for team members |
production | Store | App Store / Play Store releases |
# Development build eas build --profile development --platform ios eas build --profile development --platform android # Preview build eas build --profile preview --platform ios eas build --profile preview --platform android # Production build eas build --profile production --platform ios eas build --profile production --platform androideas submit --platform ios eas submit --platform androidBefore submitting, update EXPO_PUBLIC_API_URL in the production profile of eas.json to point to your deployed backend URL.
| Script | Description |
|---|---|
pnpm start | Start Expo dev server |
pnpm web | Start for web browser |
pnpm ios | Start for iOS simulator |
pnpm android | Start for Android emulator |
pnpm build:web | Export static web build to dist/ |
pnpm lint | Run ESLint |
pnpm format | Format code with Prettier |
MIT