Comment by CSMastermind
7 hours ago
I'm increasingly convinced that there's a killer app waiting for whoever can come up with a UI that makes claude code or codex accessible to the average user.
Onboarding my non-software engineer teammates to it has super-charged them and essentially given them all their own personal developer that can automate tasks for them. Managing codebases, etc. is still a hassle though.
90% of the power of Excel was that it was functionally a database that a normal person could actually use. I think we'll see something similar with coding agents.
> that makes claude code or codex accessible to the average user
That's what they aim Claude Cowork at. Every executive/leader I've shown Claude Cowork to has gone from 'what is AI' to 'vibecoding whole apps' in weeks. Then when Claude is down for an hour, they get visibly angry and don't remember how to do anything pre-Claude :)
I understand the impulse to provide a UI to manage codebases, etc. But my observation is that these people just ask Claude to do whatever it is they need done. Codebase needs managing? They just ask Claude to do it. No idea how to deploy an app? They just ask Claude to do it.
Any app built on top of this stack to 'make it easier' is competing with 'I don't care what's happening, just ask Claude to do it'.
I have seen people just generate large docs with Claude cowork and they themselves have not scrutinized it or know why/how it's useful. It's just kind of impressive in its volume and well formatedness. And then they dump it in your lap as being helpful
> Then when Claude is down for an hour, they get visibly angry and don't remember how to do anything pre-Claude :)
The drug is scary when everyone is depending on it. I wonder what is future like.
The future is perpetually dealing with the fallout from all the vibe coding as the pool of people who'd have a shot at fixing it gets smaller and smaller. Shitty will be the new normal.
12 replies →
Same as anything else. It’ll go down sometimes, people will take a break and chat, then it will come back up.
Like Slack or GitHub or AWS or whatever. It’s almost always a net positive to wait vs do it yourself.
8 replies →
I think there are some pretty good ways to understand it now.
When the electricity goes out, (most) people get similarly upset. No electricity means no internet, and all of a sudden everything that people had planed to do can’t be done until the power returns.
> The drug is scary when everyone is depending on it. I wonder what is future like.
I can't wait for a Hollywood blockbuster that'll pretty much be science non-fiction.
> wonder what is future like
Probably "don't do anything to upset AI companies or you will effectively become a handicapped person"
Not that different from life in China: "don't do anything to upset Tencent and AliPay or you will become an outcast"
Or life in the US if you're a content creator: "don't do anything to upset Meta or Youtube or you will not be able to pay your rent"
The future: ToS basically becomes law, and you will be stripped of your own second brain if you violate it or say anything they deem "sensitive"
Full of security holes
same was said about electricity.
Seems far less scary to me than, say, building an electrical grid in a cold climate, where if it fails for a few days people start to die. Oh wait...
4 replies →
Imagine what happens if computers stop working* and you have to go back to pen and paper for a few days.
* ransomware attack, fire in the server room, database HDD crash, car accident takes out the internet connection, ...
> I understand the impulse to provide a UI to manage codebases, etc. […] 'I don't care what's happening, just ask Claude to do it'.
Reading the first part, I was going to say they don’t even care about whether or not there’s a codebase. It doesn’t matter; it could be all gremlins and hamsters in wheels for all they care, and for all they should care. All that matters is the functionality, the value it gives them.
We’re even getting disposable code now. Entire single-use ephemeral web apps, built on the go to enable, visualise, or simplify a specific thing, then thrown away.
Will it all lead to some trouble? Definitely. So did computers, and so did the internet.
Weird times. Fun times.
When I quit my day job and started Rails freelancing a big chunk of my work was from companies with "that tech guy" who had built a database in Microsoft Access that was vital to the department's operations. And then either left the company - or the app had started to fall apart under its own weight.
I would get called in to rewrite it, using a proper database, documented rules and ensure it stayed scalable - and everyone would be happy.
These Access "apps" were abominations from a technical point of view - but they got the job done without having to spend a load of money on off-the-shelf or bespoke software. And the "tech guy" made a valuable contribution to the company. It's only at a certain point that Access started to struggle.
I foresee the exact same thing happening in the near future - except we won't be building the replacement apps ourselves - we'll just know how to give the coding agents well-specified prompts and tell them when they're making a mistake.
5 replies →
>Every executive/leader I've shown Claude Cowork to has gone from 'what is AI' to 'vibecoding whole apps' in weeks.
Do you, and those executives, own the risks associated with that practice? Are those risks actually indemnified?
Its neat that 'anyone can do anything' but if they don't actually know what the risk to business or 3rd parties, why is this a good thing, especially in the enterprise where there are actors who are explicitly looking for this type of environment to exploit?
These are largely friends and peers, so they ultimately own their own risks. But I'm not saying it is good or bad. I'm just telling you what is happening in the real world. Every senior person I know, whether a high tech exec or a solo coffee bean importer, is vibing to some degree. Some will be more successful than others.
I've been working in tech since the late 90s. This is the biggest and most sudden change in company behavior I've ever seen. The only thing that comes close was the web 1.0 world in the 90s where everything suddenly became websites.
That creates tons of risks and opportunities. Good and bad. Maybe a great time to start a security company. But maybe a terrible time to be a small time web app developer when your clients can get 'good enough' in minutes for dollars on their own.
18 replies →
What kind of risk do you see?
3 replies →
What risks? You don't even known what they are building and you start the FUD train.
I found the Microsoft guy!
5 replies →
Haha I can't even trust developers who know the dangers of what they're doing to vibe code responsibly
> Any app built on top of this stack to 'make it easier' is competing with 'I don't care what's happening, just ask Claude to do it'.
To put it another way, the customers of these frontier models are implicitly being competed against by the model itself.
Yeah I'm realizing now how many of you guys work in industries with no data security/protection requirements
Exactly. The tools aren't the rate limiting factor for me. I can automate an entire department right now with Claude but I can't because of regulations and audits. Basically, turning an error prone manual process into a probabilistic process that Claude would do far more accurately in the end than what we do now. The process wouldn't be "repeatable" though by the letter of the regulation so would open the company up to automated regulatory violations and existential fines. The technical issues for me are trivial but the regulations are insurmountable. The bubble is in the TAM. My work is exactly who Claude for Small Business would be aiming at but we can't do anything with these tools because of regulation. That is a huge % of the economy.
1 reply →
There are requirements they just don’t get enforced enough to matter
>90% of the power of Excel was that it was functionally a database that a normal person could actually use.
I really thought Airtable would take off because it was even more of a "database that a normal person could actually use".
> killer app waiting for whoever can come up with a UI that makes claude code or codex accessible to the average user
That would be a capable 'personal assistant', or 'executive assistant', of 'chief of staff'.
Why? because the point is, just like in real life, to abstract away the complexity, irrespective of domain.
"Average user" implies someone not skilled or savvy in the domain you're thinking of. For a medical doctor, the 'average user' is not-a-doctor. For a technologist, the average user is not-a-technologist. For an insurance specialist, an average user is not-an-insurance-specialist. Etc. etc.
The personal assistant, exec assistant or chief of staff are themselves not necessarily experts in any domain, but they do rely on specialists to get stuff done.
So the UI for this killer app is basically voice input, keyboard input, camera input (mirros of human output) in the user's language with natural language interaction, and the output is voice and monitor/screen, and possibly a robotic arm/hand/body (mirrors of human input). Anything more complex than that would require tailoring it to a domain/domains.
If you doubt this analysis, think of all those folks for whom the IE/Chrome icon was/is "The Internet". Sure, you can go one level deeper with having them put in URLs, or operate email through the aol/gmail bookmark or desktop icon, maybe open documents/files from 'My Documents', but are they going to go any deeper than that, for the 'average user'?
We're building something along these lines, but since our roots are a consulting business, we're still building around the idea that there needs to be an expert integrator doing the front-loading work of discovery/decomposition/scoring of tasks/implementing them as those agents. These tools are terrifying to anyone not quite technical, and it turns out, people are bad at decomposing their own work, let alone describing it in a box with a blinking cursor.
We're obviously going to be holding ourselves back in terms of scale and in terms of not being a "true" SaaS with this approach, but my thesis is that we get much higher quality results and higher compliance/activation and can charge more for the bespoke model backed by our own platform.
> I'm increasingly convinced that there's a killer app waiting for whoever can come up with a UI that makes claude code or codex accessible to the average user.
I haven't tried it, or know a lot about it, but isn't this the whole claw thing?
Depending on what an average user looks like in your mind. For me openclaw is the opposite of a tool designed for an average user.
ChatGPT/Claude's web ui is much more like something for average user, tbh.
I don't think it needs to specifically be a coding agent for the average user, creating apps for whatever they want to do, just something that can use code and has appropriate access for what they're already asking it to do (instead of the model bullshitting to them that it can do it, annoying them), and some way to make it repeatable when needed, like skills.
I'm currently doing something like this in the internal model-independent LLM chat app I work on at a F100, specifically targeted at our everyday users. <input type="file" webkitdirectory> lets the user give the model read and write access to a local folder (and OPFS lets us reuse the same fs tools we give the model for files manually attached to the chat, or for files tools want to create if they haven't granted folder access).
Every time we used to release a new version it was "still can't handle the 6MB Excel file I drop into it" when that was being extracted to CSV and added to context - now it can poke about in the big Excel file directly with SheetJS to pull the sheets/headers and inspect the shape of the data, and use locally sandboxed code execution to write code against either extracted data or the spreadsheet itself via SheetJS for pivot tables and such (all locally - none of which need go into the context).
The base models are good enough at tool calling (I really mean Claude, though, the GPTs just go on a tear calling tools with no context for the user) they're already decent at automating stuff for the user without a dedicated harness (our default system prompt is still "You are a helpful AI assistant", lol). Add tools for Graph API stuff, and now it can pull the nightly batch file from a support inbox, unzip the spreadsheet within, diff it against yesterday's and generate an import file for new users and draft an email to welcome them, something that used to be a daily support task (which I'd already automated most of - but now you don't need a dev for this kind of thing). Or go find the big 450,000+ row spreadsheet that's being automated somewhere on SharePoint, pull it down in 150,000 row chunks (Graph Excel REST API limit) and write code to go figure out whatever the user is asking.
Having implemented and used it, I like this setup so much it kinda ruined Claude.ai and ChatGPT.com for me, so I've hooked up similar access for them using a browser extension to add the folder picker input, with the extension talking to a local server to tell it which folder to give access to, and Claude/ChatGPT talking to the same server over MCP via a CloudFlare Tunnel to work with the selected folder.
> Onboarding my non-software engineer teammates to it has super-charged them and essentially given them all their own personal developer that can automate tasks for them.
This is probably fine as long as the code is acting on local resources. The moment you have vibe coded software interacting with shared state or database the risk increases exponentially and all it takes to have a bad day is a poorly worded prompt from one of those users.
Some oversight by humans or automated guardrails will probably reduce those instances.
> Claude, fix the bug. Make no mistakes.
/s
You forgot to add "you are an expert software engineer with PhD level architecture insights".
2 replies →
True story, heard yesterday from a consultant who was working with some VP type (not a large company, but still high management): VP uploads a spreadsheet to Claude and tells it to remove column F.
The power of Excel is not what it was. Nor is the power of ordinary thought.
I'm trying to do this with orcabot.com
A figma like dashboard for turning ClaudeCode, Gemini Cli, Codex into an OpenClaw but with security measures to break the lethal trifecta while running on a VM.
But it's not quite there in terms of usability. I agree that is the hardest part of the equation. It's something I'm constantly experimenting with and haven't found the solution to it yet. Open to feedback!
Non-engineer average user here: this is what cursor is for!
The average person isn't going to be using a shitty vscode fork.
I am building a product in that space :)
It's targeted for creatives atm. For the few in private testing, it's been amazing what they're able to do with the little tooling I've given them. It is a legitimate change in their daily drive.
>I am building a product in that space :)
I don't know anyone not building a product in that space
I think everyone is making bespoke versions of what they think people want. It all feels gimmicky and dev oriented.
I have a vision for what will be the next household ChatGPT:
1. An actually frictionless way of keeping the human in the loop. My product is primarily targeting that: Your tools should feel like an extension of you, not replacing you.
2. Juggling work. I feel like what I'm making here is the secret sauce, so keeping a hush on it :)
3. Keeping all your work in one place. Drawing, sketching, developing, emailing, planning, writing; there is no reason to depend on other apps if you have one place that does it all, and it's the best offering among them.
Edit with some follow up thoughts -- I think what I'm trying to make is best summarized as claude code for non-developers (that's what I put in my YC application), but I think what I'm trying to make doesn't quite even have a developer equivalent.
There's not an environment you can go into right now and say "after this builds every single time, deploy to this machine" and it actually seamlessly does that. The tech is there but making it a whole Factorio-esque operation is still very manual -- and that's what I'm solving.
4 replies →
So, what are you building in that space?
Microsoft is trying this with copilot, but they are calling everything copilot so YMMV.
> a UI that makes claude code accessible
Isn’t that literally Claude’s web UI?
while there are some tools available for the web UI, like building small React apps or making diagrams, it doesn't have the same loop as Claude Code in terms of iteratively building or fixing
I wouldn't want to build a business that was so dependent on a massive third-party that can either cut off my access or copy my design at any time of their choosing.
I was thinking about this and there are several aspects that can still make this viable. 1) AI labs are incentivised to increase token consumption because literally that's their product. The only thing they sell AFIAK are tokens (and maybe a teensy bit of user data). So if you build a product that is actively reducing token consumption (which they simply cannot do without hurting themselves even if their marketing fluff says otherwise) you'll save large amounts of money for your customers and they'll choose you. 2) Big providers want to funnel every prompt into their servers. If you're in a regulated market or simply don't want to share every detail with an American or Chinese megacorp you are in trouble. BUT open weight models are now quite capable for "small business stuff" and they can be self hosted. If you can bundle this into your service, in other words actually care about their privacy, they will choose you. Even more so if you're in Europe.
> whoever can come up with a UI that makes claude code or codex accessible to the average user
You mean UX? Isn't Claude Cowork supposed to be 'Claude but for normies'? As for Claude Code / OpenAI Codex for non-programmers, believe Replit, Loveable, & others are trying & succeeding.
WhatsApp comes to mind in how its sole focus on replacing SMS (rather than Skype/AOL/MSN Messenger/YChat/GChat) meant it had no (user-facing) password/username, no elaborate signup, no login, no chat/friend requests, no sync etc. & became the biggest social network right under the nose of well resourced competitors with worldwide distribution, like Google & Facebook.
Business wise, neither Google nor Facebook were impacted IMHO. Google sells the tools that WhatsApp need to run and Facebook bought WhatsApp and kept its FB users in house.
Probably phone operators were not impacted too: SMSes bundled with flat plans are still flat plans and Europe style unlimited calls + 100 SMS per month plans are still there and those SMSes are still mostly unused.
So we could have a killer app and yet nothing changes in the flow of money around it.
UX wise, WhatsApp is a big improvement over SMS. Vocal messages, I'm not a fan of them. A waste of my time.
Google was impacted: their chat product is pretty much dead.
Mobile network operators lost the profits (at prices that were pretty much pure margin) they had on pay as you go messages, and messages not included in flat plans (e.g. overseas SMS's). They also lost a huge amount on highly profitable overseas calls. Those of us with family in other countries save a lot of money by using Whatsapp and similar instead of phone calls.
1 reply →
> 90% of the power of Excel was that it was functionally a database that a normal person could actually use. I think we'll see something similar with coding agents.
If you look closely, people we already creating databases and doing computation. But on paper. Spreadsheet software move the medium to the digital and with that brings a lot of convenience. Same with email, instant chat, and shopping on the web. The killer app is not about bringing something new, but making an old problem easy to solve.
The issue with LLMs is that it makes errors. Uncontrollably. And even if you can spot the obvious ones, there’s always some you won’t be able to catch unless you’re a subject expert. I’ve never seen a random people willing to monitor a piece of tech.
I really believe that the Spreadsheets UX is great for mainstream users and that is what drives me for my coding agent that uses the sheets UX: https://github.com/brainless/nocodo
Super early stage but I am really happy to read your comment.
Lovable?
Whoever does it everyone else will just prompt the same UX.
Yes, totally agree. Spent a few years in operations consulting and our clients' people were doing such amounts of mind-numbing repetitive work you wouldn't believe. Funny thing is, they are so used to it, they don't realize how wasteful it is. Yet, they are "afraid" of AI and new technologies in general, because it is something new and unfamiliar. However, when you show them something simple, e.g. how to write an Excel formula, they feel extremely motivated and empowered. So yes, if anyone can make AI feel less "scary" and approachable so that ordinary non-tech-savvy people can click around and see how they can automate some basic stuff, it will make them feel they have superpowers.
[dead]
I was just thinking about that earlier this week.
Claude can write code pretty well, but there are just a few tasks that I need to do to orchestrate everything. If it could do those tasks well even some of the time it would be about 10x more useful.
I agree and that's what i'm working on (for businesses) - an all-one-one consolidated AI application that's setup and ready for non-technical users.
It's called Zenning AI - we're a small team in London, testing it with a few companies at the moment!
We’re (harriethq.com) trying to do this by reframing it as a “provisioning” challenge - how do you get your connectors installed on non-technical desktops, how do you give some easy pre-bake recipes that wake them from their dogmatic slumber
Honestly though we are finding that a little FDE to set up pre-bake stuff that’s sufficiently specific to the customer is needed. Otherwise people are like, “I don’t need to close the books, I need to do a per-working-day profitability analysis for 10 EU countries with different public holidays”, and they get stuck there.