34/100

Emerging evidence

Trace: a gain and a problemPublished recordBusinessThe Trace

I asked Lovable, Bolt, and Google AI Studio to build the same web app, and one is in a different league

Truvace record
TRV-2026-3014raw data (JSON)
Version
v1Published
First published
Evidence type
News report
Sources
1 sourceJournalism
sha256
003b678af65e…check it

All three got the math right, but only one understood the meaning behind the numbers If you have the vision of an application, and the words to describe it, there are many no-code AI services that can deliver it to you with just a prompt. Three of those apps that have gotten increasingly popular amongst vibe coders and developers ali

42Gain side

How the two sides scoreClose call

44Problem side

The gain

In one reviewer's single-prompt test, Lovable's benchmark app matched the other two on the 75 FPS and 57 FPS caps, then correctly traced the stutters to loading or shader compilation early in the run.

The problem

In the same hands-on test, Bolt labelled both Jedi Survivor runs choppy despite four of six slow frames falling in the first two seconds, and Google AI Studio's app advised stepping down to 0 FPS and 1 FPS.

A fixed formula sets both scores from the evidence and its sources. Reader votes don’t move them.

What the scores mean

G is the gain side, out of 100. It goes up when the gain is specific, when it measurably helped people and when the sources behind it are strong.

P is the problem side, out of 100. It goes up when the problem is specific, when it measurably hurt people and when the sources behind it are strong.

What this doesn’t fix

The comparison is a single informal test by one reviewer, using one prompt, one game (Star Wars Jedi Survivor) and two captures, with no fixes allowed.

Sources

1 on file
  1. XDA Developersxda-developers.com
    Journalism2026-11-17

Cite this record

v1

Truvace Impact Record TRV-2026-3014, v1: “I asked Lovable, Bolt, and Google AI Studio to build the same web app, and one is in a different league.” Truvace, 2026-11-18. /record/TRV-2026-3014 (accessed on the day you copy it). sha256 003b678af65ed872…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv1003b678af65e…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-3014 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.