Guests use a travel platform when it feels fast, clear and someone looks after them when things go wrong.
The rivals of a domestic booking or tour platform are international names guests already know by heart. Sinh Vũ gives your platform an identity, a UI design system and a voice that stay consistent across app, web and notifications, so guests remember the name and trust it when they pay in advance.
Three things: a clear position so guests know why to use this platform, a consistent interface system across app and web, and a voice that reassures when things go wrong. A platform never touches the room or the trip, so trust comes from how it appears and how it replies.
One reason for guests to choose you, for example understanding Vietnamese travelers better, being clearer, or offering Vietnamese-language support.
The same color, type, buttons and cards across app, web and email, so adding a new feature doesn't add clutter.
Confirmations, delay notices and rescheduling messages written clearly and calmly, with something for the guest to do next.
All of them connect guests with travel services, but the users and what worries them differ.
Their customersGuests comparing many places to stay, and property owners who want more bookings.
Brand challengeShow both sides a platform that is clear, easy to compare and fair.
Their customersGuests searching for tours by destination, date and group, who want to read honest reviews.
Brand challengeMake choosing among many hard-to-compare tours easy, on a phone.
Their customersMany sellers (vehicles, attraction tickets, guides, experiences) and guests buying each item separately.
Brand challengeKeep one shared face across many suppliers, so guests trust it even when each partner looks different.
These are the places where platforms tend to lose guests even when the features are complete.
Each team adds a screen in its own way, with buttons and colors differing everywhere, so guests have to relearn at every step.
Build a shared UI design system: color, type, buttons, cards and rules, so every new screen grows from the same root.
Start from this problemThe list of cards looks like a copy of a big platform's, and guests have no reason to remember your name.
Design result cards with their own mark: how information is arranged, how reviews are described and how what the platform has verified is flagged.
Start from this problemConfirmation emails, rescheduling notices and refund messages written dry and hard to follow, leaving guests uneasy.
Write a set of notification templates in one voice: say plainly what happened, what has been done and what the guest needs to do next.
Start from this problemPartner documents, the management page and the guides each look different, and partners hesitate to commit.
Make a polished partner document set in the same system as the interface: an invitation, a sign-up guide and shared working rules.
Start from this problemAt the Book stage. Guests like the platform, but when it comes to entering details and paying they hesitate, because they don't trust it enough yet or the payment screen is confusing.
Touchpoints are the places where guests see, touch or hear about the platform. You don't need to do everything at once. These five touchpoints decide most of the trust.
What guests see every time they open the app, and the smallest size at which the mark has to stay legible.
Where guests compare and decide whether to go on.
The moment guests decide to pay, so every word has to be clear.
Guests read them when anxious: rescheduling, refunds, trip reminders.
Partners are the supply, and they read these to decide whether to stay.
Listed in the order to do them. A new platform stops at step two or three; a platform with several teams goes all the way.
Name, mark, color and type: the base for app, web and every document.
A shared UI design system so every team builds screens from the same root.
An introductory website and landing pages for guests and partners, in the same voice as the app.
A set of notification templates, confirmation emails and guidance copy in one voice.
A document set for inviting partners and a sign-up guide.
Sinh Vũ has not published a travel platform project. The two below are closest in the problem: a platform running in parallel on app and web, and a platform with many production teams building together.
2017Homedy is a real-estate marketplace running in parallel on app and web. Sinh Vũ built the strategy, identity and a shared digital design system…
A platform set on one shared root, from position and mark to the digital design system, so app and web grow fast without speaking in two voices.
Metacity builds a 3D city where residents buy land, raise buildings and earn a living from the work of building. Sinh Vũ built the brand foundation and the standards behind it…
A standard for many production teams working every day while the product stays one place: a lesson for platforms with many teams.
The principles behind it
An app logo lives mostly at very small sizes on a phone screen. Sinh Vũ tests the mark at app icon size first, then scales up to larger sizes.
Yes, once two or more teams build screens together, or when there is both an app and a website. A design system lets every screen share color, type, buttons and rules, so you don't start over each time you add a feature.
Don't compete on every front. Choose a specific position such as understanding Vietnamese travelers, Vietnamese-language support, or strength in one region, then let the identity and the interface say that.
Yes, and they are what guests read most closely when anxious. A set of notification templates in one voice helps guests feel there are real people behind the platform.
Build a shared display template for service cards, photos and descriptions, then give partners clear guidance documents. Guests see one platform, not a pile of stalls.
A few lines about the product, your users and what is holding you back is enough. Sinh Vũ will read it and reply within one business day.