Hi all,
Over the past months, several discussions have emerged around Xojo and the use of AI in development, often focused on individual features or specific tools.
I’d like to share a broader thought starter, with the goal of encouraging a constructive discussion among developers rather than proposing a closed or definitive solution.
Xojo is appreciated by many for its RAD model: visual designer, event-driven programming, and rapid development of business applications. This is a real strength and not something that should be lost.
At the same time, the way many of us work with code is changing: external editors, automation tools, headless builds, and AI helping to read and modify complex projects. The question may not be whether Xojo should “chase” these tools, but how it can coexist with them without losing its identity.
With modern AI tools (ChatGPT, Gemini, Claude), I’ve put together a technical document that explores this direction, starting from a few general principles:
- keeping RAD and the visual designer at the centre
- avoiding imposed architectures or radical rewrites
- making projects more open and interoperable
- moving forward in phases, without disruptive changes
The document is intentionally aspirational but explicitly phased: it’s meant as a basis for discussion, not as a list of features to be implemented immediately.
For those interested in the technical details, I’ve attached the document to this post as a ZIP file.
I hope this can serve as a starting point for a community discussion:
- Which aspects do you consider most relevant for Xojo’s future?
- What feels realistic in the short term, and what does not?
- Which pain points do you experience most in your day-to-day work?
The idea is that value emerges from the discussion itself. Xojo has grown in the past thanks to this kind of exchange within the community.
Thanks to everyone who wants to share their thoughts.
Xojo_RAD_AI_RFC.md.zip (6.7 KB)