The problem
The same screens had to work beside a customer and across a showroom, in landscape and portrait.
At sales events, staff had no good way to present a project at a booth or sales gallery. The answer was a presentation mode: one project at a time, with site plan, floor plans, unit types and facilities.
Four layers
Components only read the last layer. Everything device-specific sits in the scale factor.
The palette and base sizes.
TV, landscape, portrait.
Sizes for this screen.
Text, surfaces, actions.
Five TV layouts from one tablet screen
I started from my landscape tablet screen, 1194 × 834. For the TV, I made a moodboard of streaming apps. Three patterns kept coming up: no fixed nav bar, full-bleed images with a dark scrim, and rows of thumbnails.

Netflix, Prime Video, Hulu, Apple TV on TV and on iPad
What I took from the references
The project photo fills the TV. Price and details sit on a dark glass card over it.
Floor plans line up in a row. The selected plan is larger and has an orange outline.
Only three sections, playback and close stay on screen. The floor-plan screen drops the bar for chips.
Then I had AI generate five layouts of that screen, using every element (even four hidden Figma layers) and the file's own colour and type variables. Only the layout changed, so I could compare directions on the same tokens.
On the TV, a project plays in three parts
Then I designed the TV screens. Each project runs as three sections in a slim top bar: project details (รายละเอียดโครงการ), the look and feel of the project (บรรยากาศโครงการ) and register (ลงทะเบียน). An orange line under the sections fills as the project moves from one part to the next.
Staff stay in control from the same bar: pause (หยุด) or play (เล่น), the previous project (ดูโครงการก่อนหน้า), the next project (ดูโครงการถัดไป) and close.

Project details: the first of three parts
- Details on one card. Starting price, land and house size, bedrooms and floors sit on a dark card over the photo, with two actions: see the location (ดูทำเลที่ตั้ง) and see floor plans (ดูแบบแปลน).
- Look and feel. Eight photos a page in a four-by-two grid, with arrows and page dots.
- Register by QR. A large QR code over the project photo. Customers scan it with their own phone, so nobody types on the TV.

Look and feel: eight photos a page

Register: scan, no typing on the TV
I tried the floor-plan screen several ways
Every arrangement has the same parts: chips for the master plan and each unit type (แบบแปลน, Unit A, Unit B, Unit C), the plans themselves, and a panel with the usable area, number of units, floors and facilities. Each facility is an orange icon with a label.
They differ in two things: how much room the selected plan gets, and whether the panel sits beside the plans or under them.

A · Panel beside the plan, thumbnails below

B · Selected plan large, panel below

C · Compact row, every facility in view

D · Selected plan grows inside the row
On a tablet, the details card moves when you turn it
The tablet keeps the TV's top bar, sections and playback controls. In landscape (1194 × 834) the details card stays on the photo, as on the TV. In portrait (834 × 1194) the details move under the photo, and the two buttons share the full width at the bottom.

Tablet, landscape: card on the photo

Portrait: details below
Designing for a 10-foot screen
- Focus, not hover. On a TV there is no cursor, so every interactive element needs a clear focus state and a predictable order.
- Bigger targets and type, from the scale factor. No separate TV components.
- Presentation first. The TV is for showing a customer. No data entry.
Checking the code first
The code used the framework's default type scale about 50 times, and 5 of the 13 project tokens were never used. Nobody had chosen that default scale, so tokens should replace it.
No font family was set on iPad, tvOS or Android, so everything used the system font. Line-height and letter-spacing were rarely set. With no shared text component, each screen set its own size and weight, and one style appeared three ways.
Also in these two months
I also worked on a pre-sales bid for a LINE Official Account service platform. That work is in the pre-sales case.