Seems like creating a buzzword for no reason. Correct me if I’m missing something, but how is this not just thinking about animation and video in the user interface? How does it not fall under UI, UX, or content (which in my opinion are already splitting hairs and share a ton of overlap?)
Thanks for the feedback! I tried to keep the restrictions of the current technology, though certainly different sized displays would yield all different sorts of likely better designs. The current newest clocks are just computers displaying a webpage so in terms of technical capability they can do pretty much anything within reason.
It’s mostly ridiculous because line-height should always be defined as a unit less number. It’s a ratio of space to characters, so just define it as a number that will be multiplied by the font size. This is a fundamental of web typography that many people miss.
I think next train at a terminal would be handled in the same way — obviously less need to show the next two trains as well, but you want to know which track will depart soonest, and when it will depart. The proposed design supports that well.
I’m gathering feedback for a follow-up and will definitely incorporate a mockup of a pre-swipe sign as well!
I think we also need to consider what text is best to show for the destination, not just output whatever internal designation is set for the terminal. Longer names can all be reduced and still carry the same meaning: Eastchester-Dyre Av and Dyre Av mean the same thing to anyone looking for that info. In many cases “Uptown” or “The Bronx” would be even better.
Thanks for the thoughtful response! Curious what you found lacking about the solution for this in my design, which shows the next three trains to come.
Also, I just removed the bottom bar with the time and service info from the equation for the exercise but it’s definitely an important element that would stick around!