Dabang (다방) DESIGN.md

Design System Inspiration of Dabang (다방)

Overview

Visual Theme & Atmosphere

Dabang is Station3’s residential-information service: the company presents Dabang alongside its broker and landlord services, while the service terms describe a platform where individual users, licensed brokers, and landlords can find or register property information. The current public web product is deliberately utilitarian rather than a brand campaign. Its home and map routes use a white field, dark neutral text, compact controls, and one loaded Pretendard Variable family to make browsing and filtering legible. The notable product expression is geometric rather than decorative: an 8px header control, 2px outlined actions, a 32px home-search pill, and a 42px map-search pill coexist because they serve different contexts.

The supplied evidence establishes three separate source domains: the home and map as product surfaces, the FAQ as support-documentation chrome, and Station3’s service page as corporate context. This reference does not turn support controls or corporate messaging into universal product tokens.

Primary tasks

• Search housing information and move from there into an inquiry
• Look for a place on the map by location
• Register property information on the service as a licensed broker
• List a property for rent as a landlord

Brand Narrative

Station3 publicly positions Dabang beside Dabang Pro and Dabang Bangjoo-in: consumer property discovery, broker workflow, and landlord-management services are related but different offerings. The service terms make the platform boundary equally explicit: Dabang provides real-estate information and a place for registered content, while users, landlords, and brokers provide the relevant listings and conduct their own transactions.

The current public web UI reflects that operational role. Its controlled neutral palette and compact map controls prioritize a finding/filtering task rather than a decorative real-estate lifestyle story. The pink identity colour remains catalog metadata in this revision because the supplied web evidence does not show it as a reusable product-control rule.

Principles

1. Separate source domains. Home/map evidence, FAQ chrome, and Station3 corporate copy have different authority. UI implication: do not merge their component values into one synthetic library.
2. Keep property tasks explicit. The terms distinguish search, listing, and transaction roles. UI implication: name the task and actor instead of using vague conversion language.
3. Use action blue locally. #326CF9 is verified in the map-route selection and tool states and on the footer button. UI implication: expand its use only after a specific product component provides evidence.
4. Preserve measured geometry. The two search pills differ by route and purpose. UI implication: keep the 32px and 42px radii distinct rather than averaging them.

Personas

These are service-role contexts from the official terms and Station3 service page, not invented demographic personas.

• Property seeker: searches public housing information and needs a clear route into filtering or inquiry.
• Licensed broker: can register and provide permitted property information through the service.
• Landlord: can provide a listing for rental and needs the platform’s registration boundary made clear.

Colors

• #FFFFFF — observed public home/map canvas and control background.
• #222222 — repeated home/map foreground and control text.
• #DFDFDF — repeated outline border on public header and map dock controls.
• #F5F5F5 — observed muted surface; it is also the hover and pressed fill of the header links and account control (§4), a header-local state rather than a global interaction rule.
• #EDEDED — map location-search border.
• #326CF9 — map-route action colour: the rest ink of the selected header link and of the selected side-navigation link (with a 1px #326CF9 border), the hover and pressed ink of the map tool buttons, and the fill of the footer button. Corrected 2026-09-30: the July text called it the map tool's default treatment, but the tool buttons rest at #222222; the blue is their hover and pressed frame. The evidence supports it as a map and footer action colour, not a universal Dabang CTA rule.
• Component-local colours recorded in §4, not promoted to palette roles: #434343 (map side-navigation text), #EEF8FF (selected side-navigation fill and pressed map-tool fill), #FCFCFC (hover and pressed fill of the header outline actions), #F0F0F0 with a 3px #396BF3 top edge (home accent cards), and #515151 with #E5E5E5 text (footer link buttons).

The pink value in frontmatter is catalog identity metadata. It was not established as a reusable current product-control token by this supplied capture, so it is not silently substituted for the map action color.

Typography

Verified visible UI family

