Physical buttons with the indicator lights on the button - to do a hard reboot of a computer you need to hold down the button until the light goes off - the light that your finger is covering
These two remind me of many in-house apps at work that would send you to a web page that said “click the purple arrow below to continue”, and yes indeed there was always a nice big purple arrow to click.
This all was a side effect of some clunky implementation of Single Signon (SSO).
I imagine that both apps in your case are doing something similar with SSO, sending the browser to a SSO server that puts some token in a cookie and then sends them elsewhere.
If the cookie isn’t there, the middle website would prompt, using LDAP somewhere to do the authentication. In other cases, there might be a different kind of token present that the SSO site could deem “sufficient” and then insert a token for the specific application.
When it works as intended, you see a brief redirect followed by the app, with you automatically logged in. If things are done with less finesse, there are often middle pages that crop up.
It probably is something with a single sign-on system. But the funny thing is, with the first one at least, you can bookmark the online textbook, and once you’re logged in to the main course site, the bookmark for the textbook just works, just like you’d expect it to.
Apple’s philosophy has always seemed to be style over function. One of their bright ideas that really irked me was translucent menus. Yeah, they look cool, but it’s HARD TO READ the text on the menu when the background is showing through. I think a pretty basic principle of UI design is “don’t deliberately make the UI hard to use”.
I think the idea was that “yes” and “no” buttons, or “OK” and “cancel”, require the user to read, parse, and understand the sense of the question being asked.
Suppose you click on a link in a website and a dialog comes up.
You have to read it carefully enough to understand what it’s asking; does “yes” mean I want to continue or want to stay? I think that’s why designers shifted to buttons with verbs like “continue” and “stay”; you can just scan the question and get a general sense of what it’s asking, and the buttons are obvious.
That said, bad design is still far too common.
My last employer had an HR app (think it was for scheduling time off) that had a perplexing UI - if I wanted to cancel a given PTO event, I would select it, get a box with EDIT or CANCEL options, click on CANCEL, then it would put up a confirmation box that had OK or CANCEL options, but this time, clicking cancel would cancel the cancel.
If they built the confirmation dialog to say something like Confirm Cancelation or Exit Without Making Changes, it could have been more obvious.
When I was in college someone showed me a website called the User Interface Hall of Shame that highlighted many of the things people here are complaining about. It looks like the site still exists, but it also looks like it hasn’t been updated in 22 years.