Journal
Journal: no-code
On this topic, 6 articles from the journal, from practical guides to behind the scenes of the product.
Bubble or Lovable: two ways to lock you in, and the question to ask
One interprets your application in an engine found only on its platform. The other lets you leave with code but refuses to take yours in. The locks are different, and the question separating them fits in one sentence.
Read the article
Firebase Studio is closing: what to replace it with, and what a closing tool owes you
Google closed Firebase Studio signups in June and will delete workspaces in March 2027. GitHub deprecated Spark in August. Two application-building workshops ended in one summer, with the same lesson for those building elsewhere.
Read the article
Why my no-code MVP never gets finished: day 9 and the remaining 20%
The screens exist, the demonstration works and the test payment succeeds. Then the project stops and nobody can say why. An account from a no-code MVP provider, what the final fifth contains, and why it costs dearly after a launch date has been announced.
Read the article
Building an application without knowing how to code in 2026: four routes
No-code, prompt generator, coding assistant, agent team: four ways to have software written without writing it yourself. They do not cost the same, and above all they do not leave the same things in your hands when you stop paying.
Read the article
No-code or AI: should you still learn Bubble in 2026?
No-code promised building without coding, at the cost of learning an editor. AI shifts the promise: nothing left to assemble yourself, requirements to direct, and standard code you own.
Read the article
Lovable, Bolt, v0 or Maestro: which AI tool should you choose for your application?
Compare project preparation, construction, publishing and code handover. A reading of documented capabilities to help you choose for your needs, including Maestro's limitations.
Read the article