A cross-platform app, from one codebase.
A cross-platform app for iOS and Android, built in React Native from a single codebase. It carries the same developments as the website — Hadley Heights, Weybridge Gardens and Cavendish Square — so a buyer who first saw a launch page finds the same units, the same photography and the same enquiry routes on their phone rather than a thinner version of the site.
- Platforms
- iOS & Android
- From one build
- Framework
- React Native
- One shared codebase
- My role
- Design & build
- Interface through to delivery
- Screens shown
- 5
- Walked through below
The website already sold well. The app had to carry that restraint into something people operate rather than read.
- 01
The buyer is often not in the country
Off-plan is frequently bought at a distance, so the app has to stand in for a site visit: the renders, the unit mix and the size range have to be legible on a phone, and the route to a human has to be one tap from whatever the buyer is looking at.
- 02
Two platforms, one small team
Separate native builds would have meant two codebases, two release cycles and two sets of bugs for the same screens. React Native keeps one component tree and one place to fix anything, which is what makes a two-platform app viable without a two-platform team.
- 03
Nothing may contradict the website
The same three developments, the same photography and the same enquiry destination. A buyer moving between the site and the app should never see two different answers to the same question, because the moment they do, both stop being trustworthy.
Screen by screen, and why each one is built that way.
- 9:41
01 / 05·Sign inAn account is offered, not demanded.
The first decision is whether to make anyone sign in at all. Most first visits to a property app are browsing, not buying, so a wall in front of the developments loses the people it is meant to qualify. Continue as guest sits directly under the login button, at the same weight — an account is offered, not demanded.
Guest browsing by default - 9:41
02 / 05·HomeOne development leads, not a grid.
A single featured development leads, not a grid. One building with its location, unit mix and size range answers more than six thumbnails do, and Enquire Now and Call Us Now sit on the card itself rather than behind a menu — the two actions a serious buyer wants are never more than one tap from what they are looking at.
Actions sit with the content - 9:41
03 / 05·DevelopmentsThe full portfolio, one card per building.
The full portfolio, one card per development, each carrying its own entry price. Price on the card rather than behind a tap is deliberate: it filters early, which costs some browsing and produces better enquiries. The same three developments the launch pages cover, so nothing contradicts the website.
Price on the card, not behind a tap - 9:41
04 / 05·MenuA slide-over, not a tab bar.
Developments, investments, the LEOS Hub and news, as a slide-over rather than a tab bar — five destinations of uneven importance do not divide well into equal tabs. Log out sits at the bottom in the accent colour, visible rather than buried in a settings screen two levels down.
Weighted, not evenly split - 9:41
05 / 05·EnquireFour fields, and nothing else.
Name, email, phone and a message. Every extra field on a property enquiry costs completions, and the ones that matter for a first conversation are how to reach someone and roughly what they want. Qualification happens on the call, not in the form. It is reachable from every development card, so nobody has to navigate back to a contact page to act on what they are looking at.
Reachable from every card
What I handled on this project.
Design
- Interface design for the screens shown here
- Platform-appropriate navigation: slide-over rather than a tab bar
- Sign-in that offers an account without requiring one
Build
- React Native, one codebase for iOS and Android
- Shared components across every screen
- Development data matched to the website, so the two cannot drift
Enquiry path
- Four-field enquiry form, reachable from every development card
- Enquire and call actions on the content rather than behind a menu
What it changed.
1
Codebase for both platforms
One component tree to build, fix and maintain, rather than two.
Enquiries per month from the app and Time to first response are deliberately absent. One figure a client can verify is worth more than three they cannot, so nothing goes here until the number is real.
Have a project in mind? Let's start it.
Whether it's a paid campaign, a website or app, or ongoing design and social support — tell me what you need and I'll get back to you with next steps.