Gavin Smith.
Today Iāve got an āTell us what you thinkā mail⦠just discarded it.
Havenāt been on TOF nor the Xojo Profile Website for awhile but as far as I remember, I didnāt wanted to be asked by marketing.
Yes, thatās how shitty marketing respecting users.
And again, a biased surveyā¦
Apparently you only get the email if you have set the flag in your profile. But it also takes me a few tries to convince that an empty checkbox means itās not set. Well, as former users, we know that mistakes are human
You did right! Some weeks ago I reported in this thread that Claris asked developers for candid feedback - and got candid feedback. Now, more than 4 weeks later, there is absolutely zero feedback from Claris. They just carry on with their marketing nonsense as if nothing happened.
This marketing thing must be an incurable disease.
I actually answered it but was brutally honest. The chances of me using Xojo again are slim to none for all the factors weāve all hashed out on this forum over the last couple of years.
Same for me.
There was no reaction or visible improvements during their surveys the last decade⦠how on earth can anybody expect another outcome in this one?
They are finished and life in denial, but do not know it yetā¦
well, the millions of low code coders smarter than us and understanding all the new benefits might vote differently ā¦
Exactly the same for me. No doubt it will just get ignored or deleted.
Well, IIRC the previous surveys were of the, āWould you recommend Xojo to others?ā variety. Customer engagement survey or whatnot.
This one asked specifically about satisfaction with Issues and Documentation and then wanted specific issues that are holding me back. I essentially said there are too many issues to list and I didnāt believe that putting them in the survey would make any difference whatsoever. Plus, the Xojo ship has sailed for me.
Do I expect them to change? No. I forget the exact phrasing of the question but something to the effect of what does Xojo have to do different to be better? I said new leadership. Which of course will be ignored.
This is about the same way they came up with the initial 2022 bug bash list if I recall
New leadership is a prerequisite for most anything else theyād do
If you said āfix development process so code is better tested before its shippedā that requires leadership buy in that the process needs fixing - I dont believe they think it does
If youād said āhire more developersā again it requires leadership buy in that this IS a problem
Again I dont think they do (aka adequately staffed)
Leadership needs to take a hard look at what things they already assume, and whats things users consistently bitch about and reconcile the two
Until, or unless, they do nothing will change
They need to hire an outside consultant to come in and realistically assess things, how they can improve, etc
And NOT one of the people who already use the product or are āfriendsā
Someone from completely outside & objective
As was recently said on radio ads here for an election we had
Nothing changes if nothing changes
Its the same there
Continued fumbling of documentation:
https://forum.xojo.com/t/desktop-listbox/75955/7
āAbandon all hope, ye who enter hereā
Dante Alighieri, The Divine Comedy
I received it too, but answered. And a few hours later one of the main issues for several of my apps, dating back from years, had been fixed.
A pleasant fact.
I also answered. Explained to them the reasons why Iām migrating away from Xojo. Why spend hundreds of hours migrating existing apps to API 2 just to stand still feature wise, when I could spend a similar amount of time migrating to a different language that will offer more modern features and fewer bugs? I guess thereās the distant hope that upgrading to API 2 will mean some Xojo issues I have āmightā be addressed in the future, but why risk it when I can migrate to Swift and known that the issues I have wonāt be there and Iāll be able to take advantage of all modern MacOS features?
Basically, Xojo gave me the excuse to migrate away from them. Iād been thinking for a while that Iād like to move to Swift, but didnāt want to waste time putting in hours of work just to get back to where I already was with Xojo. Upgrading to API 2 meant I had to do that anyway, so why would I stay? As Radiohead once said, āyou do it to yourself, you do, and thatās what really hurtsā.
I also expressed my dislike of the new documentation.
Well, I had a similar root cause for leaving. Most of my remaining apps were anyways web based. When I found out, while investigating into Web Plugins Development, that I had to learn TypeScript for that, and as I did already know that I had to use CSS and JS anyways for Web 2, it was just logical to move everything to one platform.
And I know of many to whom it was just the last drop to finally move away, something many already had in mind for quite a while ⦠I never used the new documentation, but just looking at it, I donāt see any benefits whatsoever.
API 2 seems to have been the last straw for many
For others it was the Web 1 to Web 2 fiasco
Either way many years of forgiveness is gone
The assessment I gave them is that itās not cross-platform in the sense of āone code base for all targets for the most partā and that the mobile and web versions I judge to be too limited to be of use. For the desktop, thereās nothing compelling in terms of stability / ease of use / features to overcome my clientās natural aversion to anything thatās not in some perceived sense āmainstreamā, and the Green Ones are now garnering a reputation for bugginess and instability as well.
Iām sure theyāll take it to heart, even though I didnāt do their job for them (look up / upvote my particular bugs, yet again. Iāve filed them; they can deal with them, or not, along with all the others).
He promote changes, he got changes⦠but not as he thinksā¦
Sometimes the change is that the customers are going.