AptLok Mobile
An Expo and React Native client designed for shared phones, weak signal and people who have never used a society app.
The problem
The people who most need access to the community platform, such as gate security staff and residents approving deliveries, are the least likely to be at a laptop, on weak signal and often on shared phones.
What needed to be done
Design and ship an Android client on the same Laravel API, with one specification serving as the source of truth for web and mobile.
How the right problem was found
I started from the users with the least tolerance for friction: a watchman with one hand free and residents who have never used a society app. That drove ten decisions, including role selection after login, OTP instead of Google sign-in, visitor pre-approval, a one-handed watchman module, per-device push tokens, secure on-device credential storage, camera capture, over-the-air updates and separate navigation for signed-in and anonymous users.
The outcome, measured
A signed Android release, v1.1.0, built and shipped. Gate registers are digital at the point of use, visitors can be pre-approved, notices arrive as push notifications and rentals can be browsed without an account.
- v1.1.0
- Release
- 10
- Design decisions documented
- Android
- Platforms