Idara Etim
Back to work

GetGigs — Mobile App

In progressMobile

The React Native companion app for GetGigs, sharing one Supabase backend with the website.

Role

Mobile Developer (Solo)

Status

In development

Category

Mobile

Screenshots

Screenshots coming soon

Overview

A React Native (Expo) client for GetGigs that talks to the same Supabase project as the web app — no separate backend. Currently at MVP: sign in/up (email and Google), discovering and searching nearby providers with device GPS, provider profiles, requesting a service with photos and location, a realtime messaging thread, in-app notifications, and profile management. Feed/stories, provider onboarding, the business dashboard, admin tools, job postings, and device push notifications are web-only or not yet built on mobile.

The problem

Most GetGigs customers are on their phones, often while the problem is right in front of them — a leaking pipe or a faulty socket. They need to find a nearby provider, show them the problem, and talk to them quickly, which is clumsy on a mobile browser.

The solution

A native mobile app built with React Native and Expo that uses the phone's GPS to find nearby providers, lets customers attach photos to service requests, and keeps the conversation going with realtime chat — all on the same Supabase backend as the website, so accounts and data carry across.

What it does

Email & Google sign-in

Customers sign up or log in with email/password or Google, using the same Supabase Auth accounts as the GetGigs website.

Nearby provider discovery

Uses device GPS via expo-location to surface providers close to the customer, with search and full provider profiles.

Request a service with photos

Customers describe the job, attach photos from the camera or gallery, and include their GPS position or Local Government Area.

Realtime messaging & notifications

A conversation list and live message thread powered by Supabase Realtime, plus in-app notifications and profile management.

How it's built

  • React Native with Expo and TypeScript, developed and tested on real devices with Expo Go.
  • React Navigation for stack and tab navigation; NativeWind brings Tailwind-style styling to native components.
  • Talks directly to the GetGigs Supabase project — same schema, same RLS policies, same auth — so there is no separate mobile backend to maintain.
  • Supabase Realtime subscriptions keep chat threads updated live without polling.
  • expo-location for GPS and the image picker for photo uploads to Supabase Storage.

Challenges & how I solved them

Avoiding a second backend for mobile

Because the website's security lives in Postgres row-level security rather than in web-only API code, the mobile app could safely use the same Supabase project directly — the same rules protect both clients.

Location that works for everyone

GPS isn't always available or accurate, so service requests accept either the device location or a manually selected LGA.

Key highlights

  • Built sign in/sign up with email+password and Google auth
  • Implemented nearby-provider discovery using device GPS (expo-location)
  • Built a request-service flow with photo upload and GPS/LGA location
  • Added realtime messaging (conversation list + live thread) on top of Supabase Realtime
  • Shared the same Supabase schema and auth as the GetGigs website — no separate backend

What's next

  • Device push notifications
  • Provider onboarding and dashboard on mobile
  • Feed/stories, job postings, and business tools to match the website

Tech stack

React NativeExpoExpo GoTypeScriptNativeWindReact NavigationSupabaseSupabase Realtimeexpo-location