Which Apps Make Sense for Vibe Coding by Non-Engineers Today?

A framework for non-engineers to assess which applications are suitable for 'vibe coding', categorized by risk level from green to red light, based on 100+ hours of experience.

Original analysis and content by .

🧠 Core Concepts 🔗

Vibe Coding

A colloquial term for using AI-assisted or generative AI tools to create software applications, often by non-engineers, based on natural language prompts or 'vibes' rather than traditional, line-by-line coding.

Personally Identifiable Information (PII)

Any data that could potentially identify a specific individual. The post warns that vibe-coded landing pages may inadvertently collect and store PII, creating a security risk.

No-Code/Low-Code

Platforms that allow users to create applications through graphical user interfaces and configuration instead of traditional programming. Vibe coding is an evolution of this concept.

Spec-Driven Coding

A development approach where coding is guided by a formal specification. Mentioned by a commenter as a more mature and scalable sibling to the more intuitive 'vibe coding'.

🚦 The Vibe Coding Scale 🔗

Lemkin Scale of Vibe Coding

circa August 2025

non-engineers
can vibe here
non-engineers
should not vibe here

green light

  • Basic info web apps (no customer data) — like Squarespace on steroids.
  • Prototypes for validation (demos, concept proofs).
  • Internal apps (properly secured): dashboards, tracking tools, workflow automation, etc.

yellow light

  • Landing pages — great for marketing agility, but most collect PII. Vibe coding apps often store this data even if you don't realize it. Manageable risk with proper review.

orange light

  • Complex apps: possible but time consuming. Each feature creates exponential complexity in testing/maintenance.
  • Apps with confidential data/PII. Need expert security review.

red light

  • Rolling your own Salesforce. Yes, you can build a basic CRM. No, you cannot build enterprise software. Don't even try.

🛠️ Mentioned Technologies & Tools 🔗

Salesforce

An enterprise-level CRM platform. The author advises against trying to replicate it.

Squarespace

A website builder. 'Green Light' projects are compared to 'Squarespace on steroids'.

Kiro from AWS

An Integrated Development Environment (IDE) from Amazon Web Services (AWS) for spec-driven coding.

Figma

A collaborative interface design tool, suggested as an alternative for user feedback prototypes.

Bubble.io

A no-code platform suitable for low-complexity enterprise apps with security control.

Tailwind CSS

A utility-first Cascading Style Sheets (CSS) framework for rapidly building user interfaces (UIs).

Shadcn/ui

A collection of re-usable UI components for building prototypes quickly.

Next.js

A React framework for building full-stack web applications.

❓ Frequently Asked Questions 🔗

Basic informational web apps with no customer data, like content sites or company pages, are considered the safest (Green Light). They present little risk and are a great use case for the technology.

The primary drawback is fragility. As complexity increases, the application becomes exponentially harder to test and maintain. Each new feature can introduce unforeseen issues, making the system unstable.

Vibe coding is an evolution of no-code, leveraging generative AI and natural language prompts for a more fluid, conversational development experience. However, as commenter Scott Brinker noted, the types of applications suitable for each (e.g., internal tools, prototypes) have remained largely the same over the years. Vibe coding is more about the 'how' than the 'what'.

No. The author strongly advises against this, classifying it as a 'Red Light' activity. The underlying complexity, security, and scalability of enterprise software are far beyond the capabilities of current vibe coding tools.

👥 Contributors & Commenters 🔗