Pretendard Variable is the only family promoted to tokens.typography.family.ui. The supplied bundle records 376 visible first-family uses across body text, headings, buttons, inputs, and lists; it is marked loaded with high confidence and is corroborated by 92 Dabang-hosted dynamic-subset WOFF2 source URLs. That is computed use plus FontFaceSet/source corroboration, not an inference from a CSS declaration.

Layout

• The home and map are distinct product compositions: home exposes a 32px-radius search-entry control, while the map route uses a 42px location-search field and compact dock controls.
• Repeated observed spacing values support only a conservative 4 / 8 / 16px set. They do not establish a full layout grid, rail width, map-canvas percentage, or breakpoint contract.
• The FAQ uses a separate support-documentation layout. Its 16px/20px row padding must not be treated as map or listing-card spacing.

Responsive Behavior

The supplied evidence uses a 1440×900 viewport for all three routes. It does not verify mobile breakpoints, map drawer behavior, native safe areas, or listing density at another viewport. Treat the current dimensions as desktop public-web observations only.

Elevation & Depth

The selector-backed product controls retained in §4 report box-shadow: none. This is useful evidence for those controls, but not proof of a global zero-elevation system: the supplied routes do not establish cards, markers, drawers, or native-app elevation. Use flat borders and surfaces only where a retained component names them; label any broader shadow system as a local extension.

Motion & Easing

No motion duration, easing curve, or animation behaviour is promoted. The static supplied capture has no interaction records, and any motion implementation must be treated as a local extension with reduced-motion support rather than as verified Dabang behaviour.

Components

Header account control

Default

• Background: #FFFFFF
• Text: #222222
• Radius: 8px
• Padding: 8px 16px
• Font: 16px / 400 Pretendard Variable
• Hover and pressed: background #F5F5F5 (the account button on all three routes; six frames agree)
• Use: Shared public header account control on the product home; home::[data-omd-capture="4"].

Header outline action

Default

• Text: #222222
• Border: 1px solid #DFDFDF
• Radius: 2px
• Padding: 0px 16px
• Font: 14px / 700 Pretendard Variable
• Hover and pressed: background #FCFCFC, opaque over the transparent rest (six actions, twelve frames agree)
• Use: Shared public header outline action; home::[data-omd-capture="5"].

Map location search

Default

• Background: #FFFFFF
• Text: #222222
• Border: 1px solid #EDEDED
• Radius: 42px
• Padding: 7px 37px 7px 15px
• Font: 14px / 400 Pretendard Variable
• Use: Map location-search field; surface-2::[data-omd-capture="1"].

Map dock control

Default

• Background: #FFFFFF
• Text: #000000
• Border: 1px solid #DFDFDF
• Radius: 2px
• Padding: 0px 7px 0px 11px
• Font: 14px / 400 Pretendard Variable
• Hover and pressed: background #EDEDED (five dock buttons and the icon-only dock button, capture 19; twelve frames agree)
• Use: Map dock control; surface-2::[data-omd-capture="14"].

Support FAQ row

Default

• Border: 1px solid #F5F5F5 on the block end
• Padding: 16px 20px
• Use: Support-documentation FAQ row (support-faq-row); surface-3::[data-omd-capture="10"], five rows. It is documented here as support chrome, not promoted into product tokens.
• Corrected 2026-09-30: the July text gave this row #000000 text and 13.3333px / 400 type. Those are the browser's defaults for a button element that sets neither; the row's label sits in a child the capture did not sample, so no label style is claimed.

Header navigation link

Default (header-nav-link)

• Background: #FFFFFF
• Text: #222222
• Radius: 8px
• Padding: 8px 16px
• Height: 42px
• Font: 16px / 400 / 26px Pretendard Variable
• Hover and pressed: background #F5F5F5
• Selected: text #326CF9 on the map route
• Use: home::[data-omd-capture="1"]. Eight rest links (home and FAQ captures 1–3, map captures 3–4) and the active map link share this geometry; all eighteen hover and pressed frames on the nine links record #F5F5F5. The map link with class active (surface-2::[data-omd-capture="2"]) records #326CF9 where its siblings record #222222.

Public-home controls

