[markbao]

Everyone who has built software knows that the hardest parts involve making complex, tricky decisions with tradeoffs. Let’s say you make a grocery list app. Now you have to make decisions about all the different ways to specify quantity. Units, weight, dollars, bunches… oh, and fractional vs. decimal weight, etc…

The claim is that now every random person now will build their own app and have to make those hard decisions instead of paying $5 a month for someone else to do that work. Comparative advantage doesn’t just apply to the cost of writing code, but also the effort of making product decisions.

Edit: I don’t mean that a grocery app should cost $5/month, the grocery app was a toy example and the $5/month refers to an example of a separate app you’d pay for with much more value.

[rubb3rDucc]

This thread hits very close to home for me. I'm engineering the frontend for a grocery list app as a capstone project right now and I'm handling a lot of the product and feature decisions, and the discussion about "just prompt Claude to build it" versus the reality of those decisions is something my team deals with constantly.

The example of reverse-engineering your grocery store's API and building a custom solution is awesome, and it's exactly the kind of thing that's now possible. But what I've found is that even with AI assistance, there are so many interconnected decisions that make this more than a one-shot prompt project.

I pushed for us to build a mobile app specifically to take advantage of portability (use it at home for planning, at the store for shopping) and the camera (image recognition with OpenAI and scanning barcodes with expo-camera). That sounds simple, but it cascades into hundreds of UX decisions about offline-first architecture, gesture patterns, camera permissions, and more.

The units and quantities problem mentioned in this thread is just the tip of the iceberg. I'm trying to figure out a data model that mirrors how people naturally think about groceries: how they categorize items, how they plan meals versus staples versus impulse buys, how they track what's running low. Modeling those mental models is genuinely hard.

What helps is that I worked as an ecommerce shopper at Whole Foods, and I learned that stores are meticulously organized with numbered bays and predetermined routes optimized for efficiency. Translating that knowledge into a system that can intelligently sort a shopping list based on store layout (which varies by location!) and typical shopping patterns is genuinely complex.

One of my teammates put it well: this is a simple idea, but it requires a level of care, expertise, and experience to get it right. AI's incredibly helpful for implementing solutions once we've made these decisions, but the decisions themselves require domain knowledge, user research, and taste. That's the part that's hard to automate, and it's what makes this a real engineering project rather than a weekend Claude experiment.

[SoftTalker]

Some things are just not suited to an app. It's still easier to jot down a shopping list on a piece of paper than to use an app and a janky mobile phone keyboard. And bonus, nobody gets to sell your shopping preferences or blast you with ads as you're trying to use it!

[eddythompson80]

I spent years trying to find the PERFECT pantry tracking, auto shopping list generating, auto "what can I make tonight with what I have", auto meal preping app. The idea seemed so simple in mind back then. Let me input everything I have, then as I pull ingredients out of the fridge I just "decrease eggs by 3, decrease butter by 1tbsp, decrease bacon by 2 slices" then over time, it will just build my shopping list for me etc. I even built a requirement list and spent a year implementing my own thing.

Given the number of apps put there, from dozens of OSS hobbyist apps to industrial resturant inventory management ones, I wan't alone in thinking this is a solved problem and someone should just have the perfect interface for it. Between auto-unit converting apps, natural language processing apps, @cooklang, a million ideas about tracking pantries and ingredients and their categories, frequency of use charts, etc..

Then one time I went on a trip with a friend to his home town where we stayed at his parents house. His 78 year old mother had a 2 notepads attached to the fridge with a pencil on a string. As she worked in the kitchen, between washing hands she would just jot down random notes, cross others, doddles some on one notepad, and the other she would just add meal plans as she went along. Then when we were going to market she just ripped the page off.

Sounds so fucking simple and easy and I felt so stupid for the amount of effort I put trying to figure out the right app, the right device to mount on my fridge, how to connect power to it. How to make it not always on to blind me at night, but also so I don't have to keep fiddling with it to unlock it. how to use it with wet fingers, how to keep translating units and "catch up" when I miss updating it for a couple of meals, how to hide ingredients I don't care about and highlight ones I do, how to rearrange the interface. It seriously gave me a pause at how dumb I was that the solution is much much simpler and I pigeon holed my thinking on a tech solution for some reason.

Can't sell people notepads though. There is no margin or lock-in in that stuff.

[esafak]

That's just a contrived example. Every application involves a million subjective decisions; from the architecture, algorithms, to the UI/UX.

[noelsusman]

A grocery list app is the perfect example of the kind of thing that AI will make obsolete. Why would I pay $5/month for a list app when I can pay Claude $0.30 one time to make it for me?

I in fact did just that. I used Claude to reverse engineer my grocery store's API and build a grocery list app that automatically pulls in the aisle information for each item and sorts it by how I typically walk through the store. It's the kind of thing that would be incredibly difficult to scale but works just fine when you only have one user. No SaaS grocery app can hope to compete with me being able to tailor my own shopping list app to my exact preferences.

[pan69]

> reverse engineer my grocery store's API

Your grocery store has a free API you can use? Even if that is the case, that will then soon change. If app building becomes "free" then the cost will shift over to the data access.

[notahacker]

Who pays $5 per month for grocery store apps anyway? The usual revenue model is the app is free and you pay for the groceries...

[bavarianbob]

I think an engineer might, but my mother and wife will certainly pick the $5/mo option every time.

[markbao]

That is exactly the type of awesome app that can now be built. I edited my comment to clarify that the grocery app and $5/month app are separate examples, but I think your example shows that someone with coding knowledge can build something extremely useful for n=1 users which I fully support.

I just don’t think most people will end up doing that just like how most people don’t 3D print their own desk drawer organizers even when Gridfinity does all the work for you. Automation doesn’t fully replace the volition to build a thing and make tricky decisions that are familiar to us software engineers but not others.

[fatfox]

Exactly. I think only software developers believe AI is going to kill app subscriptions, because they're the ones who can actually wrangle the output into something maintainable.

For anyone without dev or product experience, getting beyond a basic feature set and keeping it running reliably (or roll it out to > 1 user) is still a massive challenge.

[xnx]

Or is the claim that someone will write the app and sell it for $5 one time or give it away free?

[markbao]

Yes, that’s a possibility! And for app types that have a limited ceiling of how much value they can provide, that will definitely be a thing as an AI app can saturate all of that value.

But for apps that have a lot of ceiling, people will still gravitate to apps that have had more care and attention than someone vibe coding it once and throwing it on the store, just like how people choose those well-built and maintained apps today over using their built-in Reminders app.