Call me crazy, but I actually like using things like paragraphs containing actual sentences comprised of things like, I dunno, subjects, verbs, and objects. /s (sarcasm).
In other words, I eschew the software engineering norm of using inane terse commands such as “Snooze” which probably came about due to tiny displays that were difficult to read back in, say, the 1950s and 1960s.
No, I’m not going off on a bizarre tangent.
Here’s how you could make this easy for both Mark Suster’s novice and pro.
Give users a message, which engineers would probably consider, ridiculously long and better placed in the documentation (which, nobody reads, yet devs adore bikeshedding about in, absurd discussions like this Technical Writing Courses https… //news.ycombinator.com/item?id=22652241).
SOMETHING LIKE THE FOLLOWING BELONGS IN THE ACTUAL VIKUNJA APPLICATION, NOT MERELY IN THE DOCUMENTATION
I AM NOT SHOUTING… I AM SCREAMING AT THE TOP OF MY LUNGS!!!
Dear Mr./Miss/Mrs. User,
Notifications can be helpful; yet, notifications can also be overwhelming. Striking a proper balance is often deceptively difficult.
Of course you don’t want to miss an important notification, yet you almost certainly aren’t going to want wake up to 47 emails because Ben or Naomi changed a task, 47 times over the course of, say 5 hours last night.
Therefore, we here at Vikunja World Headquarters (my living room), have decided to follow the sage advice in the quotation generally attributed to Albert Einstein, “Everything should be made as simple as possible, but not simpler.”
Put simply, this is a complicated matter. Therefore, we are going to provide you with many different choices. However, please don’t worry, you can configure all of your choices in, say, 10 seconds right now, or in, perhaps a few hours over the course of, say, a couple of months or even years. It’s up to you. And, yes,of course, you can change your mind.
You can configure notifications for a particular task, a particular user, or globally (for all tasks and all users). Regardless of how you configure them generally, you will be able to customize the notification settings for each particular task
Here’s a 10 second choice…
Always receive an email notification every time, anyone makes a change to a Task
Simply choose that option and will be all done configuring notifications… but, if you actually use Vikunja, we think you will quickly want to change that option because you will tend to get overwhelmed with notifications.
Here’s a 20 second choice… Receive an email notification every time, anyone makes a change to a Task, but not more frequently than every A days, B hours, C minutes, and D seconds [For this I eschew unnecessary pull down menus in favor of allowing users will enter number in manually].
For example, you might choose to Receive an email notification every time, anyone makes a change to a Task, but not more frequently than every 15 minutes.
That way, if Susan were to make 4 changes in 12 minutes, you would only receive one notification.
Here’s a 30 second choice… Receive an email notification every time, anyone makes a change to a Task, but not more frequently than every A days, B hours, C minutes, and D seconds [For this I eschew unnecessary pull down menus in favor of allowing users will enter number in manually], but only send notifications between hour X and hour Y.
For example, you might choose to Receive an email notification every time, anyone makes a change to a Task, but not more frequently than every 45 minutes, only between 7AM and 5pm.
That way, if Mike were to make 6 changes in 1 hour and 20 minutes between 7am and 5pm you would only receive two notifications, but you wouldn’t receive any notifications between 5pm and 7AM.
As you have probably surmised, this follows Mark Suster’s advice Design for the Novice, Configure for the Pro
They key thing is having a proper user interface. I envision something that would be a bunch of sentences would could be dragged around to form a series of paragraphs.
It probably sounds incredibly difficult based on the complexity, but I assure you it’s merely a bunch of boolean logic presented in a very user friendly manner.
For example, please take a look at these Trello cards…
https… ://archive.is/wip/f7M8X. (The link is on Medium .com; I used Archive.is to get you past their soft paywall).
The inherent problem with most settings in software applications is this: they normally fail to use parts of speech subjects, verbs, objects, articles, prepositions, etc. They also rarely use complete sentences; and almost never use one or more paragraphs.
I am not talking about documentation; I am talking about linking huge amounts of text as part of the UI/UX (user interface/user experience). Think of Wikipedia. Sure it can be overwhelming, but it doesn’t have to be.
In 20 seconds, an ordinary reader could learn this about bicycles…
A bicycle, also called a pedal cycle, bike, push-bike or cycle, is a human-powered or motor-assisted, pedal-driven, single-track vehicle, with two wheels attached to a frame, one behind the other. A bicycle rider is called a cyclist, or bicyclist.
An expert could go down a “bicycle rabbit hole” for hundreds of hours.