Breaking the problem down into features
We’ve seen in several chapters before this one how a good approach is identifying the features we need to implement. These features are less about reading and writing data and more about ensuring the design and interaction work well on prioritized devices. You might therefore have a feature breakdown looking like the following list:
- Should render the basket page in a double-column design for landscape mode.
- Portrait mode:
- Should render the basket page in a single column for portrait mode.
- Should display menu actions at the bottom of the screen.
- You should hide certain features, say, X, Y, Z (assuming X, Y, Z are available on a desktop with a wider screen). The point of this requirement is that you must “rethink” what a mobile experience is versus desktop, what features are central to the experience, and what features we only show if we have plenty of screen space to show it...
