The Web Comes First: Why We Built ZFORB in the Browser

Every travel company is expected to open with an app. We chose differently: ZFORB was built web-first, and everything the platform does — search, membership, redemptions, the concierge — works in any browser today, on any device, with nothing to install. That was a decision, not a delay, and it deserves an explanation.

Travel is an occasional relationship

The apps that earn a place on a home screen are daily ones. Travel is not daily. It arrives in bursts — planning weeks, booking evenings, the trip itself — separated by quiet months. Software for that rhythm should be instantly available when the burst arrives and invisible in between. The browser is precisely that: no download standing between intention and a booking, no stale version from last year's trip.

One platform, every screen

Web-first also means the platform is identical everywhere — the laptop where itineraries get planned, the phone at the airport, the tablet on the sofa. Improvements ship to everyone the moment they ship, not when an update is approved and installed. For a platform that improves weekly, that immediacy compounds.

What the app is for

The web came first. The app followed, and the ZFORB app is now on the App Store, built the same way we choose hotels: only where it genuinely adds. It lives in the moments a phone is naturally in hand — finding a stay on the move, your trips and stay details, the concierge a tap away. An Android edition follows on Google Play.

What the app will never be is a requirement. The browser remains a first-class citizen, because your access to what you have paid for should never depend on an install. One account works across both.

The entire ecosystem is still one address away, and now one tap as well. That, we think, is what "it just works" is supposed to mean.