From Xojo’s Black Friday sales blog post:
And that’s how Xojo saves you time and money. In enterprise environments, Xojo is excellent for:
- Prototypes and proof-of-concepts
- Internal tools and utilities
- Testing
- Demos
No more talking of producing commercial software with Xojo.
At this point, I wouldn’t care if they did. It only hurts their community even more than they’ve done it themselves.
I suspect, there will either be an e-mail from the CEO tomorrow morning, or nothing from them.
I’m not asking them to do that, I was ask for functionality that would make the transition smoother, especially the stupid DesktopControls. And fixing some of the problems with their 25 year old Mac framework.
The Mrs told me today that I’m a lot less angry recently, she thinks it is because I’m no longer working in a tool that I believe no longer has a future (at least for me anyway).
The Receptive Tour Operator I worked for in Orlando serviced all those people! So that was a sweet deal for them… I worked as their dev and IT person… We used FileMaker back then.
Ironically, that’s one of the reasons peeps are done with Xojo. 
@JeffT , @HalGumbert. Please enlighten me ignorant who lives on the other side of the Atlantic what this is about. 
Hoover did a promo. Cost them dearly…
There are several silent folks posting on that about how disastrous Sam leaving App Wrapper would be
Sad but I expect there’s no outreach by Xojo to @samRowlands about this
There should be
BUT, I also dont think that will change anything either
If you ignore a problem long enough doesnt it just go away ?
Of course that “problem” may just move to another tool / language so in a way yes it does
Just it has knock on effect
The ‘Pro-Friendly’ beginners tool 
Worst part is since everyone here is labelled “a troll” there’s 0% chance that anyone at Xojo would reach out to the collective group here and ask “Ok so what COULD we do that might entice you again?”
I dont expect many would go back since they have moved elsewhere
However I do think that some advice from the group MIGHT help Xojo better understand WHY people left and how they might address those issues to stem the tide
But, as I said at the opening, theres a 0% chance they’d do this regardless of whether it would help them or not
The “trolls” are just the one who dare to speak up. The others think the same but will simply say Fuck it and leave without complaining.
And thinking that no complains means everything is ok “I know what everyone wants” is plain stupidity.
Another one bites the dust:
https://tracker.xojo.com/xojoinc/xojo/-/issues/74622
I haven’t gotten to my work 'puter yet, but I am expecting either an e-mail today asking to schedule a talk or none from them ever again.
Which seems to be exactly what they’ve done since API 2.0 was announced. Didn’t Geoff say he was surprised that it is still a problem and doesn’t understand why, but like all things it will pass.
In my recent weeks, I’ve discovered that it’s not even a good option for that.
Because IMHO, they don’t want to know. I believe the mentality there is they all know Xojo is in a bad shape for the future, so they’re simply doing what little they can to keep some money flowing in until the inevitable.
At this point, there has to be some really big problems with Swift and SwiftUI for me to consider using Xojo for my personal projects.
I believe I’ve made it clear my reasons for leaving. I’ll summarize it if they’d like me to do so, but I honestly don’t have any faith that the CEO is interested.
Absolutely. In fact the worst thing for a developer is zero response from a declining group of customers. I have been told by a couple of customers as to why they no longer need to renew App Wrapper and sadly it’s not something I can directly do anything about, I did try to change that, but found myself lumbered in the same group as them.
“You’re were supposed to help turn Xojo around, not join the leavers”
And this is a perfect example of why I just silently went away from Xojo and back to Delphi as my primary tool. I started way back in the DOS days with Turbo Pascal 3.0 and have kept using Delphi over the years. It is expensive for the initial purchase but the 1 year maintenance support (which gets you the new released version also) is only about $425 USD. Windows, MacOS, iOS, Android can all share a lot of code with one project being able to generate all of the executables.
I’m not trying to convince anyone else to switch to Delphi. It was the right choice for me to move on with for many of the same reasons many of y’all have looked at other tools.
I’d like to know about this. I’ve had several people write to me and ask about alternative to Xojo, I personally have gone with SwiftUI, but I’d like to be able to give people a list of x-plat tools. Does it use a Declarative UI (which appears to be the trend) or specific forms for each target?
Thinking about this post, it illustrates why Xojo isn’t growing. Instead of just letting the customer dangle, they should be really inquiring why hasn’t the customer updated in almost 10 years and what they can do to change that.
It is old-school RAD just like VB, VB.Net WinForms and RB/Xojo. Just drag and drop the components from the palette onto the form. Being an old guy myself I prefer that mode of working and find the Declarative UI to not be intuitive.
I would recommend anyone try the Community Edition that was interested in evaluating Delphi. Here’s the link to compare the editions of Delphi: Delphi: App Development Product Editions - Embarcadero
The IDE is a Windows App so you have to do your development on a Windows physical host or VM. For a UI based app Delphi has two primary ways to go about it: 1) Windows only - create a VCL type project; 2) X-plat create a FMX (FireMonkey) type project. Depending on the complexity of your form, just the single form can be used for all targets. I love that part of it. Lets say I want to tweak that form for mobile I can easily create a mobile version of that form which inherits from the base form and apply my mobile tweaks to the mobile child form. To my way of thinking I would create a child mobile form for phone and a child mobile form for tablet off of the first mobile child form. The reason why is that I can probably put 95-98% of the mobile tweaks/code (iOS and Android) in the base child form and child phone and tablet forms would get the form-factor specific tweaks OR you could just add a lot of compiler conditionals in the original form to handle all the variants if you don’t like inherited objects.
Embarcadero has lots of free plugins available, additional components, reporting generator components, form skinning, etc. Plus there are a number of solid third party components which can be purchased.
Did I dump too much info? lol I can try to answer any other questions if you have them. Glad to help out if I can.
Remember the (in)famous last words in the CEO’s Covid-era (2022) XDC keynote: ‘…ah, you are still here? You can go now’.
Hi Norman,
I have to correct you; nobody here is a troll. I only see hurt people because they realize Xojo could be so much more if Geoff Perlman had listened.
I like this democratic community so much. I don’t bother myself much anymore about TOF; sometimes, I visit, but I cannot remember my last post. I think that says enough.
Chris
Absolutely not, this information is terrific. Thank you for taking the time to write it out for us.
Actually we have already moved all our applications except 1 from Xojo to various other platforms based on their nature.
Like we re-coded a photo album designer (a direct competitor to apps like Fundy Designer) in Delphi as it is very calculation intensive.
All business desktop/mobile apps that are heavily based on Database are re-coded in WX.
The scarce feedback to your post in TOF indicates that developing commercial software in Xojo is already dead. You could announce the end of AppWrapper support in a year from now and see what happens.