Tenant in Ibadan taps a listing. Bids flood in from agents, each with fees laid bare—no smoke, no mirrors.
That’s Ilere, the transparent rental marketplace crashing Nigeria’s opaque housing game in cities like Lagos, Abuja, Port Harcourt. Built on Expo for the mobile frontend and Supabase as the backend muscle, it’s not just another listing app. It forces competition into the shadows where agents hike “service charges” at whim. Zoom out: Nigeria’s rental market chews up 30-50% of tenant income (World Bank data), riddled with off-app deals and ghost fees. Ilere drags that into the light.
Codebase screams intention. Tenants browse, bid flows activate, chats spin up—all enforced by database rules and hooks. Agents post, landlords list direct. Push notifications ping new offers. It’s opinionated, workflow-bound, real.
Expo Router: Navigation That Mirrors the Product
File-based routing in src/app. Clean. (auth) group for sign-in. (tabs) for the core shell. house/[id].tsx drills into details, bids at request/[id]/bids.tsx, chats at chat/[id].tsx. No bloat.
Here’s the shell in src/app/_layout.tsx: loads fonts, QueryClient, hydrates auth via authService.getCurrentUser(), subscribes to changes, toast host. Straightforward. Good.
State? Split smart. Zustand just for user, loading flags, password reset. Rest—houses, bids, chats, notifications—server state via React Query. Why? Supabase realtime subscriptions mutate data underfoot. Client stores? Recipe for sync hell.
The service layer uses relational selects heavily. housesService.getHouses() joins house_photos and the posting user in one round trip, while src/services/supabase/chat.ts loads both participants plus recent messages and derives last_message and unread_count on the client.
Supabase shines here, less raw DB, more query surface.
Why Does Ilere’s Bid Flow Actually Work?
Open a house. Local fee breakdown computes—rent, agent cut, whatever. Direct landlord? Skip bids. Else, useCreateRequest() fires. Backend checks availability, blocks duplicates, handles races on unique constraints.
Pick winner? requestsService.selectBid() updates, marks accepted, grabs agent, spins chat. Business logic layered: screen to hook to service to Supabase. No leaks.
Defensive. authService.onAuthStateChange() dodges deadlocks with setTimeout(…, 0). housesService.getHouses() sanitizes search: trims, strips junk, .or() filters. Debounce at 350ms on home screen. useInfiniteQuery keeps it snappy, no backend thrash.
Supabase client? Typed, AsyncStorage auth persist, auto-refresh. Services own queries: src/services/supabase/*.
Can Expo and Supabase Scale Nigeria’s Chaos?
Market dynamics: 20 million urban Nigerians hunt rentals yearly (est. from NBS housing stats). Agents control 80% (local reports), fees arbitrary—10-20% gouges common. Ilere bids commoditize that. Tenants choose lowest. Agents sharpen or starve.
Tech fits. Expo Router scales to complex flows without Redux sprawl. Supabase realtime? Chats, bids update live. PostgREST joins cut roundtrips. But limits? Free tier caps at 500k rows—fine for MVP, but Lagos alone could spike. Edge functions for heavier logic ahead?
My take: bullish, but watch concurrency. Nigeria’s 4G patchy; offline-first via AsyncStorage auth helps, but saved homes, drafts? Untapped.
Unique angle—echoes M-Pesa’s 2007 Kenya launch. Opaque mobile money? Safaricom transparently bid carriers down, agents proliferated. Ilere could spawn agent networks, not kill ‘em. Prediction: by 2026, 10% Lagos rentals via such platforms, fees drop 15%. (Parallel: India’s NoBroker shaved 20% via direct connects.)
Hype check: not corporate spin. Open source code reveals pragmatism—race guards, sanitizers—not vaporware.
The Hidden Wins in Ilere’s Service Layer
services/supabase/houses.ts: getFeeBreakdown() local math on fetched data. requests.ts: createRequest() rejects landlord bids, refetches on constraint fails.
chat.ts derives unread_count client-side. Efficient.
Push notifications? Registered in layout. In-app too.
Block/report? Baked in.
Workflow boundaries: DB enforces no dup requests, bid acceptance chains chat create. Frontend can’t cheat.
What Happens When Agents Fight Back?
They will. In-app coordination kills side deals. But data wins: explicit breakdowns build trust. Tenants save homes, compare bids cross-listing.
Risk: agent exodus to WhatsApp shadows. Counter: realtime edges it—bids update live, chats persist.
Broader: proptech Africa lags. Jumia Houses flopped on opacity. Ilere’s stack—lightweight, fullstack Postgres—blueprint for 100 clones.
Numbers: Supabase handles 100k+ concurrent (their benchmarks). Expo deploys fast, OTA updates dodge app store friction.
Sharp position: this makes sense. Not if you’re a fat-cat agent. For tenants, builders? Gold.
🧬 Related Insights
- Read more: Pinterest Crushes Spark OOMs by 96% – Finally Fixing a Decade-Old Headache
- Read more: Why Solana Frontend Development Is Finally Getting Easier (And Why It Still Trips Up Most Developers)
Frequently Asked Questions
What is Ilere rental marketplace?
Mobile app for Nigerian cities letting tenants get competitive agent bids with transparent fees on Expo and Supabase.
How does Ilere use Supabase for realtime bids?
Realtime subscriptions update bids, chats, notifications; services layer with joins and mutations enforce workflows.
Can Ilere expand beyond Nigeria?
Yes—stack portable, but tune for local agent norms and data volumes.
