Design System Inspiration of MyRealTrip (마이리얼트립)

1. Visual Theme & Atmosphere

MyRealTrip is a Korean travel marketplace whose own public materials describe a 2012 start brokering locally made tours and a current scope across travel experiences. The current public home and hotel-listing surfaces pair a white working canvas with low-chrome navigation: a blue header action, a pale-gray search field, compact gray text, and a selected dark locale pill. The visual system recorded here is deliberately narrower than a brand story. It covers only current rendered public web evidence, while the separate corporate/about site is kept as corporate chrome rather than silently blended into consumer-product tokens. MyRealTrip’s public partner program foregrounds reliable booking, sustained traveler ratings, and prompt communication; its current company blog describes the organisation as an AI-native travel platform. Those are product and organisational context, not evidence for an unobserved app component or visual token.

Observed character: restrained utility chrome around travel discovery, with #2B96ED used for the repeated public header action rather than a generalised brand palette.

Primary tasks

• Find a locally made tour or travel experience to book
• Search for a stay from the hotel listing
• Manage schedules so a confirmed reservation gets fulfilled

2. Color Palette & Roles

The following are current computed observations from the supplied 2026-07-13 product bundle. They are not a published MyRealTrip token library.

The prior deep-blue, violet, semantic, sale, and success palette claims are not retained: the fresh bundle does not establish them as current reusable product tokens.

Component-local colours recorded in §4 and not promoted to palette roles: #343A40 text on a pair of white 15px / 600 home buttons; on the separate corporate about site, #374151 header links, a #000000 header pill with white text, and #666666 footer links.

3. Typography Rules

Current public-web font evidence

Measured public roles

These are captured public-web roles, not a claim about authenticated booking screens, mobile native UI, help-center chrome, or a company-wide typographic scale.

4. Component Stylings

Public header action

Observed default

• Background: #2B96ED
• Text: #FFFFFF
• Radius: 12px
• Padding: 0px 24px
• Height: 40px
• Font: 14px / 600 / loaded internal Pretendard alias on home; Pretendard stack on hotel listing
• States: default only; the bundle holds no hover, pressed, or focus frame on any of its three surfaces, so none is claimed, and no disabled, menu, dialog, validation, or loading variant was captured. Corrected 2026-09-29: the July text gave interactionCount: 0 as the reason; that field counts expansions, not pointer-state frames
• Use: repeated header action on home::[data-omd-capture="5"] and surface-3::[data-omd-capture="3"]

Public search field

Observed default

• Background: #F5F6F7
• Text: #495056
• Border: 0px
• Radius: 0px
• Padding: 0px 54px 0px 20px
• Height: 48px
• Font: 15px / 500 / loaded internal Pretendard alias on home; Pretendard stack on hotel listing
• Use: public keyword search at home::[data-omd-capture="3"] and surface-3::[data-omd-capture="1"]

Selected locale tab

Selected state observed

• Background: #101418
• Text: #FFFFFF
• Radius: 16px
• Padding: 6px 10px
• Height: 32px
• Font: 15px / 700 / Pretendard
• Active: aria-selected="true" on home::[data-omd-capture="1"]
• Use: selected locale tab within the home-header tablist

The unselected sibling’s transparent computed text is not promoted as a reusable inactive variant. Its static capture does not establish an interaction transition.

Header text button

Observed default (header-text-button)

• Background: transparent
• Text: #666D75
• Radius: 3px
• Padding: 8px 12px
• Height: 39px on hotel listing (22.5px line height); 34px on home (normal line height)
• Font: 15px / 600 / Pretendard
• Use: surface-3::[data-omd-capture="2"] (class GlobalNavNonLineButton) and home::[data-omd-capture="4"], beside the blue header action; 105px wide on both.

Outline button

Observed default (outline-button)

• Background: #FFFFFF
• Text: #495056
• Border: 1px #CED4DA
• Radius: 4px
• Padding: 9px 8px
• Height: 40px
• Font: 14px / 700 / 21px Pretendard on hotel listing; normal line height on home
• Use: footer customer-centre button (button.mrt-button) at surface-3::[data-omd-capture="15"] and home::[data-omd-capture="23"]; 140px × 40px on both surfaces.

