Two Kinds of Studio Operate in Ho Chi Minh City
Before comparing portfolios, work out which half of the market you are talking to, because the two halves sell different things. One group designs for domestic brands and knows the local conventions cold: the payment wallets people actually use, the messaging app that carries customer conversations, the way an address is written. The other group works almost entirely for foreign clients, often as a design function attached to an offshore delivery team, and is fluent in the workflow a foreign product manager expects but has no particular reason to know the local habits.
Both are useful. Neither is a substitute for the other. Say in the brief whether the audience is domestic or export, because a studio staffed for one will quietly deliver the other and you will not notice until the pages are in front of real users.
Keep the disciplines apart as well. Research, structure, wireframes, interface and brand application, typography, states, responsive rules and a documented component set are design. Build, integration and platform work are not, and if the difficult part of your project is engineering you should be talking to development teams in the same city and contracting the design on its own terms.
Vietnamese Diacritics Are a Layout Constraint
This is the single most common way a foreign design fails here, and it is entirely mechanical. A vowel can carry a mark that modifies the letter and a second mark that carries the tone, stacked above one another, and some letters carry a mark below as well. That means the visual height of a line of Vietnamese text is greater than the same line of English, in both directions from the baseline.
The consequences are predictable once you know to look. Tight line heights clip the upper tone marks, so headings look damaged. Fixed-height buttons and chips cut the tops off capitals. Uppercase settings are worse than lowercase, because the marks sit even higher above a capital, and a menu set in all caps with a snug bounding box will lose them. Text that has been vertically centred by eye in English drifts once the marks appear.
The font choice compounds it. A large number of popular typefaces ship without full Vietnamese coverage, and the fallback is invisible in a mockup written in English. What you get in production is a mixed page where accented characters come from a different family, in a different weight, with different spacing. Ask the studio to prove coverage by setting real copy, including a line of all caps, in every weight the design uses. Ask who will hold the webfont licence, and confirm it covers the accented range rather than the Latin basic set.
Conversations, Payments and the Components They Require
Customer contact runs through Zalo far more than through email, and for many businesses an official account there is the real front door. That belongs in the design: an entry point that survives on a small screen next to a cart bar and a consent notice, a prefilled message so the team knows which page a person came from, and a plan for what the desktop version does with a channel built for handsets.
Checkout has its own local shape. Wallets such as MoMo and ZaloPay sit alongside bank transfer and card gateways, and cash on delivery remains normal enough that a design which treats it as an edge case will lose orders. Each method needs drawn states: a QR panel with a countdown, a redirect and return, a pending confirmation, a failure that explains itself. Bank transfer by QR standard is widespread and the code needs a composed place in the layout rather than a corner someone finds later.
Addresses are a three-level selection of province, district and ward, usually as dependent dropdowns, with a free-text line for the street and building. Designing this as a single address box looks tidy and breaks delivery. Phone numbers, not email addresses, are often the account identifier, which changes sign-up and recovery flows.
Screens Are Small, Networks Are Mixed, Patience Is Short
The typical visitor is on a mid-range handset. That argues for type sizes and touch targets set for thumbs rather than trackpads, imagery that carries meaning at a small scale, and interfaces that stay usable while assets are still arriving. Design the skeleton and the loading state deliberately, because on a busy mobile connection they are what a real person sees first.
Dark interiors, glare and one-handed use are worth designing for rather than assuming. Contrast that passes a specification on a bright office monitor can still fail on a cheap screen outdoors, so check the palette on actual hardware before the component library is signed off.
A Calendar That Reshapes the Page, Not Just the Banner
The lunar new year period is the commercial peak and also a long shutdown, and campaign design around it is much more than a red banner. Sites take on a seasonal skin, promotions change shape, delivery cut-off notices become prominent and then have to be removed cleanly. Mid-autumn and the recurring monthly sale dates run by the marketplaces add further variants.
The right deliverable is not a folder of seasonal page designs. It is a theme layer in the component library, with tokens for the festive palette, a rule for which components accept the skin, and a documented way to switch it off. Ask a candidate studio how a previous client changed season and who did the switching.
Bilingual Sites Need a Structure, Not a Toggle
Export-facing companies usually need Vietnamese and English on the same site, and the two languages do not occupy the same space. English runs shorter in places and longer in others, headline breaks fall differently, and a layout tuned to one will look loose or cramped in the other. Decide early whether the two versions share one template with flexible blocks or diverge, and design the language switch as a visible, persistent control rather than a flag hidden in a footer.
Copy quality is part of the design contract. English written by someone who does not write English professionally undermines an otherwise strong page, and this is the most common weakness in export-facing work from Ho Chi Minh City. Agree who writes and who reviews each language before kickoff.
Handover Is Where Cheap Becomes Expensive
Ask for the working file rather than flat exports, with named components, tokens for colour and type, responsive rules, and empty, loading and error states drawn rather than described. Hold the design tool account in your company name so a change of supplier does not cost you the source. Get the icon and image export set, and get the font licence purchased in your name.
Run a small paid exercise before committing to a full site: one real template, in both languages, with the states included. It tells you more about a team than any portfolio, and it is cheap enough to repeat with a second candidate.
You can browse verified profiles and client feedback for web design studios in every market on Edvido, compare product interface specialists when the work is an application rather than a site, and send a single brief to a shortlist to see how the proposals differ.