--- title: Software for One | daily.dev description: A developer shares their experience building hyper-personalized apps for their own household using AI coding tools — a sleep scheduler, a fitness tracker that... canonical: https://daily.dev/posts/software-for-one-sswr63wxl twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Software for One | daily.dev og:description: A developer shares their experience building hyper-personalized apps for their own household using AI coding tools — a sleep scheduler, a fitness tracker that... og:url: https://daily.dev/posts/software-for-one-sswr63wxl og:image: https://api.daily.dev/og/posts/Sswr63WXl.png og:image:alt: Software for One og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Software for One **[Hacker News](https://daily.dev/sources/hn)** · 7 min read · 0 upvotes · 0 comments ## Summary A developer shares their experience building hyper-personalized apps for their own household using AI coding tools — a sleep scheduler, a fitness tracker that adjusts smoothie portions to morning run distance, a jazz chord quiz, and more. The stack is Next.js on Vercel, Postgres on Neon with Drizzle ORM, and Claude Code as the primary AI coding assistant. Key takeaways: build cost has dropped dramatically, maintenance is easier than expected, the pattern of aggregating data from multiple sources and feeding it to an LLM unlocks insights no single app can provide, and ephemeral apps are perfectly fine. The author argues that as tools improve, personal software will become accessible to non-developers, and once people experience apps that truly know their context, generic apps will feel broken. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community take How the wider developer community reacted, aggregated from 1 discussion and 134 comments across hackernews (as of 2026-08-04). **TL;DR:** Commenters are broadly enthusiastic about AI-assisted personal software ('software for one'), sharing their own examples and validating the core thesis, though several push back on specific claims in the article (sleep consultants, calorie tracking accuracy, platform lock-in) and a few are skeptical about long-term reliability and quality of vibe-coded apps. **Sentiment:** 55% positive · 30% mixed · 15% skeptical **The case for** - Many commenters share their own successful personal apps built with AI assistance, confirming the trend is real and productive. - AI coding tools dramatically lower the barrier for non-developers and lapsed developers to finally ship ideas they've had for years. - Personal-use apps have a much lower quality bar than commercial software, making LLM-generated code 'good enough' for the use case. - PWAs and VPS hosting offer cheap, accessible alternatives to locked-down app stores for personal software distribution. **The pushback** - AI agents still require significant iteration (10–20 prompts) to get features right, and adding new features can silently break existing ones. - Platform lock-in (Apple's $99/year fee, code-signing friction, Google's APK restrictions) is a real obstacle to running personal apps on mobile. - Calorie tracking from brief meal descriptions is questioned for accuracy, and wearable calorie-burn estimates are unreliable. - Some examples in the article (sleep consultant PDF, smoothie-sizing fitness app) strike commenters as over-engineered solutions to trivial problems. - One commenter suspects the article itself was written by Claude, adding to concerns about AI-generated content flooding the web. **By community** - hackernews (positive): Commenters are largely enthusiastic and share their own personal-software wins, with lively side debates about nutrition tracking accuracy, Apple/Android platform friction, and the limits of vibe-coded quality. **Hottest debate:** Whether AI-assisted vibe coding produces reliably correct and maintainable software or just superficially working apps that break under real use. **Open questions** - How will 'software for one' apps be maintained or transferred when the creator is no longer around? - What is the right higher-level abstraction or language to reduce the remaining boilerplate in personal app development? - Will Apple and Google loosen platform restrictions as personal AI-coded apps become more common? **Highlights** > Things I've built in the last month or so: * A personal music player for Apple Music with an embedded agent loop, so I can say things like "I'm going to work in the wood shop, play woodworking-appropriate music and keep the playlist full and non-repeating indefinitely". * A calorie/protein tracker that takes 1-liner summaries of meals, resolves them to macros with GPT5 calls, and tracks them in SQLite. * A macOS menubar combined Apple TV and Roku TV remote control. * A calculator front-end to SageMath that renders Latex math notation and has point/click shortcut affordances for linear algebra and MVC. * A "self driving wiki" macOS desktop llmwiki that imports and digests PDFs. * A menubar tracker for the little temperature sensors I have scattered all throughout the house so I can click my menubar and instantly see the temps in the different rooms of the house. * A layout tool for designing picture frames to get cut lists and rabbet depths and stuff. That's just the desktop stuff. These applications are generally better than what I'd get from the App Store. The calorie tracker is one of the better-designed apps on my dock. I feel like I'm not doing this enough yet, it hasn't fully sunk in, and I'm going to be building a lot more stuff when it does sink in. I haven't yet gotten to the point of writing my own note-taking application (still Bear.app for that), but how long can that last? > — [tptacek on hackernews · 3 comments](https://news.ycombinator.com/item?id=49130811) > This is such a romantic idea, but unfortunately Apple and Google are hostile to this model. Of the two, iOS is /worst/ for running vibe coded apps. You need to pay $99 a year to be an Apple developer if you want your app to live on your phone for more than a a week. Distribution is a also pain in the ass even for personal use alone (you can't just toss around an IPA). Finally, so many useful APIs are totally locked up. The fact that I cannot in 2026 extend Siri, for example, us infuriating. Android is far more promising but Google recently shot themselves in the foot with their verified APK nonsense. Google's privacy posture is infamously nonexistent as well, and I have little interest in rooting a Pixel at my age. Hopefully now that enough people can vibe code, these walls will crumble a bit. > — [fny on hackernews · 11 comments](https://news.ycombinator.com/item?id=49130665) > > If you want fixes/features, you'll prompt your LLM and it'll make it so. I've been using the agents since the day they came out. This, does not work. It works if you want an app that looks like it works if that works without any testing. If you use the app in any way that isn't boiler plate it will break. Because you can't prompt ai with a simple feature no matter how small and have it cover all the important cases. What these models do is the absolute bear minimum to satisfy the user even if it means cheating. And anyone who doesn't look thinks its miraculous. It really is not. So, you absolutely can prompt it to add a feature, but you need to prompt it 10-20 times to get the actual feature built. If you don't know this yet rip. And before we continue, also known that when you prompt for the next feature. There is a high chance the last feature you built will be altered or deleted. > — [tim-projects on hackernews](https://news.ycombinator.com/item?id=49132761) > A typical (in fact, the modal) line from the database, which goes back to April, is "oyakadon 1/2c rice, 2 thighs, 1/2 breast, 2 eggs, bunch broccolini, std oyakadon broth", and the model works out for itself that these are average-sized thighs and breast (boneless and skinless, because it's oyakadon). "std oyakadon broth" is a reference to a "house recipe", of which there's a side database, each costed by GPT5. There's a low/med/high adjuster on every entry; sometimes the thighs are bigger or smaller, for instance. I've: * Checked these against all three major frontier models and gotten the same macros breakdown within relatively tight bands * Manually researched a couple of the most common recipes * Run this system over many months against my most likely TDEE and reconciled against scale weight loss (which has been profound). My confidence in frontier model's ability to generate "good enough, probably more than good enough" from this level of meal description is quite high. Key simplifying assumption (for the model): I'm cooking most of my meals. I cook. I virtually never order out or eat packaged food of any sort. This would be a harder problem and the answers less reliable if I was giving it, like, "1/2 JP Graziano muffaletta, extra hot giardiniera". > — [tptacek on hackernews · 1 comments](https://news.ycombinator.com/item?id=49131202) > The article is also obviously written by Claude too. I’m starting to hate the internet. > — [lloydatkinson on hackernews](https://news.ycombinator.com/item?id=49132623) **Source threads** - [hackernews](https://news.ycombinator.com/item?id=49096605) · 67 points · 134 comments ## Similar posts on daily.dev - [The age of personalized software](https://daily.dev/posts/the-age-of-personalized-software-yq58afqbk) · RUBYLAND · 0 upvotes · 0 comments - [Claude Code and the rise of personal software](https://daily.dev/posts/claude-code-and-the-rise-of-personal-software-cwlj5v66c) · The New Stack · 1 upvotes · 0 comments - [An experiment in vibe coding](https://daily.dev/posts/an-experiment-in-vibe-coding-4bhvzgnie) · Read the Tea Leaves · 33 upvotes · 1 comments --- Tags: [#llm](https://daily.dev/tags/llm), [#nextjs](https://daily.dev/tags/nextjs), [#claude-code](https://daily.dev/tags/claude-code), [#vibe-coding](https://daily.dev/tags/vibe-coding) [View this post on daily.dev](https://daily.dev/posts/software-for-one-sswr63wxl) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Software for One","url":"https://daily.dev/posts/software-for-one-sswr63wxl","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/software-for-one-sswr63wxl"},"datePublished":"2026-08-01T03:34:46.543Z","dateModified":"2026-08-04T03:51:44.122Z","description":"A developer shares their experience building hyper-personalized apps for their own household using AI coding tools — a sleep scheduler, a fitness tracker that...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a1625d87158c3628cf6e0743245a3a06?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a1625d87158c3628cf6e0743245a3a06?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Hacker News","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Hacker News","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/hn","url":"https://daily.dev/sources/hn"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/software-for-one-sswr63wxl","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"llm,nextjs,claude-code,vibe-coding","timeRequired":"PT7M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Hacker News","item":"https://daily.dev/sources/hn"},{"@type":"ListItem","position":3,"name":"Software for One"}]} ```