2026-03-08 · 5 min read
Expo + shared APIs for a production mobile app
How the Nadriverzum Expo app shares backend canisters with the web client, and why wallet tools stayed on the website.
The problem
A mobile app drifts as soon as it grows a private copy of profiles, chat, or community data. Web and device then disagree about who a member is and which message is newest.
One Candid surface
On Nadriverzum the React site and the Expo app both connect to the same decentralized backend canisters. Profiles, community hubs, classifieds, and chat share consistent APIs rather than duplicating backend services for the phone.
The decision was to keep complex wallet and staking interactions on the web, where browser-based decentralized identity unlocks them. The Expo app covers discovery, messaging, and community storefronts without unnecessarily reimplementing heavy token flows.
Notifications on top of the same chat
The phone still needs a nudge when someone sends a message. The Expo client polls the existing conversation API and, when the latest message is from the other person, schedules a local notification. Opening it routes back to that thread.
That keeps notifications as a client behavior. Chat history remains the canister's data.
The pitfall
The expensive mistake is a mobile-only payload that the Candid type does not have. Encode the same actor arguments the web already sends. If a flow needs a heavier session, such as staking, leave it on the web instead of approximating it on the device.
Related case studies
- Nadriverzum — A web and mobile community platform for member discovery, classifieds, messaging, and local commercial connections.