Case study · BBW Multi-Skills Ltd
Prezpa
Your business profile, prices and work, shared by QR. Clients book on WhatsApp.

- Role
- Founder & Full-Stack Engineer (solo: product, design, engineering, release and support)
- Timeline
- Development started 9 September 2026. Approved and live on Google Play in October 2026, about 6 weeks to launch. Ongoing updates since.
- Platforms
- Android app (Google Play), the same app on the web, a marketing website, and an internal admin portal
- Status
- Live
TL;DR
The problem
Nigerian small businesses sell through WhatsApp and Instagram, so their prices and work are scattered across chats, and clients keep asking “how much?”
What I built
One professional profile, shared by a QR code, link or NFC card, that any client can open in a browser and book from on WhatsApp.
The result
I took it from idea to a live Google Play app, web app, marketing site and admin portal in about 6 weeks, working solo.
Overview
Prezpa gives small businesses and service providers a single, professional home for their business: who they are, what they offer, what it costs and what their work looks like. They share it as a QR code, a link (prezpa.app/u/username) or an NFC card. Their clients open it in any browser, with no app to install, and tap one button to book on WhatsApp.
The problem
Small Nigerian businesses and service providers, such as nail technicians, lash technicians, photographers, cinematographers and installers, sell mostly through WhatsApp and Instagram.
- Their prices, past work and contact details are scattered across chats, statuses and DMs.
- Clients ask “how much?” again and again.
- There is no single, professional link or QR code to share.
Who it’s for
- Business owners create and manage the profile in the app.
- Their clients view it in any browser, with no app needed, and book on WhatsApp.
My role
Founder & Full-Stack Engineer. I owned Prezpa end to end, from the idea to a live Google Play app with real users.
01
Product & design
- Defined the product for Nigerian small businesses: profile, ₦ pricing, portfolio, QR/NFC sharing and WhatsApp booking.
- Designed the user flows: sign-up, onboarding, profile building, sharing and the client booking view.
- Designed the visual system: dark-first, a neon-green accent, Sora and Inter type, and bottom sheets for quick actions.
- Made the product decisions: sign-up in the app only, the web for viewing and logging in, and a centred phone layout on laptops and tablets.
02
Database & backend
Supabase / PostgreSQL
- Designed the database schema: profiles, services and specialties, portfolio, links, analytics events, referrals, support tickets and messages, push tokens, reports, moderation and legal acceptances.
- Wrote the security model: Row-Level Security on every table, plus security-definer functions for sensitive actions, so each user can only ever reach their own data.
- Wrote 37 versioned migrations and 20 pgTAP test files covering permissions and business rules.
- Built the Edge Functions (Deno): view, scan and WhatsApp-tap tracking; account deletion; content moderation; support push notifications; health checks.
- Set up Storage: public portfolio images, and private support attachments served through expiring signed links.
- Built Nigerian phone handling: every format is normalised to one international number in both the app and the database.
03
Mobile & web app
Expo / React Native / TypeScript
- Built the Android app and the web app from one codebase with Expo Router and React Native Web.
- Wrote web-specific versions where browsers differ: dialogs, sharing, QR saving and photo processing, including a multi-photo upload fix.
- Built the camera and gallery photo flow (crop, multi-select, tagging), QR and NFC sharing, activity tracking, and the support chat with real-time updates.
- Added push notifications using Expo and Firebase Cloud Messaging.
04
Admin portal & marketing site
React / Vite
- Built the marketing site with live, admin-editable content.
- Built the internal admin portal with two-step sign-in (password plus authenticator app). Two workspaces: a real-time support inbox (reply, resolve, close, photo replies) and a website content manager.
05
DevOps, release & quality
- Hosted everything on Cloudflare at prezpa.app, with email routing for support@prezpa.app.
- Ran reproducible, signed Android release builds locally when the cloud build quota ran out, keeping signing secrets out of files.
- Shipped to Google Play: store listing, screenshots, Data Safety, review and production release. Then handled the Play Console quality warnings: code shrinking (R8), and Android 16 large-screen and orientation support.
- Set up Sentry error monitoring, an enforced 150-line file limit for maintainable code, type checking and tests before each release.
06
Support & iteration
- Answered users through the in-app support chat.
- Fixed real issues reported on users’ phones, such as sheets hidden behind the navigation bar on small phones.
- Diagnosed production-only bugs, such as push notifications that silently reached no one because of a database permission difference between local and hosted environments.
How I worked
I used AI pair-programming (Claude Code) to speed up implementation, while I owned the product decisions, architecture, reviews, testing on real devices and releases.
Features & user journey
Feature 01
Business profile
Name, username link (prezpa.app/u/username), logo and cover, services (up to 3 categories), and an “Open for bookings” availability switch.

