One API. Two mobile apps. A connected booking platform.
The architectural questions behind connecting VillaHub’s web platform with iOS and Android.
Permissions belong on the server
A role-specific dashboard helps people find the right tools. It does not, by itself, provide access control. Hiding a finance link in a guest interface cannot prevent someone from requesting the underlying endpoint.
For a multi-role product, authorization needs to consider both the action and the resource: who is requesting it, which booking or property it affects, and whether that person is allowed to make that change. Every client benefits when those rules have one authoritative implementation.
Treat responses as a contract
Web and mobile releases do not always happen together. A website can ship a change immediately, while an installed mobile application may remain on an older version. Response shapes, error codes, pagination, and field semantics therefore need predictable behavior.
Additive changes are often easier to introduce safely than renaming or removing existing fields. A useful review question is: what happens when yesterday’s app calls tomorrow’s API?
Shared code still needs platform testing
React Native can share application code across iOS and Android, but release behavior still depends on each platform. Navigation, keyboard handling, permissions, and network interruptions deserve checks on both.
The useful outcome of a shared architecture is consistency in the product’s rules, together with room for each interface to work naturally. The VillaHub case study describes the delivered scope; these notes explain the broader design considerations rather than exposing private implementation details.
Context: the published project scope. The design considerations in this article are general guidance, not a disclosure of private implementation details. VillaHub — View case study.