Pixel-identical modals across platforms

WHAT THIS TESTS The interviewer wants to see that you treat consistency as brand-level, not pixel-level, and that you proactively surface platform conventions before building. Blindly matching pixels breaks native muscle memory.

A GOOD ANSWER COVERS Raise the interaction differences first. Android users expect the system back gesture or button to dismiss a modal, while iOS users expect a swipe-down on a sheet and often a grabber handle. Layout differs: safe areas, notches, home indicators, and status bars vary, and the soft keyboard pushes content differently on each OS. Accessibility expectations diverge, including focus trapping, screen reader announcement order (TalkBack versus VoiceOver), and dynamic type or font scaling that can break a fixed pixel layout. Performance and available native components differ too. Propose keeping the visual language consistent (colors, type, spacing) while honoring each platform's interaction conventions, and confirm this tradeoff with the designer before coding.

COMMON WRONG ANSWERS Simply agreeing to pixel-perfect parity and starting to build, ignoring native expectations. Forgetting the Android back button and gesture entirely. Overlooking safe areas, keyboard insets, and accessibility differences that make a fixed layout fragile.

LIKELY FOLLOW-UPS How do you keep brand consistency while respecting platform norms? How do you handle the Android back button for a modal? How do dynamic type and font scaling affect a fixed design?

ONE CONCRETE EXAMPLE You tell the designer the modal can share colors, typography, and spacing across platforms, but on iOS it should present as a sheet with swipe-to-dismiss and a grabber, while on Android the back gesture must close it and content must respect the gesture-navigation insets. You also flag that VoiceOver and TalkBack announce dismiss controls differently, so the close affordance needs platform-appropriate labels rather than one fixed pixel design.