Footer links and select

Sitemap link (footer-sitemap-link)

• Text: #666D75; radius 4px; padding 6px; 14px / 400 / 21px Pretendard
• Height: 33px on hotel listing, 29px on home (normal line height)
• Use: SiteMapItems--MenuLink at surface-3::[data-omd-capture="16"] and home::[data-omd-capture="24"]; nine links per surface.

Policy link (footer-policy-link)

• Text: #666D75; radius 4px; padding 6px; 14px / 400 / 21px Pretendard
• Height: 44px on hotel listing, 56px on home
• Use: PolicyList--Link at surface-3::[data-omd-capture="25"] and home::[data-omd-capture="33"]. One link in each row (hotel capture 26, home capture 34) carries a different generated class and renders 14px / 700; that is a fixed emphasis, not a state.

Select popup button (footer-select-button)

• Background: #FFFFFF; border 1px #CED4DA; radius 4px; padding 0px 10px; 118px × 40px
• Use: DesktopSelect--PopupButton at surface-3::[data-omd-capture="34"] and home::[data-omd-capture="43"]. The button's own computed colour differs by surface (#373A3C on hotel listing, #000000 on home) and its own type is 10px on hotel listing and the browser-default 13.3333px on home, so the visible label sits on a child element the bundle did not capture. No label style is claimed.

Home content controls

White button pair (home-white-button)

• Background: #FFFFFF; text #343A40; radius 0px; padding 0px; 162px × 38px
• Font: 15px / 600 in the loaded alias __pretandard_7bdbf6
• Use: home::[data-omd-capture="46"] and "47"; the bundle does not record their role.

Blue text link (home-blue-text-link)

• Text: #2B96ED; 14px / 500 in the loaded alias __pretandard_7bdbf6; 16px high
• Use: home::[data-omd-capture="19"] through "21". The public blue appears here as link text as well as the header-action fill.

Corporate about-site chrome (separate domain)

These are measured on https://about.myrealtrip.com/ (bundle surface-2), the corporate site. They are recorded as corporate components and do not populate consumer tokens. Their computed stacks lead with Pretendard Variable, which the bundle lists as declared-only, so no family is claimed for them.

Header link (about-nav-link): transparent, text #374151, 12px radius, 8px 12px padding, 32px high, 14px / 500 / 20px; surface-2::[data-omd-capture="1"] through "6".

Header pill (about-nav-pill): background #000000, text #FFFFFF, 12px radius, 8px 12px padding, 76px × 36px, 14px / 500 / 20px; surface-2::[data-omd-capture="7"].

Footer link (about-footer-link): text #666666, 14px / 400 / 20px, 20px high; surface-2::[data-omd-capture="8"] through "11". Its class list names a Tailwind hover utility, but a class name is not a measurement and no hover frame exists, so no hover value is declared.

No component in this reference carries a hover, pressed, or focus value: the bundle holds no ::state-* frame on any of its three surfaces.

Verified: 2026-07-13 Tier 1 sources: https://www.myrealtrip.com/ (public consumer home), https://www.myrealtrip.com/hotels (public hotel listing), https://about.myrealtrip.com/ (separate corporate/about surface), https://help.myrealtrip.com/hc/ko (official support chrome and service context) Tier 2 sources: https://getdesign.md/myrealtrip (attempted; built-in web open returned a safe-open failure and search returned no MyRealTrip detail), https://styles.refero.design/?q=myrealtrip (attempted; built-in web open returned a safe-open failure and search returned no MyRealTrip detail). No Tier 2 value was promoted. Conflicts unresolved: none

The prior prose-derived palette, broad card/badge/dialog/toast inventory, hover/focus/error/disabled catalogue, mobile breakpoints, and motion rules were not supported by the supplied current raw evidence. They are removed rather than refreshed by assumption.