Pill chip (home-filter-chip): background #FFFFFF, text #222222, border 1px #DFDFDF, 32px radius, 0px 11px, 32px high, 14px / 700 / 24px Pretendard Variable; home::[data-omd-capture="18"] through "22". The first chip (capture 17) records background #222222, text #FFFFFF and border 1px #222222; only a generated class separates it, so it is described, not declared as selected.

Search input (home-search-input): transparent, text #222222, 11px 23px 11px 56px padding, 680px × 48px, 16px / 400 / 26px Pretendard Variable, border width 0px; home::[data-omd-capture="7"]. Its pressed and focus frames change only the padding (to 11px 56px).

Entry card (home-entry-card): background #FFFFFF, border 1px #EDEDED, 12px radius, 20px padding, 333px × 178px (the second row 217px × 172px); home::[data-omd-capture="8"] through "12". The card is a link container whose own colour is the browser's default link blue, so no label style is claimed.

Accent card (home-accent-card): background #F0F0F0, a 3px #396BF3 top edge, 3px radius, 33px 20px 30px 30px padding, 233px × 330px; home::[data-omd-capture="43"] through "45". Also a link container; no label style is claimed.

Map-route controls

Tool buttons (map-tool-button): background #FFFFFF, text #222222, 6px padding, 36px × 36px, 12px / 400 / 20px Pretendard Variable; the stack's top button has 6px 6px 0px 0px corners, the bottom one 0px 0px 6px 6px, the middle ones square; surface-2::[data-omd-capture="25"] (captures 22–29). Hover: text #326CF9, weight 700. Pressed: text #326CF9, background #EEF8FF, weight 700. The top and bottom buttons (captures 22 and 23) agree in each frame, and both colours are rest colours elsewhere on the route.

Side navigation link (map-side-nav-link): transparent, text #434343, border 1px transparent, 4px radius, 70px × 64px, 12px / 500 / 20px Pretendard Variable; surface-2::[data-omd-capture="9"] through "12". Selected (class active, capture 8): background #EEF8FF, text #326CF9, border 1px #326CF9, 700. Its hover, pressed and focus frames are transition frames (see How states were read).

Dark pill button (map-dark-pill-button): background #222222, text #FFFFFF, border 1px #222222, 32px radius, 0px 16px, 32px high, 14px / 700 / 24px Pretendard Variable; surface-2::[data-omd-capture="20"].

Footer controls

Link button (footer-app-link): background #515151, text #E5E5E5, 2px radius, 0px 9px, 30px high, 12px / 400 / 12px Pretendard Variable; home::[data-omd-capture="70"] through "72" (FAQ captures 22–24).

Primary button (footer-primary-button): background #326CF9, text #FFFFFF, 2px radius, 0px 9px, 30px high, 12px / 700 / 20px Pretendard Variable; home::[data-omd-capture="73"] (FAQ capture 25).

Support FAQ category tab

Default (support-faq-category-tab): background #FFFFFF, text #222222, border 1px #EDEDED, square corners, 394px × 64px, 16px / 400 / 26px Pretendard Variable; surface-3::[data-omd-capture="8"] and "9". Selected (class active, capture 7): background #222222, text #FFFFFF, border 1px #222222, 700. Support-documentation chrome, not a product token.

How states were read

A state frame is the computed style the collector recorded with the pointer over an element (hover) or pressed on it; interactionCount: 0 counts menu, dialog, and tab expansions and says nothing about these frames. Corrected 2026-09-30: the July text read the zero count as meaning the frames were not state evidence. Settled frames are declared above: the header links and account control, the header outline actions, the map dock buttons, and the map tool buttons. The map side-navigation frames (background alpha 0.024 to 0.067 and weights 501 to 513 on a variable font, disagreeing within one class) and the search inputs' padding moves are transition or focus effects and are not declared. Container links on home record only the browser's default link colours (blue at rest, red while pressed), which are not state values. No focus value is declared: the collector presses the mouse before focusing, which leaves :focus-visible false. No menu, dialog, validation, disabled, loading, or responsive variant is claimed.

