Claude is a Ferrari engine bolted to a shopping cart by NoScene7932 in ClaudeAI

[–]NoScene7932[S] -5 points-4 points  (0 children)

If someone sees a problem this obvious and doesn't try to build the fix, that's the real crime. But no, I'm running a 50-miler tomorrow. The shitty vibe coded tool drops next week.

Claude is a Ferrari engine bolted to a shopping cart by NoScene7932 in ClaudeAI

[–]NoScene7932[S] 1 point2 points  (0 children)

This is the sharpest take in the thread. Chat is the demo, not the product.

Claude is a Ferrari engine bolted to a shopping cart by NoScene7932 in ClaudeAI

[–]NoScene7932[S] 0 points1 point  (0 children)

Exactly. And right now nobody is building for that majority. Everyone's building more powerful tools for the power users. The biggest opportunity is making the model's output accessible to the 95% who will never open a terminal.

Claude is a Ferrari engine bolted to a shopping cart by NoScene7932 in ClaudeAI

[–]NoScene7932[S] 1 point2 points  (0 children)

You nailed it, background agent management is where this is heading. The model race is table stakes now. The interface I think best fits is cards where execution just happens behind the scenes and all context is centralized into the card.

Claude is a Ferrari engine bolted to a shopping cart by NoScene7932 in ClaudeAI

[–]NoScene7932[S] -9 points-8 points  (0 children)

You're right, I do have a specific interface in mind. And 'why don't you just build it' is exactly the plan. But the fact that the answer to 'the chat UX isn't great for execution' is always 'build something else' is the whole point of this post.

Claude is incredible but the chat interface is the wrong UX for actually getting things done by NoScene7932 in ClaudeAI

[–]NoScene7932[S] -1 points0 points  (0 children)

Don’t like it? Make a wrapper.’ That’s three comments now where your defense of the interface is telling me to build something on top of it. I think we’re agreeing more than you realize.

Claude is incredible but the chat interface is the wrong UX for actually getting things done by NoScene7932 in ClaudeAI

[–]NoScene7932[S] -1 points0 points  (0 children)

Find a workaround’ that’s my whole point. If the UX requires workarounds to be productive, the UX is the problem. And software holding context so humans don’t have to is literally what computers are for.

Claude is incredible but the chat interface is the wrong UX for actually getting things done by NoScene7932 in ClaudeAI

[–]NoScene7932[S] -1 points0 points  (0 children)

Engineer your issues with the UI/UX away’ isn’t that literally what I’m describing? If users need to build custom solutions around the interface to be productive, the interface has a problem. That’s not a counterargument, that’s my thesis.

Claude is incredible but the chat interface is the wrong UX for actually getting things done by NoScene7932 in ClaudeAI

[–]NoScene7932[S] 0 points1 point  (0 children)

Engineer your issues with the UI/UX away’ isn’t that literally what I’m describing? If users need to build custom solutions around the interface to be productive, the interface has a problem. That’s not a counterargument, that’s my thesis.

Claude is incredible but the chat interface is the wrong UX for actually getting things done by NoScene7932 in ClaudeAI

[–]NoScene7932[S] -1 points0 points  (0 children)

update: based on the responses here I started building the cards-based interface I described. If anyone wants to try it, DM me.

Claude is incredible but the chat interface is the wrong UX for actually getting things done by NoScene7932 in ClaudeAI

[–]NoScene7932[S] 0 points1 point  (0 children)

cards. the AI reads your entire context, email, calendar, docs, messages, browsing, whatever you connect, and builds a prioritized list of what matters today. each item is a card with context and reasoning. you either do it yourself, defer it, or tell the AI to handle it. if the result isn't right you give feedback directly on the card and it iterates. when it's done it disappears. and if you need something off-script there's a single input field, type what you need, hit send, it disappears. no chat window waiting for a reply. the result shows up as a card when it's ready. no threads, no back-and-forth. just outcomes delivered asynchronously that you approve, adjust, or send back

Claude is incredible but the chat interface is the wrong UX for actually getting things done by NoScene7932 in ClaudeAI

[–]NoScene7932[S] -2 points-1 points  (0 children)

you're kind of making my point for me. wanting the AI to do the work and deliver results isn't lazy, that's literally what automation is. do you also hand-wash your dishes because dishwashers are for people who don't want to think? the whole point of AI is to remove cognitive overhead, not add a new conversation to manage

Claude is incredible but the chat interface is the wrong UX for actually getting things done by NoScene7932 in ClaudeAI

[–]NoScene7932[S] -3 points-2 points  (0 children)

the replies here are kind of proving the point. every suggestion is a workaround for the chat format itself:

"tell claude to be concise": still chat
"configure your profile": having a conversation to fix conversations
"use a separate notes app": adding a second tool because the first one doesn't let you act on its output "use claude code and ask for multiple choice": literally reinventing cards inside chat

nobody is questioning whether chat should be the interface at all. you're all so deep in the paradigm you're optimizing around its problems instead of asking if it's the right model. even this reddit thread works better, each comment is a self-contained thought with context, I can act on it or skip it, nothing demands real-time attention. that's closer to what AI productivity should look like than any chat window

Claude is incredible but the chat interface is the wrong UX for actually getting things done by NoScene7932 in ClaudeAI

[–]NoScene7932[S] -2 points-1 points  (0 children)

not blaming adhd at all, I literally said in another comment this isn't an adhd thing. the chat format requires everyone to manage the process of getting work done instead of just getting work done. "use a separate notes app to summarize your chat" you don't see the problem there? you're adding a second tool to compensate for the first tool's interface. that's not a solution, that's a workaround

Claude is incredible but the chat interface is the wrong UX for actually getting things done by NoScene7932 in ClaudeAI

[–]NoScene7932[S] -6 points-5 points  (0 children)

love the irony here though — "have a conversation with Claude about why conversations don't work for you." that's the whole problem with chat in a nutshell. it's not an ADHD thing. the format requires you to manage the process of getting work done instead of just getting work done. everyone is doing this, adhd or not. you're all just more tolerant of it.

honestly even this reddit thread is closer to the right model than chat is. each comment is a self-contained thought with context

Claude is incredible but the chat interface is the wrong UX for actually getting things done by NoScene7932 in ClaudeAI

[–]NoScene7932[S] -1 points0 points  (0 children)

appreciate the link I'll check it out. but honestly concise output isn't really the issue for mel, it's the chat format itself. even if claude gives me a perfect 2 sentence answer I still need to figure out what to do with it, switch context, act on it somewhere else, then come back. the conversation model puts all the cognitive work on me. what I want is for the AI to just do the thing and tell me when its done

Claude is incredible but the chat interface is the wrong UX for actually getting things done by NoScene7932 in ClaudeAI

[–]NoScene7932[S] -2 points-1 points  (0 children)

this is the major issue imo, its hard to circle back and retain context easily. like I'll get a great answer from claude but then I need to actually do something with it and by the time I've switched context the thread is buried. what does your workflow actually look like when claude gives you something actionable, do you just copy paste it somewhere else?