4 ms·
I dislike his redesign, because most of what he does is fix the fact that it's ugly. Large-printing the numbers is pointless when the labels are still teeny-ti
by Pxtl 9y ago
I dislike his redesign, because most of what he does is fix the fact that it's ugly. Large-printing the numbers is pointless when the labels are still teeny-tiny and the layout of the tearable stub doesn't match so it's non-obvious that it contains the same info.
Imho, the tearaway should clearly repeat the layout of the big one so the reader can see "this is the same".
I'd sort the data in order. Putting the zone at the end is wrong because you don't use it after the seat. First you need flight number and time, then you gate days where to go, then your zone says where to go, then your seat says where to go. It seems obvious to sort the data like that.
- et-al 9y ago> I'd sort the data in order. Yeah, I liked Julian Montoya's design the most because its vertical layout immediately conveys a hierarchy of data (though the gate number is omitted). The other designs, while aesthetically novel, required my eyes to jump around to gleam meaningful information.
- Pxtl 9y agoMy problem with Montoya's design is that he used 3 letter abbreviations for the cities... You need the full name. 3 letter airport abbreviations are jargon that should not be the core of user-facing interaction.
- dx034 9y agoThey can be important. It's important to know if you're flying to LHR or LGW (for London), esp if you're at an airport where planes of the same airline leave to both. Identifying the flight by flight number is often problematic if it's a codeshare flight (displays at the airport only show one or switch infrequently), so identifying by airport and flight time is easier.
- mjevans 9y agoPutting the zone at the end is actually OK for humans; It's an edge. It could even be distanced a little from it with some small 'zone' text.