8 ms·
It's funny how I've witnessed a complete 180° change from how, in the 1990's, software was supposed to be entirely discoverable and it also came with a manual t
by crazygringo 4y ago
It's funny how I've witnessed a complete 180° change from how, in the 1990's, software was supposed to be entirely discoverable and it also came with a manual that documented literally everything, to now there's a ton that's hidden, often without any manual whatsoever... but you can Google everything you need to know.
Probably the single most useful skill I've had to learn in my life is, whenever you wonder something, just Google it. If you don't think your software does X... don't just assume it. Look it up.
I've been astonished at how often a feature was added 3 years ago to a program I've used for 8 years, or there's a secret swipe that avoids a bunch of menus, or an unofficial command-line flag.
And it really leaves me feeling deeply conflicted. Because on the one hand, I still believe in the virtue of learning your tools inside and out. I would read the manual and be proud I knew exactly what every program/language could and couldn't do. But on the other hand, is that really just a waste of time? Programs have so many features now, that instead of learning all the things via discoverability or a manual, we just learn them by... querying how to do things when we need them.
I don't really like the idea of so fundamentally relying on Google and forums and tutorials and Reddit and YouTube videos as the main way of learning how to use software. But at the same time, software does so much now and adds new things so quickly that it appears to be the only reasonable way.
- agumonkey 4y agoThis pattern is quite global. Everything is "more available" now, real time streamed, there's no apparent need for apriori organization since we can correct on the fly. Or so it seems. Games are patched live, browser in constant update etc etc
- layer8 4y ago> we just learn them by... querying how to do things when we need them. The problem with this is that you don’t learn any new features that you wouldn’t have come up with on your own. I loved reading the well-written manuals and “on-line” (integrated into the software) help of the 90s (and 80s) that explained all the concepts and features of the particular software. You’d learn a ton of new ideas and possibilities. It was really fun and exciting, and it gave you the perception of a well-designed and well thought-out whole. You built up a consistent mental model of the software, and you thus ended up with the feeling of mastery and control over the software. Nowadays it feels more like poking the software with a stick in an attempt to build a mental model and discover its capabilities by trial and error, often remaining in doubt about the actual intent of how exactly things are supposed to work.
- deleted 4y ago[deleted]
- thih9 4y agoI feel like I’m reading more manuals than ever. Libraries, CLI tools and other specialized software have well written and very useful docs. Same with pro camera software, music gear software, and more. For “consumer” software I usually don’t need manuals, I can find what I need via poking; this often includes power user features (when I use something sufficiently often). Is it possible that what you’re feeling is nostalgia? Have you actually read the manual for your phone?
- layer8 4y ago> Have you actually read the manual for your phone? I have, and it’s abysmal, because it doesn’t make any attempt at explaining anything on a conceptual level, or even explaining basic UI elements. It doesn’t teach you how to interpret what you see on the screen. It does the bare minimum of enumerating the steps to activate a given feature, presuming that you are able to match those descriptions to what you see on the screen (there are barely any screenshots) and that you know why you would want to use that feature in the first place. It also doesn’t address any failure modes, and doesn’t discuss relevant considerations regarding the use of the given feature.
- thih9 4y agoI see your point better now, thanks for explaining. That makes sense. Then again, today’s smartphone operating systems are as popular as home appliances in the 90s. Maybe if we took something modern that is as niche as software in the 90s then it might come with a manual with a mental model too.
- layer8 4y agoHome appliances also used to come with detailed and easy-to-understand manuals, and mostly don’t anymore. It’s mainly that manufacturers stopped caring, due to accelerated product cycles and globalization, because the products sell regardless.
- toast0 4y ago> but you can Google everything you need to know. It's hard to Google things you don't know exist. And it's hard to Google things that changed. If you've ever had a problem on macos, Googling is only useful if the problem is new; if it's been an issue in older versions, you're going to find all those questions and maybe some answers but they likely don't apply because Apple broke it differently now. Other vendors are not immune to this either, of course. I understand Apple actually does have manuals, they just don't print them and if they reference them, many people (including me) never noticed.
- morsch 4y agoMacs in the 90s, so System 6, 7 and 8, were full of hidden stuff. Clicking stuff while holding option, you would discover all kinds of interesting features and easter eggs. https://wiki.preterhuman.net/The_Macintosh/Newton_Easter_Egg_List https://wiki.preterhuman.net/The_Macintosh/Newton_Easter_Egg...
- WalterBright 4y agoI still can't find a list of all the command key shortcuts for Windows. Googling it yields lots of pages of partial lists.
- thih9 4y ago> also came with a manual that documented literally everything Note that iPhones have a manual too, it’s easy to navigate and quite comprehensive. E.g. here’s a page that describes the “trackpad” action: https://support.apple.com/en-gb/guide/iphone/iph3c50f96e/16.0/ios/16.0 https://support.apple.com/en-gb/guide/iphone/iph3c50f96e/16.... .
- Ankaios 4y agoEven the manual itself isn't discoverable. (At least I don't see an obvious entry to it in the iOS UI.)
- judge2020 4y agoThe "Tips" app has the User Guide available interactively with full Table Of Contents & search functionality. There are also more tutorial-esque articles for things like 'open control center' or 'take a screenshot'. https://support.apple.com/en-gb/guide/iphone/iph3afc3b3fc/16.0/ios/16.0 https://support.apple.com/en-gb/guide/iphone/iph3afc3b3fc/16...
- deleted 4y ago[deleted]
- jonas21 4y agoHave you tried googling "iphone manual"? The first result is the iPhone User Guide [1], which is a comprehensive manual that does document literally everything. The manual is also available as an 843-page ebook [2], and is accessible via the Tips app, which is preinstalled on the home screen. It's not quite like the days when a paper manual would be right in the box, but it's close. And I think most people would be unhappy if their sleek new phone came with an 843-page tome (not to mention how much paper that would waste). [1] https://support.apple.com/en-gb/guide/iphone/welcome/ios https://support.apple.com/en-gb/guide/iphone/welcome/ios [2] https://books.apple.com/book/id6443146864 https://books.apple.com/book/id6443146864
- mdemare 4y ago> The manual is also available as an 843-page ebook [2], and is accessible via the Tips app, which is preinstalled on the home screen. I didn't know that. I thought Tips was an app that gave you a couple of dozens of tips, and nothing else.
- userbinator 4y agoUndiscoverability strikes again! Would naming it "User Manual" be any better?
- chrismarlow9 4y ago"it just works"
- oliveshell 4y agoTo be fair, it does for most people. That’s why they’ve never read the manual.
- bosie 4y agoWhat metric are you using to establish that claim though? Most people don't know what they don't know.
- bobbyi 4y agoIn the 1990s, plenty of people felt obligated to drive to the mall, walk into B Dalton, and purchase a 300 page book to learn how to use their new software. There was a whole section for it. Today, they can find the equivalent information for free without leaving the device where the software is running.
- JKCalhoun 4y agoHard to say though if those books were in fact published by opportunists that surmised (correctly) that there was an audience out there that were either intimidated by the software manual (or assumed they would be without actually trying to read it) or who had pirated the software and so had no manual.
- 1-6 4y agoI actually miss picking up books like the Macintosh Bible where you can read through UI features. There was something fun about reading and then trying it in front of the keyboard.
- Gigachad 4y agoApple actually does have an extensive and up to date manual on their products which includes all those obscure convenience features. I don’t think much has really changed in this regard. The manual exists, is very easy to read and understand, but people don’t care because they get by without it just fine.
- ramraj07 4y agoAs an aside, the ability to stop yourself and know when to google something is what’s starting to separate the truly “smart” from everyone now - whether it’s coding, or general knowledge and discussions, or even when you’re just sitting in the toilet musing about some random question. Especially in coding I see this as the major difference between a good and great engineer - google things at the right time to find the best solutions. You don’t have to build it all yourself.
- xen2xen1 4y agoI'm very, very tired of the size of the backlog of stuff I probably ought to Google. It's too freaking long. Just make it easy to do without looking it up!
- userbinator 4y agoGoogle only helps if you know what you're looking for and it's a search that it happens to give you good results on. I've increasingly found the latter to be a problem, because when it comes to the point that I need to search online, it's probably not something easily found.
- toss1 4y agoYes it's great that we can Google/DDG most stuff at a whim. And there are often many great tutorials both written and video searchable online on a lot of software. That does NOT solve the original discoverability problem. >>I've been astonished at how often a feature was added 3 years ago to a program I've used for 8 years, or there's a secret swipe that avoids a bunch of menus, or an unofficial command-line flag. THAT is the problem right there. You're a likely typical example of someone who is smart, knowledgeable, experienced, and motivated, probably beyond what used to be called a "power user". Yet great swaths of features, and the work of scores of designers, developers, & testers for years, simply escapes our notice. The result is that vast amounts of productivity go squandered until we discover by chance accident or encounter with some "You didn't know this!" post. I've occasionally seen some introduction wizards be somewhat helpful, but they are never in any kind of depth. It's like they are afraid to show you what the software can really do — but the real case is some marketing dude thinks (likely sometimes correctly) that if the intro is too long, people will think it's complicated and won't use it. If that's the case, we're again being dragged down by the lowest (of most ordinary) common denominator. Solutions? How about the Quick Tour, and even the outline/TOC of a full manual, so we can at least skim it and see if some feature exists and then Google/DDG it...?
- DrewADesign 4y agoAs an interface designer I am completely confident that you're looking at old usability through rose colored glasses. Most software these days doesn't come with a big monolithic manual because it doesn't need one. More people directly use software now than ever before and most of them will probably never read a single line from a software user manual; not because they don't exist, it's because they don't have to. The vanishingly small percentage of folks very experienced with interfaces designed for professional software users– often using old interface flows and metaphors– get frustrated with software designed for everybody else. Your understanding of software usability isn't representative– that's why almost no open source software, no matter how big the manual is, gains anywhere close to the same usage as their commercial equivalents.
- theamk 4y agoThat's not what the article ssys though.. do you really think "everybody else" would have discovered the actions described without any sort of help page? I think the modern software does not come with the manuals because it simply has severly reduced functionality compared to the old days. For example, when was the last time you had used a navigation software with "avoid area" and "add custom road" features? There was always a tradeoff between "more features thus more UX complexity" (power user approach) vs "cut features to keep UX simpler" (UX designer approach). Sadly, the designers won.
- DrewADesign 4y ago> do you really think "everybody else" would have discovered the actions described without any sort of help page? No, the article is completely accurate about the lack of discoverability of those features. It highlights them because they are a direct contrast to nearly every other interface feature on iOS. That's what makes them interesting to interface designers. > I think the modern software does not come with the manuals because it simply has severly reduced functionality compared to the old days. Oh? > For example, when was the last time you had used a navigation software with "avoid area" and "add custom road" features? Did those navigation applications offer traffic overlaying satellite imagery? Public transit directions with real time vehicle tracking? Were you able to just type an address as we parse them or did you need to enter it in some weird little-endian order? Density of people at any given location, how many people are on a bus, or how busy Home Depot is? Up-to-date business hours? Alternate routes on regional rail and airlines? Up-to-date road closures even for temporal events? 3D photographic street-level POV navigation? Terrain maps? Cycling instructions? Weather? Descriptions of area attractions with an array of photographs for each? Wildfire maps? Hail you a ride share? The number of gained features dwarfs the number of lost features by an order of magnitude in software lasting that long. > There was always a tradeoff between "more features thus more UX complexity" (power user approach) vs "cut features to keep UX simpler" (UX designer approach). You're wrong. Our software today does vastly more than software of yesteryear. Most of it feels so natural-- like those maps features-- that you don't notice it coming into existence. It just sort of fits right into the ecosystem-- and that's the whole point. FOSS is a perfect example of what happens when software interfaces are assembled by developers rather than designed. I've been a developer, mostly towards the back of the stack, for a good 11 years. I also have art school education in interface design. Most developers have no idea how little they know about the way people use interfaces. To us, a GUI is a visual wrapper that facilitates interacting with the underlying software, like an API. Obfuscating functionality when it's not likely useful seems wasteful to someone used to reasoning about complex software. The problems arise when they take their personal usage preferences, assume they're representative of all users, and treat them as broadly applicable maxims in all of the software they create. Most users don't have the mental models in place to reason about the software functioning behind the interface-- to them, the interface is the software. An interface that doesn't consider what users need to and almost as importantly, don't need to see at any given point is confusing. Confusing is bad, so to them, the software is bad. To a developer, a confusing interface is something to be overcome by reading a manual. For example, you'll regularly catch professional photographers kvetching about the cost of adobe products... they have almost all tried Gimp but nearly none of them use it. There's little photographers (vs. say, graphic designers) can do in Photoshop that they can't do in Gimp... so why don't more photographers use it? Because it was designed by developers, for users who already have a mental model of the way software works with little regard for everyone else. Literally the only people you see advocating for Gimp are more FOSS fans than artists. Ask photographers why they don't use it and they'll mention the same things every time-- the interface sucks. It's confusing. Things are in unexpected places and function in unexpected ways. Affinity Photo, on the other hand, is starting to get a following. Photoshop is far from simple, but both the new user experience and the overall capability vastly surpass Gimp. That's why Adobe's userbase grows by millions of users every year despite direct competitors and people having complained about the price since they released v1. Software with expert users will either accommodate expert workflows or they'll no longer have expert users. Software with new users will accommodate beginners or nobody will adopt the software, if there's competition. Inkscape, on the other hand, enjoys a decent-ish reputation among professional vector graphics artists and unlike Gimp, is sometimes considered a viable tool of the trade. Illustrator and other tools do a hell of a lot more, but people don't roll their eyes when someone brings it up as a FOSS alternative. Design vs functionality is a false dichotomy. The fact that so many developers assume complexity in interface == good functionality is the reason open source alternatives are alternative rather than the standard. > Sadly, the designers won. Your misplaced blame betrays your lack of understanding of what interface designers actually do. Only managers controlling the purse strings want software to do less. Designers are perfectly happy doing the hard work of figuring out the best ways to communicate software's functionality by what is shown, and what is not shown, on any given screen. Could you imagine people with different domain expertise, like health insurance claims, designed the interfaces around people with their level of familiarity with the underlying systems? What would you say when they scoffed at your lack of sophistication when you refused to crack open a 400 page manual to file a simple claim? After all, it's right there on page 288 in the manual! How do you find it? Just look for 'adjustments, claims' in the index! How would you know to look for that term? "Hhhhhhhh... you don't deserve to have that claim filled!" Hyperbolic? Sure. But you shouldn't need an existing mental model of the underlying insurance claim machine to file an insurance claim, and that flavor of contempt for users not already understanding "how software works" is endemic in software development, and exactly what designers mitigate.
- copperx 4y agoI haven't encountered a professional software product without a manual yet. What you describe applies to software for mass consumption only. It might change in the future, but it would be a bit ridiculous for a company to sell a product for a professional without documentation.
- BeFlatXIII 4y agoI think you just articulated what my #1 blocker to mastering vim and/or emacs has been: they're both designed for the "mastery thorough thick manual" era. Dashing off to Google answers my immediate query, but often is far less instructive than a well-organized manual with an index at letting me discover the adjacent thing I actually need. OK, that's my #2 blocker. My #1 blocker is that I am no longer 15 and have things to do other than just poke about until I master a new text editor.
- 9dev 4y agoFor me, those are ancient tools for ancient times, designed when things really were different. We have other capabilities now, nobody is forced to work on the CLI anymore - I also refuse to spend weeks to „master“ my editor. Typing code is literally the least bad thing slowing me down when creating software.
- wruza 4y ago“Ancient” with regard to a living thing is usually a characteristic that shows an ignorance of features and a lack of experience with dynamics of toolsets. Truly ancient (obsolete) things get lost to history. We have other capabilities now, nobody is forced to work on the CLI anymore - I also refuse to spend weeks to „master“ my editor I agree with all of that, but from the vim side of things. Although these are not my main concerns with organizing a development process, I find it troublesome to set up and tune a modern IDE into a useful state either, and refuse to do that unless it’s a workplace requirement. Typing code is literally the least bad thing slowing me down when creating software. Typing code in vim-insert or emacs is the same as in any other editor. You press keys, they show up on the screen. Press F1 and type a command. Press a shortcut to enter files pane and select a file to edit. Press C-K C-9 to expand all user folds. Install a plugin, map some keys and now you can set and cycle through bookmarks easily.
- skydhash 4y agoIt’s not about typing faster. It’s about learning a language of editing. When you’re begin to be fluent in it, you will be communicating with the editor the changes you want to see. And it’s just a terse language that realizing what you want to actually do it and see it done take only one or two seconds. I strongly believes the “Think about it” -> “Express it” -> “See it done” is much better the whole ballet your hand would be doing with the mouse and keyboard.
- mannykannot 4y agoAll too often the search results are padded with advice for some other version than the one I am having trouble with, and it is difficult or impossible to craft a query specific enough to weed them out as the information simply isn't there. Then there is the problem of authors using product- and version-specific jargon that I haven't mastered yet, precisely because one can usually pick up the basic operations without reading a manual - "1. From the customization agent..."
- NonNefarious 4y agoThe G in "GUI" stands for "graphical." People forget that when they defend shitty, undiscoverable UI. The examples in this article are right on point. Apple (and others) far too often simply punt and give up on doing the necessary design work, burying functionality behind some bullshit like "long presses" or "gestures" or modifier keys or modifier-key-clicking on a text label that isn't even demarcated as a control. UI design takes time and thought; that's true. But why does a company with Apple's resources not bring the necessary effort to bear on it? It's not as if they can't afford it. Sure, there are time constraints, but if you're going to fold to those and trowel out shitty UI, then don't presume to publish "human interface guidelines" or other such bibles. And it's high time to stop tolerating smug douchebags who denigrate any complaint about missing functionality and declare, "Well, you simply long-press Option-Shift-Command-Q to bring up the configuration menu."
- davedx 4y agoI really LOVE how rust approaches this: provide as much help as possible in the compiler error messages. Not sure if they were inspired by elm that does this too, but it means you do a lot less context switching between your program and “the manual”/stackoverflow/whatever else.
- gmadsen 4y agoI think relying on google might be too far, but there is certainly a middle group. My linux tools usage vastly improved by switching to a newer shell , with auto complete, pop up man pages, syntax checking arguments before executing, etc. Same with vim and tmux. Also using modern cli tool replacements that rust made popular. I wasted so much time when I was younger remembering things that provide a very small to no advantage if you do the above instead. So, I'd say, google can be wrong, the ideal case is modify your existing tools as needed to maximize discoverability and minimize friction to actual documentation
- numpad0 4y ago> I've been astonished at how often a feature was added 3 years ago to a program I've used for 8 years, This looks suspiciously similar to lifecycle of a social media, especially how they grow new features and eventually dies when users migrate. Maybe it's a viable strategy for a social media, mobile OS, MMORPG, anything aaS to not explain features or educate users, but to grow as users consume added mechanics, until it becomes impossible for new users to catch up and old users to keep up?