---

Verified: 2026-07-13 Tier 1 sources: https://www.dabangapp.com/ (product home), https://www.dabangapp.com/map/onetwo?m_lat=37.494367328004216&m_lng=127.01446798508894&m_zoom=11 (product map), https://www.dabangapp.com/service/faq (support documentation), https://www.station3.co.kr/service/ (official company/service context), https://static.dabangapp.com/html/useragreement.html (official service and stakeholder context), https://github.com/orioncactus/pretendard (upstream font context), and https://github.com/orioncactus/pretendard/blob/main/LICENSE (font licence). Tier 2 sources: https://getdesign.md/dabang (attempted; built-in web open safe-open failure and name search returned no record), https://styles.refero.design/?q=dabang (attempted; built-in web open safe-open failure and name search returned no record). Conflicts unresolved: none

The earlier reference’s full semantic colour ramps, pink-as-global-brand-control rule, status meanings, map-marker semantics, universal 8px layout system, zero-shadow universal rule, and unobserved interaction/motion matrices were rolled back. The supplied 2026 bundle does not substantiate them as reusable product claims.

States

Corrected 2026-09-30: the July table listed default values only because no interaction expansion was retained; the capture's hover and pressed frames are measurements in their own right. Focus, disabled, error, empty, loading, success, skeleton, menu, dialog, and toast contracts remain unclaimed.

Live state probe, 2026-10-16 (https://www.dabangapp.com/), footer-primary-button: pressed — no visible change (measured 2026-10-16); focus — outline #ededed solid 1px.

Do's and Don'ts

Do

• Keep home, map, support-documentation, and corporate-context evidence explicitly separated.
• Use Pretendard Variable only where its loaded public-web evidence applies; retain a normal runtime fallback in an implementation.
• Preserve the observed 32px home-search and 42px map-search geometries as separate controls.
• Use #326CF9 only for the documented map-route selection and tool states and the footer button unless a broader product source verifies it.
• Build the retained outline controls from their explicit border, radius, padding, and type values.

Don't

• Don't promote the frontmatter pink identity color into a current universal CTA or status color.
• Don't represent the FAQ disclosure row as a product-listing, modal, or accordion component contract.
• Don't infer hover, pressed, focus, disabled, error, or loading states beyond the settled frames declared in §4; transition frames, focus frames, and the browser's default link colours in the capture are not state values. (Corrected 2026-09-30: the July rule tied this to the zero interaction-expansion count, which does not describe these frames.)
• Don't substitute a system font as if it were loaded Pretendard Variable.
• Don't invent map markers, card elevation, breakpoints, icon geometry, or motion values absent from the supplied evidence.

Voice & Tone

The official service context centres on housing information and on connecting the people who search for, list, and manage a property: individual users, licensed brokers, and landlords. That makes the reliable voice direction practical and role-aware. Name the property task, make the next action clear, and distinguish information provided by the platform from content entered by a user or broker. Avoid a campaign-like promise, a demographic stereotype, or an implication that the platform itself is a party to a property transaction.

Agent Prompt Guide

• “Create a Dabang public-home account control with a white background, #222222 text, 8px radius, 8px 16px padding, and 16px/400 Pretendard Variable.”
• “Create a Dabang map location-search field with a white background, 1px #EDEDED border, 42px radius, 7px 37px 7px 15px padding, and 14px/400 Pretendard Variable.”
• “Create a map dock control from the selector-backed default and its measured hover and pressed fill #EDEDED; do not add focus, disabled, or selected states as verified Dabang behaviour.”
• “If a component is not listed here, mark it as an extension rather than presenting it as a verified Dabang product component.”

Governance

Known Gaps

• Contrast, home-search-input. Text #222222 on #00000000 measures 1.32:1, below the WCAG AA 4.5:1 minimum for normal-size text. Recorded as measured, not adjusted.
• Contrast, map-side-nav-link. Text #434343 on #00000000 measures 2.12:1, below the WCAG AA 4.5:1 minimum for normal-size text. Recorded as measured, not adjusted.