I'd like to share some of my thoughts on this matter.
I first approached computers through music and then Hypercard. But I started my first real programming with Livecode, several years ago (RunRev).
I discovered Livecode to be a formidable tool, which allowed me to achieve extraordinary results, despite my old age and almost complete ignorance of other programming languages. So much so that in recent years I created an innovative startup and published my software with satisfactory results.
I often encountered some of LC's limitations, not to mention the frustration of figuring out how to overcome them using Livecode Builder.
When the Livecode Create project was born, knowing a little about the no-code world, I immediately thought it was the wrong path.
I "understood" my code, having roughly in mind the names given to variables, commands, and functions, and the logic of the implementations. I needed help when things didn't work or if I needed specific features, not "something" that would write the code for me, making the logic, in my eyes, incomprehensible or at least difficult to reconstruct, as if it had been developed by another programmer.
With the 2027 deadline (EOL for Livecode Classic) and the slow start of LCC, I returned to the web to look for an alternative and discovered I didn't have one. Native languages are too complex for me, as I've been spoiled by LC, and the various no-code programs all suffer from the same flaw: the author often doesn't know what's going on under the hood and sooner or later has to rely on an expert programmer to fix bugs or implementations.
Meanwhile, thanks to a friend, I discovered Claude AI.
At first, it was with endless sessions (I think I contributed significantly to teaching Claude how LC works...

, but then, little by little, I learned how to manage it and get what I needed, while always maintaining control over how things worked.
So I created an extension to read NFC on iOS, another to communicate via Bluetooth LE on Android and iOS, I improved some JavaScript pages that were updated remotely, etc. All of this, mind you, without knowing Java, C+, JavaScript, or Java.
Once I learned how to communicate with Claude on the OSX terminal, he writes the frameworks for me, compiles the Java or C+, and explains what it's done. I just have to launch LCB and test.
Amazing!
This is the tool I wish I had: LC and good integration with an AI.
I've learned a lot using Claude, but especially that my logic is often better than his, and that, knowing the bigger picture of the app, I can always point out the right direction.
All this to say that, if I've figured out what LCC will become (when actually usable), LCC it's not for me and I probably stop programming in 2027.
Trevix