Dali Wears — Mobile App
In progressMobileThe React Native app for the Dali Wears store, sharing its Supabase backend and paying through Paystack's hosted checkout.
Role
Mobile Developer (Solo)
Status
In development
Category
Mobile
Screenshots
Overview
A React Native (Expo) app for the Dali Wears store at daliwears.shop. It has no backend of its own: it uses the same Supabase project as the website for accounts, products, orders, chat, and rewards, and calls the website's Paystack endpoints to start and verify payments. Customers browse products with photos, videos, sizes, and discounts, check out with Paystack, track their deliveries, chat with the store, and earn coins through daily check-ins, streaks, and referrals.
The problem
Dali Wears customers mostly shop from their phones and wanted an app, but a second backend just for mobile would double the work and let the app and website drift apart.
The solution
A React Native app that reuses what the website already has: the same Supabase project for data and accounts, and the website's Paystack endpoints for payments. It's shipped as an installable Android APK built with EAS Build.
What it does
Paystack in the app
The app asks the server to start a payment, opens Paystack's hosted checkout in an in-app browser, returns via a deep link, then asks the server to verify the payment before confirming the order.
Coins & referrals
A wallet screen for daily check-ins, 7-day streak bonuses, coin history, and entering a friend's referral code (also accepted at sign-up).
Shop & track
Products with photos, videos, sizes, discounts, and pre-orders, plus a cart, wishlist, and step-by-step order tracking.
Chat & notifications
Message the store and see announcements about new arrivals.
How it's built
- React Native + Expo + TypeScript, developed on Expo Go and built for Android with EAS Build.
- React Navigation with bottom tabs and native stacks.
- Supabase client with AsyncStorage sessions — same project and row-level security as the website.
- Postgres functions (daily_checkin, apply_referral_code) for rewards logic, so the rules live in the database.
- Calls the website's /api/paystack-initialize and /api/paystack-verify routes; expo-web-browser auth sessions handle the payment page and deep-link return.
Challenges & how I solved them
Paystack without a popup
Paystack's inline popup only works in a browser, so I added a server endpoint that creates a hosted checkout session (after checking the amount against the order). The app opens it in an auth session and the server verifies the result.
Keeping secrets out of the app
Anything bundled in an app can be extracted, so the Paystack secret key stays on the server. The app only calls the website's API routes.
Key highlights
- Built Paystack checkout with a server-initialized hosted payment page, opened in an in-app browser and returned through a dalimobile:// deep link
- Verified every payment on the server through the website's API — the app never treats the browser result as proof of payment
- Built a coins wallet with daily check-ins, streak bonuses, and referral codes using Postgres functions (RPC)
- Added order tracking, product videos (expo-video), sizes with a size guide, discounts, and pre-orders
- Compressed review photos on the device (expo-image-manipulator) before uploading to Supabase Storage
- Set up EAS Build for installable Android APK distribution
What's next
- Publish to the Google Play Store
- Prepare an iOS release