TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

User Driven UI

183 点作者 bradwoodsio将近 2 年前

30 条评论

hsn915将近 2 年前
The main challenge in UI design is balancing between:<p>- Allowing the user to perform desired operations in as few steps as possible<p>- Without cluttering the screen with all kinds of irrelevant controls<p>These constraints can be at odds:<p>Every time you hide some feature away in a menu, you are adding steps the user has to perform to achieve what they want<p>On the other hand, presenting every single feature on the screen all the time just clutters the UI and makes the user feel confused<p>It&#x27;s no good to let the user decide what goes on the UI either: you&#x27;ve now just burdened the user with the job of creating a UI for your application.<p>Other constraints:<p>- Make sure all features are &quot;disocverable&quot; by just casually playing around the UI.<p>This rules out the idea of &quot;hiding&quot; things until the user triggers some kind of magic incantation.<p>Command pallets and shortcuts are great ways for enabling power users to perform operations quickly, but the product must have other ways for exposing features that is predictable and boring. Menus are a great way to do this. A user casually playing around with buttons and menus will eventually discover features, and they will also eventually learn the shortcuts for them.
评论 #35991469 未加载
评论 #35990124 未加载
pavlov将近 2 年前
These ideas have a strong late 1990s vibe.<p>Desktop app complexity had grown over a decade so that Microsoft Word, which started with a simple single-row toolbar, now was taking over 30% of a typical PC screen with a sea of icons and controls. Meanwhile the growth in PC sales meant there was an influx of non-corporate users who were not being trained to use the apps.<p>That’s how we got Clippy (essentially similar to the text input box proposed here), “progressive”menus that hide advanced actions and features the user hasn’t been accessing, as well as the explosion of task-oriented panels in Windows XP.<p>The execution of these ideas left a lot to be desired. (The Office 2006 Ribbon UI was actually a meaningful step forward because it contextualized and prioritized the UI rather than hiding stuff. Microsoft has solid data showing that Ribbon improved the user experience.)<p>Maybe language model AI can give this kind of UI a new lease of life.
评论 #35986062 未加载
评论 #35985840 未加载
评论 #35989975 未加载
评论 #35989683 未加载
littlecranky67将近 2 年前
UI is no longer user-driven as in giving the user the best possible experience. It is <i>business model</i> driven, I.e. utilizing dark patterns (&quot;Yes&quot; | &quot;Ask again later&quot; dialogs), data&#x2F;telemetry collection for advertising, showing &quot;pro&quot; features pretending to be available just to tell they require upgrading when trying to use etc.
评论 #35991530 未加载
asimpletune将近 2 年前
I really like the site owner&#x27;s &quot;digital garden&quot; metaphor. One of the problems with social media is they&#x27;ve constrained personal websites to a standard format, and this has molded creativity around what a personal website should look like.<p>For example, if people were somehow forced to make their own sites, they would find that the content they have to share is not quite blog, not quite portfolio, not quite photo gallery, etc.. sort of like geocities of the 90&#x27;s. It&#x27;s actually a hard problem.<p>In general, I really enjoy personal websites because they show different people&#x27;s attempts at solving this problem, and the digital &quot;garden concept&quot; is a cool metaphor.
评论 #35990272 未加载
d0m3将近 2 年前
VS code (developer interface) has this feature where you activate a text input with a hotkey. It is used to trigger specific actions. You can type text and it will give you the actions that match the text. You also see a list of the actions you triggered that way previously. This is great because I don&#x27;t have to remember how to trigger a specific action and I can also discover new actions just by searching. Ultimately it doesn&#x27;t change the UI, but it sounds quite similar to what the author describes. There is some potential there with a search bar that is more about intent than text matching.
评论 #35988728 未加载
评论 #35986812 未加载
评论 #35987636 未加载
jmacd将近 2 年前
In the early 2000s Microsoft did a lot of research in to &quot;Inductive User Interfaces&quot;. [1] The closest approximation still around would be Wizard interfaces.<p>Creating those UIs was so rewarding, as you really had to focus on the goals of the user and figure out the branching that could get the right user to the action or activity that they needed to perform.<p>My first &quot;startup&quot; was a tool for life insurance agents to recommend products to their prospective customers. IUIs were perfect for scenarios like that. You could abstract away a lot of complexity.<p>They were also great for accessibility.<p>1: <a href="https:&#x2F;&#x2F;learn.microsoft.com&#x2F;en-us&#x2F;windows&#x2F;win32&#x2F;appuistart&#x2F;inductive-user-interface" rel="nofollow">https:&#x2F;&#x2F;learn.microsoft.com&#x2F;en-us&#x2F;windows&#x2F;win32&#x2F;appuistart&#x2F;i...</a>
bityard将近 2 年前
I don&#x27;t think you need AI for this, VSCode and lots of other applications already have a &quot;functionality search bar&quot; built right into the program. (Often euphemized as a command palette).<p>I myself don&#x27;t use them much but I can see where they are useful to the &quot;new users&quot; the article speaks of, to discover and unlock features as the user gets more comfortable with the program.
评论 #35994754 未加载
CTDOCodebases将近 2 年前
I might just be me but as I get older I&#x27;m finding it harder and harder to navigate UIs even though I&#x27;ve been an early adopter of technology throughout my life. I wonder if it is a sign of cognitive decline or just the consequence of having to remember an increasing amount of perpetually changing UIs.
评论 #35985821 未加载
评论 #35986135 未加载
评论 #35985723 未加载
评论 #35986154 未加载
评论 #35985678 未加载
phosphorco将近 2 年前
Nice article. An alternate is completely unrelated to AI&#x2F;GPT and rather, the basic use of a command bar&#x2F;palette. Provides a lot of new ways to approach UX.
评论 #35985848 未加载
simulo将近 2 年前
The suggestion is similar to the &quot;search a command&quot;-UI that some more complex destop programs have in their help menu.<p>The idea to use text more actively in user interfaces is not new, there were&#x2F;are these ideas, for example:<p>- Gentner&#x2F;Nielsen: The Anti-Mac Interface, 1996 ( <a href="https:&#x2F;&#x2F;www.nngroup.com&#x2F;articles&#x2F;anti-mac-interface&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.nngroup.com&#x2F;articles&#x2F;anti-mac-interface&#x2F;</a> )<p>- Raskin’s ideas as in &quot;The Human Interface&quot;, 2000 and the Canon Cat, 1987: ( <a href="https:&#x2F;&#x2F;www.reproof.app&#x2F;blog&#x2F;on-designing-a-more-humane-computer" rel="nofollow">https:&#x2F;&#x2F;www.reproof.app&#x2F;blog&#x2F;on-designing-a-more-humane-comp...</a> )<p>- Wirth’s Oberon Operating System: <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Oberon_(operating_system)#User_interface" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Oberon_(operating_system)#User...</a>
kossTKR将近 2 年前
I&#x27;ve always found it weird that a &quot;function search&quot; hasn&#x27;t become more mainstream.<p>It&#x27;s easy to implement without AI. Just make a big list of your functions, describe them verbosely, and give them a link - now let the user search for what they want to do and send them there.<p>I remember Rhino3d having this 10 years ago and it was amazing while all kinds of daws, editing programs, desks etc. would be a jungle to navigate or just have a &quot;docs&quot; or &quot;help pdfs&quot; - such a waste of time to look through.<p>In general this kind of navigation has been overlooked for decades.
评论 #35987968 未加载
trabant00将近 2 年前
Current UI designs have business constraints that just can&#x27;t allow for much change. The user is not the customer, the user can&#x27;t be bothered to invest time to learn as there are multiple apps competing for their attention, if the user is familiar with some UI design you can&#x27;t give him a completely different design regardless of how much better it is and so on.<p>In spaces where the business considerations are different (aviation, medical devices, mature open source projects, etc) the UI is pretty good for the target users.
jksmith将近 2 年前
A sidebar to this includes abusing &quot;easy&quot; to equate to &quot;requiring less energy&quot; to operate. An increase in stress equates to more energy used. To wit, being forced to find differences in ui functionality across mobile and web for the same app. Or clicking on a control that just jumped location because of a slow page render. Or maybe just gratuitous (debatable value) in ui changes between windows versions.<p>OG get off my lawn stuff: When I first started writing code back in 1989, I worked on a tui desktop app that was extremely refined to facilitate data entry from a piece of paper. Sort of a microscope split your vision between paper and instrument. Everything about the tui was custom and optimized via tons of user feedback. By far that app still represents an example of the least energy required to get something valuable done on a desktop. Yes, specific use case to a large degree, but the tui framework we built suggested ease of use for tuis in general.<p>Redoing the app in windows killed the experience to a noticeable degree. The point is, suggest that generalized ui tool constraints will force the user to expend more energy, in some way at some point. Obvious point, but there is no perfect ui solution, especially in today&#x27;s world. Only trade-offs.
wpietri将近 2 年前
I like where they&#x27;re going, but I think the model is too simple. There&#x27;s no &quot;a user&quot;. Software is a response to <i>populations</i> of users.<p>An MVP is always focused on a very specific audience, the early adopters for it. It can be minimal because it&#x27;s for a group of highly motivated people eager to solve a specific problem. They tend to be both experts (in the specific problem space) and explorers (in their willingness to try things out).<p>By the time a product has spent a few years growing, it is often addressing the needs of a much broader set of users, which presents a much bigger UI challenge. But it&#x27;s not just a UI challenge. Take film&#x2F;video editing, for example. The original film editors were all using physical gear to splice actual film together. [1] The initial target for computer-based video editors was those same expert film editors. One of those editors who made the switch pointed out that people knew they didn&#x27;t know how to use his complicated set of physical tools, but assumed that since it was on a computer, they too could edit film. [2]<p>That wasn&#x27;t the case, though. If you want to go from addressing the population of &quot;expert film editor&quot; to &quot;person who wants to be come an expert film editor&quot; it&#x27;s a radically different problem. A very valid solution to that is keeping the interface as is and saying &quot;go take a class&quot;.<p>Then you also have populations like &quot;person who doesn&#x27;t want to become an expert editor but wants to share a tolerable video of Bobby&#x27;s first birthday&quot;. That&#x27;s an argument not for a modal interface, but for a tool built for that audience and no other. Maybe it&#x27;s a cut-down version of the expert one. But just as likely as it&#x27;s something that does not work with a pro editor&#x27;s mental model at all, but with that of the existing user.<p>[1] See, e.g., <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=0V8k6qMpv7E">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=0V8k6qMpv7E</a> and <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Steenbeck" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Steenbeck</a><p>[2] first video here, <a href="https:&#x2F;&#x2F;www.adapttvhistory.org.uk&#x2F;post-production&#x2F;post-production-avid-editing&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.adapttvhistory.org.uk&#x2F;post-production&#x2F;post-produ...</a>
fellowniusmonk将近 2 年前
I&#x27;m working on this a lot right now, I have long tinkered on my personal productivity and data interface and I&#x27;m trying to make it accessible to others. It basically puts an end to context switching and deletes that cost from 80%+ of my workflows. It&#x27;s a &quot;no&quot; first interface so it really removes clutter and cognitive overhead.<p>I think with NLP and with AI guides we really need to change our unifying OS interface away from &quot;adhoc work tools catagorized by icons&quot; and go to interfaces categorized by intent or users data structure (that maps to their problem&#x2F;intent&#x2F;world as it grows and develops), so much lexical work has been done, so many concepts propogated via guis, that I think composable lexical interfaces should return with visual and nlp aids.
评论 #35987023 未加载
keyle将近 2 年前
Unrelated. I did the blog style, looks awesome on mobile.
评论 #35986211 未加载
评论 #35985651 未加载
makeitdouble将近 2 年前
The ideas are interesting, the illustrations are highly distracting.<p>&gt; If the software is at a certain level of complexity, new users will only learn parts of it or not use it at all.<p>Being talked about complexity next to a cockpit of a plane that mandates pre-training, with an exam leading to the acquisition of a license, followed by a mandatory minimum number of flight hours per month to keep the right to fly alone isn&#x27;t the best illustration I have of &quot;new users will only learn parts of it&quot;<p>And it goes on for every bullet point, there will be a plane cockpit next to it...<p>But yes, I totally agree that more thought needs to be given to the learning curve and discoverability of features of other non life critical, non regulated software.
thelogicguy将近 2 年前
I feel like you could strip down a UI, stick a language model on a help menu and you&#x27;d be most of the way there with this already.<p>I have a minor hesitation here. The user inputs an endpoint, and the program is then supposed to connect a user with the tool to complete it. Solutions often have different ways of being reached with tradeoffs associated with each method.<p>Also, I wouldn&#x27;t underestimate the ways in which, for some types of workers, the affordances of tools are part of the creative process. There&#x27;s a way in which a product will be less thought through when the journey from conception to completion is cut short.
评论 #35991194 未加载
yoshyosh将近 2 年前
Really good article! I like how it framed simplicity and complexity of apps, and how users want to stay in a certain zone.<p>I know the example was trite but future UIs will just allow the user to type or speak what they&#x27;re trying to do. For example coloring in the circle&#x2F;triangle will literally require you to say just that.<p>Whenever I see how people are cropping, masking, and adjusting an image, it already feels so outdated with what AI feels like it will be able to do based on text&#x2F;voice input.
wrftaylor将近 2 年前
The &quot;Zone of Proximal Development&quot; is a good concept for writing concise documentation too.
2dvisio将近 2 年前
Very interesting and it resonates with the things mentioned by Adobe ex-CPO to Lenny: <a href="https:&#x2F;&#x2F;youtu.be&#x2F;HCKosdV1J-8" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;HCKosdV1J-8</a>
nmeofthestate将近 2 年前
The &quot;can we help&quot; toast sliding down at a glacial pace when dismissed made me laugh out loud. But I just gave up at the Terms and Conditions scroll speed.
deterministic将近 2 年前
Game developers (usually) master this. Introducing a complex game step-by-step without overwhelming the player.
notjustanymike将近 2 年前
I liked the article all the way to the point where the author reinvented the help menu, but now with AI.
n0w将近 2 年前
I&#x27;m not convinced.<p>I don&#x27;t think products necessarily accrete features because the existing users need them to do more &quot;stuff&quot;.<p>Additional features tend to target new&#x2F;different subsets of users in an attempt to increase the size of the user base (and thus value to the creators).<p>So how do you choose the &quot;MVP&quot; features to expose to each subset of users?
sakesun将近 2 年前
What a cool web theme.
andreygrehov将近 2 年前
Great article, but it&#x27;s somewhat ironic that the article about UI has such a laggy JS&#x2F;CSS heavy UI. Why on earth does this require React? A basic HTML page with a minor CSS polishing would do the job.
brundolf将近 2 年前
Pretty neat website :) Very unique and polished
robertoandred将近 2 年前
User-Driven UI*
baq将近 2 年前
Kept looking for LLM references in the &#x27;what do you want to do&#x27; part and was surprised to not find any. Absolutely perfect place to put tool docs in the context and let users ask the LLM how to do what they want; bonus points for fine tuning the model on the docs and use scenarios.
评论 #35987222 未加载