CASE · LOGISTICS AND SERVICESCASE STUDY · LOGISTICS AND SERVICES
VitaLink: a bilingual ecosystem from strategy through code.VitaLink: a bilingual digital ecosystem built from strategy through code.
I built the digital identity and product system for Courier and Express: research, brand, UX/UI, design-system work, Angular, and publication coordination.VitaLink needed a digital identity and a clear way to communicate two related offers: medical courier and Express services. I led the initiative end to end, from research, positioning, and brand direction through UX/UI, design-system work, Angular architecture, frontend implementation, and publication coordination.
ROLE AND SCOPE
Lead Product Designer & UX Engineer
Strategy · brand · UX/UI · design system · frontend · SEO · Angular · i18nStrategy, brand, UX/UI, content, design system, frontend, and SEO · VitaLink Courier + VitaLink Express · English + Spanish · Angular, TypeScript, RxJS, Tailwind CSS, SSR/prerendering, and Express
CONTEXTCONTEXT AND RESPONSIBILITY
The challenge
Distinguish Courier and Express without fragmenting the brand, across two languages and coherent technical behavior.The company lacked a consolidated digital identity. The product had to communicate trust-sensitive services, distinguish Courier and Express without fragmenting the brand, and keep routes, metadata, and HTTP behavior coherent across two languages and domains.
My responsibility
I turned the client's operational knowledge into strategy, identity, architecture, UX/UI, and frontend delivery.The client supplied operational knowledge, services, and approvals. I translated that input into strategy, identity, information architecture, visual language, flows, documentation, frontend architecture, and technical stabilization.
PROCESSFROM OPERATIONAL BRIEF TO DIGITAL SYSTEM
From operational brief to digital system.Five decisions connected brand, product, and architecture.
- DiscoveryDiscovery and positioningServices, audiences, and trust.I organized services, audiences, trust requirements, and goals. VitaLink remained the anchor.
- ArchitectureInformation architectureCoverage, signals, and next step.Navigation answers service fit, coverage, trust signals, and next step before contact.
- Visual systemBrand, components, responsive.I defined logo, color, typography, photography, components, and responsive behavior.
- Shared architectureOne architecture, two surfacesCourier and Express, one base.A shared Angular base reduces duplication while preserving identity and canonical origins.
- Honest conversionWhatsApp or SMS, no fake backend.Quote flow hands users to WhatsApp or SMS without claiming a nonexistent backend.
EVIDENCEPUBLISHED EVIDENCE
Intent, code, and validation.Evidence separates intent, implementation, and validation.
Every artifact declares source and state.The case does not present concepts as shipped product. Each artifact identifies its state and source.


Shared architecture
Courier and Express share one Angular base without losing identity.
REPO 34bef38 · AUTHORIZED
One shared architecture
Courier and Express share navigation, localization, components, and one Angular base while preserving distinct propositions and canonical origins.
SOURCE · PUBLIC REPO 34bef38 · AUTHORIZED
TECHNICAL EVIDENCEINSPECTABLE TECHNICAL EVIDENCE
Documented validation point.Quality is presented as a validation point, not a promise.
No business-impact claims.Values documented in the public edition and limited to the recorded validation point.
- 27
- passing tests
- 21
- prerendered routes
- ≈23.5%
- raw bundle reduction
- 478 + 478
- ES/EN parity
- 2 origins
- canonical origins
- 0
- vulnerabilities
- 27
- passing automated tests
- 21
- prerendered routes
- ≈23.5%
- initial raw bundle reduction
- 478 + 478
- ES/EN values with automated parity
- 2 origins
- corrected multidomain canonicals
- 0
- vulnerabilities reported by npm audit
OUTCOMECURRENT OUTCOME
Identity, service, and code in one system.A coherent, observable ecosystem.
The experience and repository make decisions and limitations visible.The work turned a broad operational brief into an experience connecting identity, service design, bilingual content, and frontend delivery. Product and repository make decisions and boundaries inspectable.
Limitations
No conversion or revenue claims. No payments, tracking, or backend. Express stays inactive while returning 404.
Explore the case.
Inspectable product and code.
Declared limitations
No claims are made about conversion, revenue, traffic, or ranking. The public edition excludes payments, tracking, quote backend, and operational integrations. VitaLink Express is not shown as an active link while its public route returns 404.
Review the experience and architecture.
A public product and technical repository with explicit boundaries.