01 / Mobile app
Connect to a personal account
As a returning member, I want a clear route back into my community.
The native sign-in screen provides the account entry point, with a separate registration journey for new members.
All workSelected work / 09
Interface studyBelievers Map
01 / Context
The idea
A native mobile app for discovering places of worship, reading scripture, and exploring community. Its tab-based structure connects nearby discovery with recurring faith practices.
My contribution
Lead Developer
Freelance
Built with
Expo · React Native · Firebase · NativeWind
Platforms
iOS · Android
Inside Believers Map
Product walkthrough02 / The problem & the approach
What the experience needs to solve
Location discovery, daily reading, and community are related needs, but they require different interfaces. A mobile app needs to make each one easy to return to.
The approach
The app gives home discovery, readings, and community their own tabs, while account onboarding establishes a personal starting point.
The story, screen by screen.
03 / User journeys02 / Mobile app
Start with discovery
As a user, I want a starting point for exploring places of worship and community.
The home screen introduces discovery within the mobile app’s persistent navigation.
03 / Mobile app
Return to daily reading
As a user, I want scripture, readings, and sermon audio in a predictable place.
A dedicated readings tab collects these recurring activities outside the location-discovery flow.
04 / Mobile app
Explore community
As a user, I want to find faith and community activities without losing my place in the app.
The community tab gives that activity its own destination alongside discovery and readings.
04 / Behind the interface
Engineering the experience
Expo and React Native provide native mobile screens; Firebase carries identity and user data.
Separate tabs keep discovery and reading tasks accessible without repeatedly returning through a long navigation stack.
The current login screen displays a Forgot Password control whose handler is not implemented; the case study does not claim completed recovery support.
Editorial
