While I’m griping about Instagram, why the heck are the detailed notification preferences split between the app and the system notification UI?
That’s terrible design.
Well, if it’s intended for usability, anyway.
If your goal is to make people see more notifications, though… 🙄
IMO there are two sensible ways to handle granular push notification preferences:
- Use the system’s per-app settings for all of it. (Tusky does this, even putting your per-account preferences in the system UI.)
- Use the app’s settings for all of it, and let the system just be an on/off toggle for what you’ve chosen in the app (like it was before Android even had UI for it).
Either way, everything’s in the same spot so you know you haven’t missed anything you want to turn off. Or anything you want to turn on, for that matter.
Also on Mastodon.
Sometimes it takes longer to automate something than it would to just repeat it yourself. Calvin designing a robot to clean his room, for instance. The method of estimating how long it takes to do the thing, how many times you have to do the thing, and then how long it would take to automate doing the thing, is a pretty good guideline.
But there are other factors: Like, can you include it in a checklist? If not, what are the chances that you’ll forget to do the thing? And what happens if you forget? What if you might hand things over to someone else and three people down the line, the fact that you need to do the thing doesn’t get passed along?
Or what if you have a situation like Desmond at the Dharma Initiative numbers station, and they know the step is “required,” but don’t know why? (Not that you’re likely to have quite so severe a failure mode!)
Anyway, today I automated some post-processing on a site that I hardly ever change. Not because it’s a pain to do the post-processing. Not because it takes a long time. But simply because if I don’t build it into the process, the next time I change something a year down the line I’ll probably have forgotten that I need to do the post-processing!
I was looking for sandals and found these. They’re flip flops with a built in bottle opener, I suppose to make them more…cool? Gadget-y? But it’s on the sole of the shoe.
Someone really didn’t think this design through.
Update: There are some replies at Wandering Shop from people who’ve worn or used these. Apparently there’s another variation with a built-in flask.
Putting a straight-party checkbox on a ballot violates a key design principle: The polling place and ballot should strive to avoid steering people toward specific choices. This is also why some places randomize candidates’ names or stick with alphabetical order.
The human brain would rather work on auto-pilot than think carefully. Give it an excuse to stick with auto-pilot, and it’ll happily do so.
Even if that means outsourcing your vote to the people who chose the slate and designed the ballot.
You can choose to vote a straight-party ticket, but the ballot design shouldn’t influence you to do it.
I figured out exactly what bugs me about Twitter and Facebook showing your friends’ “likes” in the timeline. It’s not just that they’re public — that’s true on Tumblr or Flickr or Instagram too, but you only see them when you choose to look for them.
It’s that broadcasting likes in the newsfeed blurs your intent.
- A “like” is a message to the original post’s author (and a bookmark for yourself).
- A retweet or share is a message to your friends or followers.
Putting them in your followers’ feeds turns a “like” into a message to them as well, even though it’s not what you intended. (If you wanted to share it, you would have shared it, right?) It’s a step above completely frictionless sharing, but it still messes with the signal/noise ratio of the timeline.