Vibe coding has escaped the terminal
Casey Newton ยท rss ยท 2026-07-08 source โ Reader ๐ฅ๏ธ
Vibe-coding tools have escaped the terminal and IDE into consumer-friendly, GUI-native app builders like Raycast's Glaze, making it cheap and fun enough for a non-technical user to build genuinely bespoke, hyper-personalized desktop software โ which gives Newton modest but real confidence that such software has a near-term future.
practical ยท narrative โ A first-person account of building three apps with Raycast's Glaze, structured as anecdote-plus-reflection rather than sustained argument. It edges toward the practical (implicitly urging readers to notice/try the shift) but never states a call to action; its real work is descriptive/illustrative, culminating in one modest, explicitly hedged generalization about the future of software.
Structure
| Part | Role |
|---|---|
| Opening: prior vibe-coding projects (personal website, briefing tools, Platformer archive) were useful but ugly, confined to the terminal or Markdown | context |
| Introduction of Glaze: an all-in-one Mac app-builder (vs. general-purpose coding tools), compared to Wabi (mobile equivalent), with pricing and access details | evidence/context |
| Case study 1 โ Nightwing: a comic-themed to-do app built purely for delight, with AI-generated images and animations | evidence |
| Case study 2 โ Platformer app: a semantic-search research/archive tool built in about a day, judged genuinely useful beyond what's commercially available | evidence |
| Case study 3 โ Source Code: a half-finished personal CRM combining phone and LinkedIn contacts, with open privacy/security and design doubts | counter-evidence/caveat |
| Closing generalization: 'the revenge' of software that finally bends to the user, and a hedged claim about a future for hyper-personalized software | conclusion |
| A separate 'Following' news roundup (China weighing restrictions on open AI models; Australia's under-16 social-media ban failing age verification) | unrelated appendix, excluded from analysis |
Key terms
- vibe coding Vibe Coding
Building working software โ now extended to full consumer desktop apps, not just code โ primarily by typing intent into a prompt box and watching an AI agent generate and live-update the result, evaluated on how satisfying and personal the outcome feels rather than on code quality. - hyper-personalized software
Software built bespoke for one person's specific, often idiosyncratic and previously uneconomical needs or tastes (e.g. a Nightwing-skinned to-do app), made viable because the marginal cost of building one-off apps has collapsed. - SaaS-pocalypse
Newton's own half-joking coinage for a hypothetical mass displacement of subscription software-as-a-service products by cheap, user-generated personal apps.
Propositions
- explicitGlaze is an all-in-one vibe-coding app purpose-built for creating and sharing Mac desktop apps, distinct from general-purpose coding tools like Claude Code.conf: high
- explicitGlaze offers concrete UX advantages over a pure coding tool for a non-technical user: a working app template to start from, automatic compiling/installing, native image-generation calls, and live in-app visual editing (including circling elements to target changes).conf: high
- explicitIn his first month with Glaze, Newton built three apps โ Nightwing (a comic-themed to-do app), a Platformer research/archive app, and Source Code (an unfinished contacts/CRM app) โ of which only the Platformer app has utility beyond what already exists in the App Store.conf: high
- implicitThe primary value Newton reports from these tools is delight and personal fit ('making my chores fun'), not objectively superior functionality.conf: high
- implicitdevelopedThe collapse in the marginal cost and skill required to build software is what makes previously not-worth-pursuing ideas (a joke to-do app, a personal CRM) newly viable to build at all.conf: highextends โThe case for making your own apps ยท p1 โ Mann's quantified 30-50%-of-your-Mac prediction extends Newton's own earlier observation (from his first month with Glaze) that collapsing build cost/skill makes previously not-worth-pursuing software newly viable โ turning a personal anecdote into a market-scale forecast.
- explicitNewton's overall verdict ('a future for hyper-personalized software, at least in the short term') is explicitly self-described as not extending far beyond 'it's fun to make things.'conf: high
- implicitNewton's assessment rests entirely on his own first-person, one-month experience as an early-access, well-resourced tech journalist with a personal connection to Anthropic, not on any broader usage data, retention figures, or a representative user.conf: high
Arguments
There is a real, if modest, near-term future for hyper-personalized software. strength: low
Explicit premises:
- Glaze materially lowers the effort and skill needed to build a working, polished desktop app (template, auto-compile/install, native image generation, live visual editing).
- Newton, a self-described non-technical person, built three functioning apps within about a month, one built in roughly a day.
- At least one of those apps (the Platformer research tool) delivers real utility not otherwise available.
Implicit premises:
- The ease and personal enjoyment of building software counts as meaningful evidence of durable value, not merely novelty.
- One well-resourced, early-access, AI-industry-adjacent user's experience is treated as indicative of where 'the next generation' of vibe-coding tools is headed, generalizing beyond that single case.
- The copyright/IP and safety-guardrail concerns Newton himself raises about generating a DC-owned character are acknowledged but not treated as undermining the overall favorable verdict.
Inferences:
- If bespoke personal software becomes trivially cheap to produce, this could erode demand for categories of general-purpose consumer SaaS (to-do apps, note apps, CRMs) โ the 'SaaS-pocalypse' Newton names but doesn't analyze in terms of business-model or App Store consequences.
- If any user can generate copyrighted characters via an LLM image model inside a consumer app, this raises IP-enforcement and platform-liability questions Newton raises rhetorically ('almost certainly' a copyright violation) but does not pursue.
Narratives
- The Nightwing to-do app: a comic-book-themed, purely-for-delight to-do list with AI-generated character images and animations.
โ Illustrates that near-zero-cost app-building lets a non-technical user pursue an idea with no functional justification, purely for personal enjoyment โ supporting the 'hyper-personalized software' thesis via a case that is fun but not useful. - The Platformer app: a semantic-search research assistant over the newsletter's archive, built in about a day, replacing a friction-heavy terminal/Claude-Code workflow.
โ Supplies the piece's strongest evidence of genuine (not just novelty) value, distinguishing Glaze-built software from a toy. - Source Code: a half-finished personal CRM merging phone and LinkedIn contacts, with the author still unresolved on privacy, security, and even whether he likes the design.
โ Functions as an honest counter-narrative/caveat โ shows unresolved limits (privacy, security, product-design uncertainty, willingness to pay) even for an enthusiastic early adopter, tempering the closing generalization.
Questions addressed
- โ
Has vibe-coding moved beyond terminal/IDE-bound tools into consumer app-building?
Yes, per Newton's direct experience with Glaze building three distinct Mac apps. - โญ Is there a durable future for hyper-personalized, one-off software?
Newton offers only a hedged, personal-anecdote-based 'yes, at least in the short term' โ he explicitly declines to extend the claim further. - โญ What are the legal/IP and platform-liability implications of an app-builder that generates copyrighted characters via AI image models?
Raised rhetorically ('does it represent a copyright violation... almost certainly') and then dropped without further analysis. - โญ What happens to the broader consumer-software/SaaS market โ and to Glaze's own app store โ if personalized one-off apps become common?
Named via the 'SaaS-pocalypse' quip but never seriously examined.
Gaps
- incompleteThe piece offers no data on how typical Newton's experience is โ he is an early-access, well-resourced tech journalist with a household connection to Anthropic, not a representative consumer; there is no discussion of skill floor, cost sensitivity, or failure/abandonment rate for a broader user base trying Glaze.
Read next: Look for adoption/retention data on vibe-coding app-builders (Glaze, Wabi) beyond first-month enthusiast anecdotes โ completion rates, subscription churn, or a more skeptical follow-up in the spirit of this corpus's 'AI Confidence Theater' theme, which treats vivid personal anecdote as a weak substitute for verifiable evidence. - incompleteNewton flags the copyright/IP question about AI-generated Nightwing artwork but doesn't pursue what it implies for Glaze's business model, Raycast's legal exposure, or likely rightsholder response.
Read next: Seek legal/industry analysis of IP liability for AI app-builders that call image-generation models, and how a marketplace like Glaze's store moderates for this. - incompleteNo examination of the security/privacy architecture behind an app like Source Code, which merges phone contacts with LinkedIn data into a 'private, locally stored' CRM; Newton himself says he is 'still thinking through issues related to privacy and security,' but the piece never examines what guarantees Glaze actually provides around local storage, API-key handling, or data-exfiltration risk.
Read next: Look for appsec-focused writing on the threat model of vibe-coded apps built by non-technical users that handle personal data (contacts, LinkedIn, API keys) โ directly relevant to the reader's application-security interest. - uninformedAs an outside-observer journalist rather than a practitioner, Newton doesn't engage with the mechanism underneath Glaze โ what agent/model architecture it runs, how the 'circle an element to edit it' feature is implemented, or whether the generated code's quality or security is auditable. The piece is long on implications and 'vibes,' short on any rigorous look at what's actually happening under the hood.
Read next: For the engineering-craft angle, look for a practitioner teardown of Glaze's (or Wabi's) underlying agent harness and tooling, analogous to a technical review of Claude Code internals. - illogicalThe 'SaaS-pocalypse' and 'revenge' framing treats one person's delight in personalizing his own software as evidence for a market-level claim (a genuine threat to existing SaaS and App Store businesses), without addressing switching costs, the long-term maintenance burden of AI-generated one-off code, or whether most consumers actually want to build rather than buy.
Read next: Look for a more rigorous build-vs-buy or market-structure analysis of personal software in the vibe-coding era, rather than a single enthusiast's month-one impression.