5. Layout Principles

The supplied bundle records public desktop-width documents only. The repeated consumer header is compact: the search field is 48px high, the primary action is 40px high, and the selected locale tab is 32px high. No public max-width, carousel, card-grid, booking-detail, or authenticated-flow layout rule is retained because the bundle does not supply a stable element-level measurement for one.

6. Depth & Elevation

The retained primary action, search field, and selected locale tab have no shadow. The selected tab’s own sample carries 0px 1px 2px rgba(0, 0, 0, 0.15) while the action and search field are none; this isolated header treatment does not establish a reusable elevation scale.

7. Do's and Don'ts

Do

• Keep the documented #2B96ED / #FFFFFF pair for the observed 40px public header action when reproducing that exact public-web pattern.
• Preserve the selected locale tab’s observed #101418 fill, 16px radius, and explicit selected-state provenance.
• Treat the pale #F5F6F7 search field as its own square-cornered public header control.

Don't

• Don't turn the captured default action into hover, focus, pressed, disabled, booking, or payment variants without new state evidence.
• Don't substitute a declared-only font face for the visibly loaded Pretendard/public aliases.
• Don't blend the corporate/about or help-center chrome into consumer product tokens.

8. Responsive Behavior

No responsive breakpoint or mobile layout was captured in the supplied evidence. The record therefore makes no claim about mobile navigation, carousel behavior, touch targets, safe-area controls, or image aspect-ratio rules.

9. Agent Prompt Guide

Use only the captured public pattern: “Create a 40px MyRealTrip public header action with #2B96ED background, #FFFFFF text, 12px radius, 0px 24px padding, and 14px/600 Pretendard-context typography. This is a static default; do not invent interaction states.”

For the selected locale control: “Use the observed selected tab only: #101418 fill, white 15px/700 text, 16px radius, 6px 10px padding, 32px height; preserve that it was an aria-selected=true observation.”

10. Voice & Tone

The public sources demonstrate Korean-first service labels such as 무엇을 도와드릴까요?, 문의하기, and partner guidance written in polite ~요 language. Those samples support a practical, explanatory service register on the public help and partner surfaces; they do not establish a comprehensive product voice system.

11. Brand Narrative

MyRealTrip’s own public offer page identifies founder Lee Dong-geon and says the company was founded in February 2012, beginning by brokering tours made by local people. Its current partner programme frames quality around responsible reservation fulfilment, traveller ratings, and timely communication. The company blog currently describes MyRealTrip as an AI-native travel platform and publishes product, technology, and organisational stories. Together, these sources establish a travel-marketplace origin and a current organisational direction; they do not supply an official rebrand history or a visual-design manifesto.

12. Principles

1. Reliable reservation fulfilment. The partner programme asks partners to manage schedules so confirmed reservations can be fulfilled. UI implication: do not represent this as a verified button, badge, or checkout-state treatment without product-screen evidence.
2. Traveller feedback matters. The public Real Partner criteria include a rolling one-year 4.8-or-higher review requirement. UI implication: the criterion is partner-program context, not permission to invent rating-card components.
3. Timely communication. The same programme asks for message responses and reservation confirmation within 24 hours. UI implication: do not turn this service standard into a notification, SLA, or error-state token without direct evidence.

13. Personas

The first-party materials identify public stakeholder groups rather than research-backed personas: travellers seeking travel products, partners who operate listings and reservations, and support visitors looking for help. No named or synthetic persona is supplied here; demographic needs, booking journeys, and conversion motivations are not established here, pending first-party research or user-provided evidence.

14. States

The collector reports one selected tab observation and interactionCount: 0, and no element on its three surfaces has a ::state-hover, ::state-pressed, or ::state-focus frame, so no hover, pressed, or focus value exists to declare. No verified empty, loading, error, success, disabled, validation, toast, dialog, or skeleton treatment is available from this packet.

15. Motion & Easing

No duration, easing, transition, reduced-motion, or animated-state measurement was captured. Do not infer motion from class names or from the presence of interactive-looking controls.