Today, travelers access information on the go, at any time, and across a multitude of devices. A question therefore comes up regularly: should you invest in a website, develop a mobile app… or both?
Behind this question lie some very concrete challenges:
- Limiting costs while ensuring reliable information
- Meeting the actual needs of travelers
- Avoiding the proliferation of tools
- Offering the best possible experience, whether the traveler is a regular or an occasional user.
While the website remains the first port of call for many travelers, mobile apps provide a level of proximity and responsiveness that is difficult to achieve otherwise. So, how do you choose? And how do you ensure that every investment truly meets real-world needs?
First and foremost: Don't confuse the platforms
In the collective imagination, we still too often associate:
- Website = computer,
- Mobile app = smartphone.
In reality:
- A mobile app, yes, is obviously used on a phone (and on a tablet too, for that matter);
- A website, on the other hand, can be viewed on any device : computer, tablet… and of course, smartphone.
This distinction is not trivial. It helps to understand the logic that follows:
the choice between a website and an app is not a matter of “computer” versus “mobile”, but rather two different user experiences.
The website: accessible to everyone, no installation required
The website of a transport network is a passenger information channel open to everyone. Accessible from any connected device, it requires no installation—a simple web browser is all you need. Passengers don't need to download an app to check schedules or plan a route: with just a few clicks on the network's site, they have immediate access to the information they need.
Furthermore, a website makes it easy to publish all official content: maps, schedules, fares, etc. It is often the first place people go to discover a network or plan a trip. It remains an essential resource for getting information before traveling.
A mobile-first design
Cityway sites are designed primarily for mobile screens (mobile-first approach). The interface is optimized for small screens: clear menus, simplified navigation, and streamlined content. The result is a smooth, ergonomic experience, even on a smartphone. Travelers can easily get information on the go without any hassle.
And this is far from marginal: today, nearly 80% of visits to Cintalia traveler information websites are made from a smartphone. Travelers can easily get information on the go without any hassle.
The mobile app: the go-to for regular travelers
While the website serves as a general entry point, the mobile app becomes the daily companion for regular travelers. Installed on the smartphone, it opens instantly and offers a highly fluid user experience. Unlike a website that needs to be launched in a browser, the dedicated app is always at your fingertips.
Above all, the application leverages the native features of the phone. It sends push notifications in real time (instead of sending billable SMS) to provide immediate alerts in the event of disruptions. It also uses GPS and the camera of the smartphone: locating the nearest stops and scanning QR codes (for example, to validate an M-ticket). It also integrates mobile ticketing : purchasing tickets on mobile, activating an m-ticket with a validity timer, digital payments, etc. Some data can even be stored locally for offline access. These are all possibilities inaccessible on a website, making the app a tool tailored for regular travel.
In summary, the app's advantages:
- Speed and convenience: direct access to information, instant launch, interface optimized for frequent use.
- Real-time interactivity: push alerts for instant notifications, services utilizing GPS and the camera.
- Integrated advanced services: purchasing and validating tickets (QR code, m-ticket), mobile payments, offline access to maps or schedules, etc.
Two complementary platforms, a winning strategy?
Rather than choosing between a website and an app, the ideal approach is to offer both by leveraging their complementarity. Each channel has its own role: the website ensures broad reach (especially for occasional travelers or those in the planning phase), while the mobile app builds loyalty among regular commuters with an optimized experience. Together, they allow you to effectively reach all types of travelers.
This dual offering can also be implemented gradually. For example, a network might first launch a passenger information website, then add the mobile app at a later stage. This staggers the rollout of new features and facilitates public adoption. The Cintalia platform from Cityway is designed to support this evolution: activate only the modules you need and scale the solution at the pace of your project.
Finally, it is essential to ensure consistency between the two platforms. The unified Cintalia platform provides exactly that: the website and mobile app share the same database in real time, with no double entry. Your teams avoid duplicate updates, and travelers find reliable, synchronized information on every platform.

Some networks, such as TRéMA (Mâconnais-Beaujolais), have understood this well: the website + mobile app duo allows them to meet the needs of both occasional and regular travelers.
When it comes to passenger information, websites and mobile apps are not rivals but complementary. The website offers universal reach and meets everyone's needs, particularly for planning a trip or discovering a network. The mobile app provides an enhanced experience and interactive for daily commutes, strengthening loyalty among regular passengers. For a transport network, offering these two complementary platforms covers the full range of passengers' digital habits.
With Cityway's Cintalia platform, this omnichannel strategy remains simple to manage: the web portal mobile-first and the native app share a common data foundation branded to your network. No need to choose one or the other: by adopting the website + mobile app duo, you effectively keep your passengers informed on all fronts.

.png)



.png)

.png)
.png)
.png)