@remixmanifesto I’m certain it has something to do with the schedules being built from BC Ferries point of view. Somewhere deep in the bowels of BCF scheduling, it somehow makes sense to someone to sort sailings by time of day first, and day of the week second. Somehow that leaks out. #Has4years
Fourth: it’s not hard to detect when a user is using a mobile browser. Heard of ‘mobile first’ design? Your desktop users would love it. For an outfit that can’t rely heavily on advertising without looking bad, it shouldn’t be hard to pick what’s relevant to a given user.
@BCFerries 10 years ago , as a web developer, I offered to build schedules for your site, since they need help. After your recent rebuild, they still need that help. Today I missed a birthday dinner with my bubble because of this page.
Third, why would the thing I’ve click prepped receive equal billing compared to an alternative that silently takes me back only 1 step, crucial though it may be?
@remixmanifesto As you know, one challenge is that the schedule changes seasonally. So two weeks from now the schedule will be different, but yeah... you don’t even really need to show THAT to the user at all either. We don’t care about the massive change that happens inside BC Ferries.
@remixmanifesto Well... people gotta plan. But today’s users should be favoured. Frankly, not that hard for an app to know you’re far from home and tell you your options for getting home.
@remixmanifesto Fonts, colours, white space, more or less fine. It’s the underlying information architecture that needs some user focused attention. That it’s lived on this long should be a text book example of how to not do things by now. The example would survive to the third printing.