I wrote most of the following in a private message… But thought it might be a good idea to share it here to see what other’s think
IMO it was never likely that Xojo would become a WIDELY used language by professionals for producing apps for sale.
Too much prejudice against it’s BASIC origins that the name changes won’t hide as well as the fact that no X-Platfrom RAD environment will produce the best result for any single platform, and most apps apps sold are not X-Platform and do not aspire to be
What IMO is Xojo’s market is those that want to produce custom apps (which is what RAD was always all about IMO) that are X-platform
IMO three classes of people tend to do a lot of that (and of course there is overlap):
-
Certain pros: Consultants/Contractors/Full time in-house developers
-
“Citizen Developers” : that i will define as those who write apps to help themselves and others at work, but who’s job is not coding… We know the workflows and users best and combining that with some coding skills (if done well) is a huge plus (and how I got into coding)
-
Pure hobbyist that do not do business apps or people just learning to code in general
I think (as originally for VB) #2 is Xojo’s biggest market… While more price sensitive than the pro’s, they are less so than the pure hobbyist I think. The 3s being most price sensitive, are likely just to use it in the IDE or use a free platform specific tool. 1s and 2s need compiled apps for sure.
But to sell to #2s, besides being a more complete easy to use RAD environment, it helps to have some commercial apps made with Xojo AND have the 1s around as it gives them confidence that Xojo can be safely used at work, and is OK for big complex projects. The 1’s are the ones helping create a 3rd party ecosystem and help it to grow and help the others on the forum a lot.
The 1s may not be the biggest source of income, but they matter more than for just the money they bring in IMO
BTW Xojo being done in Xojo is not that convincing to many because it is the same company … independent examples are always better.
In large part IMO what the 2’s need is the same as the 1’s in terms of RAD AND backwards compatibility… (Workplaces tend to have a mix of OS versions) …
I have multiple copies of expensive software at work that runs equipment that would cost of north of 10K each to upgrade to run on the latest OSes that I need to run apps on to interface with it… In general often management would rather not have such machines running old OSes on the net rather then spend the cash to upgrade… If it’s not broke don’t fix it. But I also have the same situation with some on the the latest OSes as well…
As business needs/workflows change these custom apps need to be updated even if the expensive software does not. I don’t have the time (or desire) to maintain separate code bases based on OS version… some #If XojoVersion is OK…
Backwards compatibility matters.
What concerns me is that these days Xojo seems to be worrying less making producing solutions easier by being a more complete RAD environment for desktop (which is still what is mostly needed for in-house apps IMO), or really any environment they support… In the past that seemed to be more of a priority. And now besides, that the concern for backward compatibility seems not to be what it was… or even understood.
These things make me fear for the future…
-Karen