You’re missing my point. An Arcanoid clone worked because you didn’t need to describe it in incredible detail, since the product already exists. If you need proof of what I mean, you and I are talking about a project purely by name, and we both know exactly what it is, despite neither of us actually sharing any details.
1 Like
From a business perspective, I’d be worried if 75% of my app was other people’s code. Hard to be competitive with that.
4 Likes
The use of AI for coding really comes down to what you are doing. I needed a one-off bar chart for a RowSet yesterday and Grok 3 spit out perfect Xojo API2 code that did exactly what I needed. Actually, it was a pretty complicated problem as I needed to sum up cycle counts by day and create a chart with multiple bars representing various machines showing productivity by day. It took about 2 minutes total to create the entire app. I didnt even compile it. I just ran in the debugger and made a screenshot of the chart. It would have taken maybe an hour to create it by hand.
Ask me if I recommend AI and I would say “yes, you are crazy not to use it”. That is because my perspective is using it to do mundane one-off stuff that I don’t have time to do.
Ask a professional coder that is working on a control system for a nuclear reactor and he will say “No, you would have to be insane to use AI!”
3 Likes
I can’t really object to that. There are use cases. I personally have not found one, and my attempts to utilize an AI have bet met only with failure.
2 Likes
A prompt window inside Xojo will be the best solution. AI is making incredible progress.
Check Lovable for example using Supabase as a backend with automatic generation of tables and relationships. I think Xojo developers will be happy to have an AI assistant inside Xojo to review the code, optimize it. Lovable is focusing on high quality user interfaces powered by Apple Human Guidelines.
I wouldn’t use them as an example of responsible AI use. They genuinely exposed the Supabase API key in every single request, had to put their app in maintenance mode, then still exposed it because their maintenance mode just layered a DIV over the page that could be hidden. This all happened the day before yesterday, and spread across cybersecurity and AI communities like wildfire.
7 Likes
They just nailed the user experience part. By hiring more engineers, they should be able to fix this kind of issue very fast. Security is actually a very common issue with most startups.
Such famous last words… 
6 Likes