Kaufman Lab · AI architecture
Articles · Building with AI

AI app builders: what to build yourself and when you need a developer

You can build things yourself with AI where a mistake hurts no one: a simple business site, a landing page, a calculator. You need a developer when the program takes money, stores other people's phone numbers and emails, or lets users in with a password. A security hole there hurts other people, and in 2025 a code security vendor found a serious vulnerability in 45% of AI-generated code samples. First ask: who gets hurt if it breaks?

Roman Kaufman, founder of Kaufman Lab · Data as of: October 2026

Our site kaufmanlab.ru was built together with AI, and it has no lead form.

A "Phone" field and a button look simpler than any finished page. Will a form be the same kind of change as the ones before?

In vibe coding, AI writes the code and a person doesn't read it

Vibe coding means AI writes a program from a description in plain words. Developer Simon Willison, in a note on vibe coding from March 2025, uses the term for building a program without reviewing the code the AI wrote. A person describes the task and looks at the result.

We work in a similar way. AI writes the markup, the styles and the build code. A person sets the task, accepts the work and publishes it. How to set such a task is covered in the article on the AI agent prompt. As of October 8, 2026, 229 of the 280-plus changes to our site were made together with Claude (how we built our site with AI).

The danger is not complexity but other people's data

Willison approves of vibe coding for experiments and for projects where a mistake is cheap, but he advises thinking about the harm first. Could someone lose money or reputation if the code has a bug or a security hole? He sees this question as especially important for programs other people use. He advises care with keys, passwords and other people's personal data.

Security holes in AI-generated code are not rare. In July 2025, Veracode, a company that sells code security checks, tested code from more than 100 AI models. In 45% of the samples, it found a vulnerability from the list of the most dangerous ones. Models that were new as of July 2025 wrote code no safer than older ones, so even a fresh version does not replace a review.

Once, one extra tag in our markup broke the layout of six pages at once. Unpleasant, but it hit only us. A bug in a calculator that stores nothing about people also stays your own problem.

A form brings legal duties. Under Russia's personal data law (152-FZ), anyone who collects visitors' phone numbers and emails on a site becomes a data operator. Before collection starts, the operator must notify Roskomnadzor, Russia's data protection regulator (Article 22 of the law). The law allows only narrow cases without notice, for example processing on paper only, and a form on a site collects data by computer.

Data is exposed by a wrong access rule, not by complexity

A form with a phone field is not like the earlier changes. It adds a setting that decides who can read the stored phone numbers.

In 2025, Matt Palmer and his co-authors checked 1,645 apps from the showcase of Lovable, a service that builds apps from a description. In 170 of them, user data was open to everyone, and the authors looked only at the main pages (statement on the vulnerability found).

Emails, phone numbers, keys and payments were exposed because the access rules for database rows were missing or set up wrong. According to the authors, Lovable's security check back then saw whether a rule existed, but not whether it was correct. It has changed since then.

Our form would have needed storage for other people's phone numbers and an access rule for it. Which of this data you can show an AI is covered in the article on what company data to put into AI.

If one of five answers is "yes", a specialist reviews the code

You can decide whether to call a developer before the first line of code. Our site takes no money, no phone numbers and no passwords from visitors, and if it breaks, it hurts only us.

Here are three kinds of programs side by side, based on what we covered above, as of October 2026: who gets hurt by a security hole and who should build it.

What you buildWho gets hurt if it breaksWho builds it
Simple business site, landing page, calculatoronly youyou, with AI
Form with phone and emailvisitors whose data leaksa specialist, and you notify Roskomnadzor
Payments or password loginother people's money and accessa developer

The more a program deals with what belongs to other people, the earlier a specialist joins the work.

  1. Open a note and answer "yes" or "no". Does the program take money? Does it store phone numbers and emails? Does it let users in with a password? Will other people get hurt if it breaks or gets hacked? Does it contain keys and passwords for services? If all five answers are "no", build it yourself.
  2. If there is at least one "yes", a specialist reviews the code before publishing. Before that, run the app builder's built-in security check, if it has one, and fix the critical findings. The check does not replace a specialist: Lovable's security documentation, for example, says it does not guarantee full security.
  3. Collecting phone numbers or emails? Then notify Roskomnadzor before collection starts. The "Форма уведомления" (notification form) on pd.rkn.gov.ru is filed through Gosuslugi (Russia's government services portal), with an electronic signature, or on paper.

For a calculator, step 1 is enough. A form with a phone field needs all three. If an employee builds the app but you are the one responsible, turn on the app builder's setting that blocks publishing with critical findings, if it has one. By Willison's rule, code written by someone else that you can't explain to another person doesn't go into use. What else AI does on its own and what needs a person's review is covered in the article on what work to hand to AI employees.

Frequently asked questions

Can I build an app with AI for free?

You can build an app with AI without paying a developer, but it won't be completely free. As of October 8, 2026, the cost of our site was 0 rubles ($0). We paid only for the domain and the server. These 0 rubles don't include the author's time. For the cost of the AI itself, check your service's plan.

Which AI is best for building apps?

The best AI for an app depends on where you want to keep the project. In the browser, people build with Lovable, v0 or Bolt. On their own computer, they run the project with Claude Code or Codex.

Who is responsible if an AI-built app loses data?

The app's owner is responsible: that is what the security documentation from step 2 says. Under 152-FZ, the operator is also the one who organizes or carries out the processing and sets its purposes, that is, the owner of the form.

A question about this article?

Message me on Telegram: I answer myself, look at your task and tell you which of this fits it.

Message on Telegram→
More articles
↑ top