40

Dev: This content might be too large to fit into this area on mobile.
We might need to add scrolling or design it differently.

Designer: It fits perfectly in the design.

Dev: But the user might have a smaller screen size than in the design.

Designer: We don‘t optimize for small screens.

Dev: But we still need to handle it somehow.
Also, the text might be longer for other languages.

Designer: No problem, we will provide short text for all translations.

Dev: We have 30 languages and the translations are made by a third party. We can not control it.

Designer: We‘ll manage somehow.

Dev: Also, the user might be using an accessibility setting on the device which makes the font size larger.

Designer: Unlikely

Dev: Also, the available screen size might be reduced by the on-screen keyboard.

Designer: … Ok then.

-

It‘s always a conversation like this. It repeats indefinitely.

Comments
  • 4
    I hate people like this
  • 9
    "Optimized for Internet Explorer 6 @ 1024 x 768"
  • 1
    Here the only screen property anyone should optimise for: "screen works".
  • 0
  • 0
    @Lensflare If the screen doesn't work, then you can ignore it - and that's about the only valid reason.
  • 4
    @Fast-Nop well, devs and designers have a different idea of what "works" means ^^
    At least in the concept phase.

    After the actual implementation, I bet both would agree that clipped content doesn’t count as "works".

    The hard part is to convince designers why a design won’t work.
  • 0
    @Lensflare Hopefully not the Todd Howard "It just works." Where crashing is acceptable.
  • 2
    I usually give up after 2 exchanges .. it's a lost cause
  • 1
    @Lensflare I don't mean that the website works. I mean that the screen works. As in, it's not defect.
Add Comment