Step 01
Welcome: “Your business, one tap away”
Step 02
Business name and username
Step 03
“What services do you offer?” (pick up to 3)
Step 04
“Make it recognisable”: logo and cover
Step 05
“Your WhatsApp number” (+234)
Step 06
Optional links such as a website (“you can change these anytime”)
Step 07
“You’re live!”
Then: add services and ₦ prices, portfolio photos (camera or gallery, crop, tag by service), links and availability.
Feature 02
Sharing
A QR code to save or share, the profile link, and writing the profile to an NFC card.
Step 01
Open the QR code
Step 02
Save or share it, copy the link, or write it to an NFC card
Feature 03
A client books (web, no app)
Clients see everything in their browser and tap “Book on WhatsApp”.
Step 01
Scan the QR code or open the link
Step 02
See the work, services and prices
Step 03
Tap “Book on WhatsApp”
Step 04
WhatsApp opens with the business
The client can also report a profile.
Feature 04
In-app support chat
Pick a topic, attach photos, get real-time replies, and receive a push notification when support replies.
Step 01
Settings → Support
Step 02
Choose a topic
Step 03
Send a message or photo
Step 04
Support replies from the admin portal
Step 05
The owner gets a push notification; tapping it opens the chat
Also in the app
- Services and prices in Naira (₦)
- Portfolio of up to 12 photos
- WhatsApp, website and social links
- Activity: views, QR scans, WhatsApp taps
- Testimonials and referrals
- Report, block and moderation
- Account management
- Web login
- Light and dark theme
Design approach
- Mobile-first and dark-first, with a neon-green accent on near-black.
- Type: Sora for display, Inter for body text.
- Bottom sheets for quick actions instead of full-screen forms, so common tasks stay fast.
- One phone-sized layout everywhere. On laptops and tablets the app shows as a centred, phone-width column rather than stretching.
- Built for Nigeria: ₦ pricing, +234 WhatsApp numbers checked against real mobile prefixes (70, 71, 80, 81, 90, 91), and WhatsApp as the booking channel.
- Accessibility basics: labelled buttons, clear error messages and large touch targets.
- Sign-up is app-only. The website explains how to get the app, and existing users can log in on the web.
System design
The Android app, the web app, a client’s browser and the admin portal are the clients. Cloudflare Workers at prezpa.app serve the web app, the public profile and the admin portal. The apps talk to Supabase: Auth with email codes, Postgres with Row-Level Security on every table, Storage, Realtime for support chat, and Edge Functions in Deno. Views, scans and taps from a client’s browser go to Edge Functions, which write to Postgres and send push notifications through Expo Push and Firebase Cloud Messaging to the owner’s phone. The admin portal reaches the database with a two-step verified session. The apps report errors to Sentry.
Stack and why
- Expo (SDK 57), React Native, Expo Router
- One TypeScript codebase for the Android app and the web app (via React Native Web), with file-based routing. Web-specific behaviour lives in
.web.tsfiles where the platforms differ. - Supabase (PostgreSQL)
- Email authentication with codes; Row-Level Security on every table; security-definer functions for sensitive actions; Storage with private buckets and signed links; Realtime for the live support chat; Edge Functions (Deno) for tracking, account deletion, moderation, push notifications and health checks.
- Cloudflare (Workers static assets)
- Hosts prezpa.app: the marketing site, web app and admin portal on one domain. Cloudflare Email Routing provides support@prezpa.app.
- Vite and React 19
- The marketing site and admin portal (multi-page). Website content is edited live from the admin without a redeploy.
- Expo push notifications over Firebase Cloud Messaging (V1)
- Notifies owners when support replies.
- Sentry
- Crash and error monitoring.
- Testing
- 20 pgTAP database test files covering security rules and functions, plus unit tests and TypeScript type checking.
- House rule
- No source file over 150 lines, enforced by a script before every commit, to keep code modular.
Database design
Everything centres on profiles. A profile offers up to three profile_services, each picked from service_categories and services (or a custom name), with optional specialties in profile_service_specialties, prices in profile_offerings, and portfolio_photos tagged by service. A profile has profile_links to social_platforms. Activity is stored per profile in profile_views, scan_events and whatsapp_taps, rolled up into analytics_daily, with read state in profile_activity_state. A profile owns one referral code, and referrals record who joined with it. Profiles open support_tickets, each with a thread of support_messages. For safety, content_reports can target a profile or a photo, moderation_actions follow from reports, and user_blocks record blocked profiles.
Hard problems I solved
01Push notifications sent to nobody
- Problem
- Everything worked locally, but in production, support replies produced no notification.
- Investigation
- I traced every hop. The phone had registered. A direct test through Expo delivered. The server function ran but reported “sent: 0”. The cause: hosted Supabase does not give the server role table access by default, while local setups do.
- Fix
- A migration granting exactly the access needed, plus a test to stop it regressing.
- Result
- Notifications delivered.
02Making a native app work properly on the web
- Problem
- Native alerts, the file system and image tools do not exist in browsers.
- Investigation
- Multi-photo upload also failed in browsers with a “createImageData” error.
- Fix
- Web-specific versions for confirm dialogs, sharing, QR saving and photo processing. For uploads, each image is decoded once and re-encoded at the target size.
- Result
- These actions, including multi-photo upload, work in the browser.
03Admin security and live support
- Problem
- The admin portal holds user support conversations, so it has to be locked down and stay live.
- Investigation
- Long chats scrolled the whole view, pushing the header and message box out of reach.
- Fix
- Two-step verification for admins, enforced in the database rules (session level aal2), not just in the interface. A real-time inbox. A layout where long chats scroll while the header and composer stay fixed.
- Result
- Admins must pass two-step verification to reach admin data, and the inbox updates live.
04Reliable release builds
- Problem
- The free cloud build quota ran out.
- Investigation
- Local builds were blocked by OneDrive file locks and an editor extension that broke Gradle builds.
- Fix
- Reproducible local signed builds, with signing passwords passed only through environment variables, never written to files. Resolved the file locks and the extension conflict.
- Result
- Signed release builds run locally, with no secrets in files.
05Play Console quality warnings
- Problem
- Google Play Console flagged quality warnings.
- Investigation
- Code shrinking was off, and the manifest portrait lock is ignored by Android 16 on large screens.
- Fix
- Turned on code shrinking (R8), with a mapping file for crash reports. Replaced the manifest lock with a phone-only runtime lock and a centred layout for tablets and foldables.
- Result
- A smaller app, readable crash reports, and correct behaviour on large screens.
06Real-device feedback
- Problem
- Users on smaller phones reported that bottom sheets hid buttons under the navigation bar.
- Investigation
- Short sheets were not sized to their content, so on small screens their buttons ended up under the system navigation bar.
- Fix
- Short sheets now size to their content.
- Result
- Buttons stay visible on small phones.
07Nigerian phone numbers
- Problem
- People type the same number in different formats: 0810…, +234 810… and 810….
- Investigation
- WhatsApp booking needs one consistent international format, and numbers should match real Nigerian mobile prefixes.
- Fix
- Every format is normalised to one international format, in both the app and the database, and checked against real prefixes.
- Result
- Every saved number is in the same international format.
Deployment and maintenance
- One command deploys prezpa.app to Cloudflare.
- Database changes ship as versioned migrations; server functions are deployed separately.
- Android releases are signed AABs on the Google Play production track, with an internal testing track first.
- Errors are monitored in Sentry; user feedback arrives through in-app support and “Report this profile”.
Outcome and impact
- Approved by Google and live on Google Play in October 2026, about 6 weeks after development started.
- Web app, marketing site and admin portal live at prezpa.app.
- First update shipped based on real user feedback: support notifications, small-phone and tablet fixes, and a smaller app.