2 ms·
Well, there are two ways to address the problems you're discussing. One is to create an advanced UX that is both comfortable for simplistic use cases but also e
by tsimionescu 6y ago
Well, there are two ways to address the problems you're discussing. One is to create an advanced UX that is both comfortable for simplistic use cases but also efficient for advanced use cases.
The other approach is to create two or more programs: one for (each) basic use case, that can't be used further, and one that supports the gamut of advanced use cases, with UX optimized for efficiency.
The first approach would be ideal, but in my experience it is extremely difficult if not impossible, just because of UX considerations - often times, what is efficient for an expert will look arcane and confusing to a basic user.
The second approach is more promising, though it also has its problems of course - most notably, the fact that the advanced program can easily become very difficult for beginners who do need/want to become experts.
- TeMPOraL 6y agoI generally agree. I'm definitely not asking users to jump into the most complex, feature-rich software suite they can find :). And the industry is definitely choosing to focus on developing programs for basic use cases. The problem I see with this are as follows: - The basic use case is the only one that gets developed :). That's where the money is, that's how you make userbase grow fast, and that's where my complaint about following "best economic decision" comes from. The oxygen gets sucked out from the market. - The software may only provide for base use cases, but that doesn't mean it has to be bad at it. The bar for improvement is really low here. It's fine to be focused, but you can still leave room for users to grow - to get better and faster at using the existing functionality. So e.g. you don't need to turn your photo filter app into the next Photoshop, but you could add keyboard shortcuts to all operations, allow users to apply the same operations to a batch of photos, and let them save the result in a commonly understood format (instead of just proprietary one). Shaping the learning curve is always tricky, but there's plenty of room between notepad.exe and Emacs. We don't have to build software only at the extremes. (Related: simple software for basic use cases is half of the hallmark of UNIX philosophy. The other half is that software needs to compose well. While traditionally applied to niche CLI programs, these principles work well in general-purpose GUI applications too.)
- tsimionescu 6y agoI absolutely agree with everything youve written here.