Responsive web design

Why responsive is a baseline, not an upgrade

Responsive Web Design means one page that adapts its layout to the screen, rather than a separate mobile site. In 2026 it is not a value-add — it is the floor. Mobile is generally more than half of traffic, and Google indexes the mobile version as the primary one, so a broken phone layout is a broken search ranking.

But "has responsive" and "responsive done well" are very different. Plenty of sites do not visibly break on a phone, yet the text is too small to read without zooming, buttons sit close enough to mis-tap, and the important information is pushed below five collapsed sections. Technically compliant, experientially failing.

How we approach it

1. Decide the information order before the layout

Desktop puts things side by side; a phone puts them in a queue. The moment side-by-side becomes a queue, something has to go first — and that is a decision, not a default. We set the order deliberately at each breakpoint instead of letting the browser stack elements in source order. This is the single biggest difference between a shrunken desktop layout and a genuinely responsive one.

2. Verify on real devices

We check every breakpoint for horizontal scroll, target size, whether the on-screen keyboard covers the form field being typed into, and whether images crop away their subject to fit. Most of these are invisible when you simply narrow a desktop browser window.

3. Serve images at the size actually displayed

A phone has no use for a 2,000-pixel-wide image. We output sizes to match the rendered dimensions and defer anything below the fold — usually the largest single win available on mobile performance.

4. Treat readability as a hard requirement

Measure, line height, type size and contrast all have defined minimums. Mixed Chinese and Latin text also needs its line-breaking handled, or you end up with a single character stranded on its own line.

Problems we most often find

• Horizontal scroll — usually a fixed-width table, an oversized image, or an absolutely positioned element escaping its container.
• Type too small — 13px looks refined on a desktop and requires squinting on a phone.
• Targets too tight — menus and buttons need real spacing between them or the mis-tap rate climbs.
• Content hidden on mobile — hiding sections to tidy the layout hurts both the visitor and indexing.
• Emulator-only testing — device emulation does not reproduce real font rendering or scroll behaviour.

Two plans

Blank Pro — from NT$ 80,000. For well-defined projects that need to ship quickly: professional service firms, industrial brands and personal brands.

Blank ProX — from NT$ 180,000. For multi-brand or multi-location businesses, sites with large structured catalogues, or teams needing strict permissions and audit logs.

Both include full source code and a private database, and both can add annual licensing and management. The comparison is on the home page — you should not have to ask twice to learn roughly what it costs.

Common questions

What is included?

Discovery, information architecture, visual design, front-end build, responsive work across breakpoints, baseline SEO setup and deployment. Domain and hosting fees, photography, copywriting and translation are quoted separately and itemised up front — never added afterwards.

How long does it take?

Four to eight weeks for a typical Blank Pro project, depending on page count and how fast content arrives. In practice the usual delay is not design or code — it is waiting on copy and images, so we hand you that list at kick-off.

Can we edit it ourselves?

Yes. You get your own admin area; changing text and swapping images is about as hard as editing a spreadsheet. Structural changes can go through the annual management plan.

Do we own the code?

Yes. Source code and database are handed over at completion — back it up, move it, or give it to another team. That is the fundamental difference from a subscription platform.