close
Skip to main content
nxnze u/nxnze avatar

nxnze

u/nxnze

Feed options
Hot
New
Top
View
Card
Compact

> Do you believe wrappers can still be durable businesses?

Definitely not. Keep in mind the actual cost of using LLMs is currently heavily subsidised by VC money. They are fighting between themselves to win market dominance. We are paying a favourable rate until the dust settles. At some point the money will dry up. Is your app sustainable if the API costs increases?

>  If you’re building with LLMs, where do you think the real moat comes from? 

It really depends on what you're building. Are you chat wrapper with some additional system prompts? Most definitely you will be swallowed up eventually. Maybe not even by the LLMs themselves, but all you really need is a builder-type app. If your value on-top of an LLM is speciality prompts, you have no moat. Enjoy some returns now while it lasts. Nothing wrong with that either.

Does your app actually solve a real-world problem, and then uses LLMs is very specific features or ways to improve either efficiency or automate parts of it? I'd say that's the beginning of a moat. The data you have and collect from your problem solution lends itself to improved LLM efficiency and accuracy - which is where you can start building a moat. As long as that data is proprietary, then you have a bit of a leg up.

Obviously, LLMs will keep learning over time, but don't be certain they are going to get smarter. There's a phenomena called Model Collapse. The more LLMs become popular, the more it gets trained on it's own AI-generated output, leading to a degrading in quality. This reinforces the need and value of having your own data. It's already becoming really hard to navigate the internet, including reddit, without having to wade through tons of AI-slop. A lot of this is going to be fed back into the LLMs as training data.


minus points for using tailwind and shadcn


very smooth astroturfing. I can't stand it usually but I'm also a sucker for a component library


Happened oh so many times with my own app. I thought I had nailed it after about 8 months of development and released a version to my friends and family. The feedback was... painful to say the least. It took another 2 or 3 rounds of this before it finally clicked and I got an intuitive UI.

I have over 20 years of development under my belt, focused heavily on UI and UX in my career, and have worked for big companies like Salesforce. All this to say that it is just a very hard problem, no matter the experience level, so don't let this demotivate you.

I would recommend not focusing on adding the hand-holding just yet. You've started off right by getting someone to use the app while you watch them. Now you need to iterate on the design and logic of the UI. See where they got confused and how you can make that more evident now. You might even need re-think everything, but that's ok. It's the process.

An intuitive UI shouldn't need hand-holding, so you want to get to a stage where users can navigate the features without it. Once you're there, then you can add some onboarding / usage guide as a nicety.



What creeped you out exactly? There is potential for this to happen to any neo-bank option available. The most reliable will always be a brick and mortar bank, but their tech generally is very underwhelming and you won't get favourable exchange rates.


thankfully there's bookie.tax now


interestingly all intelligence related tasks. AGI anyone?