Xojo always had potential, I’ve said it before and I’ll continue to say it, a dedicated and hardworking individual can create products 90% on par with 1st party tools. However that workload is ridiculous and quite frankly unnecessary.
1Password for instance could have easily been built in Xojo, but there is a reason as to why they didn’t use Xojo. Electron, while ugly is better known and because of that, it’s has a larger audience and therefore is better supported.
The CEO of Xojo doesn’t understand why Xojo’s market has been steadily decreasing over the decades, his attempt to fix it, was to change the language, why would this encourage people to buy his product, I’ll never know, but he bet everything on it and lost.
That single decision illustrated, exactly why Xojo has repeatedly failed to grow and the ramifications caused tremendous shrinkage. The CEO doesn’t understand how to grow the Xojo market. Their latest attempt is on the right track, listening to feedback that we filed upto a decade ago, but at this point, I think it’s too little, too late.
I was recently (2022) presented the opportunity to review Xojo for Mac publications, but I passed, because I didn’t feel a could give a balanced review of the product. This led to Xojo NOT being reviewed and losing that marketing opportunity.
While this all sounds very sour, and I am very sour over the way Xojo has treated us, it’s becoming more and more of a bad memory. I’ve been sick recently and unable to work for a while, when I returned, Swift came naturally, but having to add a workaround to Sleep Aid (still done in Xojo for the time being) for a bug in Sonoma 14.4.1, was hard work…
Xojo is certainly NOT low code, and they should stop advertising that they are.
Addendum: I have accessed Apple of doing the same thing, and to a large extent, they are. However I must point out that Apple recently investigated a bug report of mine over SwiftUI and they found no bug, but they did take the time to provide me a worthy workaround and after looking at all of my submitted code, the engineer even took the time to provide some tips, all of which I am deeply appreciative of.