Xojo for rant

it is not a bargain for private users. Adding my 2 cents as the pricing and the return of value is a big topic in some rants:

If you are using Xojo for your business I think it is a no-brainer compared to other solutions. I have a business need for the Adobe Creative Suite. But we are using it perhaps 5 times a month for a few minutes. But I’m paying more for CS on a yearly basis than for Xojo, which I’m using each and every day.

On top of that: no one is forced in buying the updates. You can still work with the old version, and skip a version if it doesn’t contain the new features or fixes, you are interested in - I think that’s a rather fair model, compared to a yearly subscription for instance. But we can discuss this for eternity ;-).

If there is one component which I think is overpriced than it is Xojo Cloud. But many, many people will disagree with me. Xojo Cloud is easy to use, stable, secure. And usually you would just make your customers paying for it. Xojo knows that we have a lot of customers in the NPO area, which can’t justify these monthly costs. But especially with Web 2.0 it is now very easy to run apps on your own servers (hence I’m very happy). But “my rant” over Xojo Cloud is not the rant of others. Despite the price I’m missing functionality: Automatic backup/restore of databases (we have very large databases), some control to install own libraries, connecting multiple domains (including! Let’s Encrypt Certs).

Rants of others are vice-versa often of no interest to myself (for instance using Web 2.0 solely in internal networks, and not the internet) and they won’t understand my challenges. Now expecting that Xojo (or any other company) can satisfy the needs of all customers is unrealistic.

Last but not least: iOS - well, compare the price to the needed “development license” Apple is charging you, that puts the Xojo price in a complete different light ;-). Ok, for 99 EURs a year you get the Apple Eco System, the right to pay them 30 percent of your revenue, a sometimes buggy platform, and the “right” to discuss silly policies with Apple :-).

2 Likes

The pricing is very competitive. As a relatively newcomer from FileMaker I have already won two contracts that I would have stood no chance obtaining with FileMakers pricing model. if you are a professional and using this product as part of your business the price of the software and it’s distribution licensing model(there isn’t one!) make it a no brainer really.

6 Likes

FileMaker is not mainstream and it is anything but a no brained do try and develop a web app with Web 2.0 if the competition is using one of the other web development frameworks, it’s a disadvantage. It’s easier manipulate Bootstrap outside of XOJO and use something like Ruby On Rails and it takes two lines of code to map ActiveRecords and you’re able to start interacting with the DB, so you are not even bring RAD to the table when competing.

1 Like

there is no perfect ide for multi platform.
the best option is to choose one ide and create a native app for a single target what means
xcode for mac and ios,ms vs for windows,android studio for phones with this os.
at marketing all products are the best on this world and promise everything until you believe it.

about xojo the ide should provide web1 and web2 in parallel for awhile (my opinion),
i not need this but i thing about users that created much web 1 apps in past.
a unnecessary conflict. (somehow a w1. namespace better than use the old and new ide in alteration)

some other decisions had also choose more wise (with the community) as example the modifications in classes.

that points could get more attention.

  • team too small
  • ignores user’s need
  • doesn’t listen to users

xojo is a good product and need more improvements just like any other software over the time.

2 Likes

On a positive note, Xojo could expand by converting VB 6 users. A while ago I discovered that a program I used for years was still being developed using VB 6. They have been around since the 80s. I’ve noticed they seem unable to improve the charting graphics and most improvements are small incremental things. So perhaps small VB 6 developers supplying niche markets could benefit by some sort of ‘conversion’ or ‘migration’ assistance or something; to move their code to Xojo. I understand that some of these guys must be getting on in years and change is difficult. So making this easier might help Xojo grow.

1 Like

That’s true, as much as it is true that you can do “more” with Swift for iOS / macOS. And if you are solely developing for Windows, MS Studio is probably the better tool. BUT: what are the efforts you have to invest to make it possible that 2 lines of code are sufficient?

How long will it take to build up a working dev and prod env for Rails (I agree, not rocket science if you know what you are doing, but for beginners, there is a learning curve too)? Should you jump into Rails without knowing Ruby? I would not recommend it (replace Rails by Django and Ruby by python - it doesn’t matter). You are talking about RAD, but none of these env is RAD out-of-the-box.

But even if you have a running dev / prod environment: it is not as “convenient”, not as simple than Xojo, which means just dropping your controls on a Canvas in a quite good (not perfect) WEB2.0 WYSIWYG IDE. So I really think that Web 2.0 is a very big step for easy RAD for users who already know Xojo). Will Xojo web 2 ever be as fast as a proprietary solution? Will you ever be able to design easily as “exactly” than with specialized frameworks? Will you have as many controls in Xojo out of the box? Most likely not. As much as you always can do more with Swift and Xcode for iOS.

But can you be faster in building a RAD app in Xojo than in any other solution? Probably: you need to download the IDE, launch it, design it, put some code in it, and make it run … that’s simpler than any other solution, not evolving any terminal “hacks” etc… And you can to a certain extend re-use code you have from your desktop world …

There is a price for everything in life: being able to develop on multiple platforms comes at the price ticket that genuinely you have a few “restrictions” and “limitation”. Am I a fanboy? No, I like the tool, and yes me too I hate those restrictions and limitations. Sometimes more, sometimes less but I am convinced that one tool can not cover all aspects. If a customer wants more and is willing to pay for it, I’m willing to convert my Xojo stuff to whatsoever solutions. But first I need to get the deal, and I want to put as less effort into that exercise as possible. And that’s where Xojo excels for my business, yours might be different of course.

2 Likes

Maybe 10 years ago they had that chance, but the “converter” did not convert any code :rofl:

This days, they want to burry the “basic” of the tool, deprecating DIM, getting rid of MSGBOX in API2, etc, etc. So… I think that nowadays other tools are more attractive for vb users than what is left of realbasic

1 Like

TLDR; I don’t believe ranting helps.

I don’t ‘get’ ranting. It doesn’t help me or Xojo or other users.

I have been on the bleeding edge with the conversion to API 2.0, first for desktop, then for Web and hopefully soon for iOS/Android.

Each time I find a showstopper, I don’t whine. Instead I try to work around it. If I can’t I create an sample project showing the issue and add it to Feedback. This enables me to move on to other code in my project. I am stunned that within a day it is usually verified and often fixed, but I still have to wait for the next release. I then go back and test my sample projects and remove them if they’re now fixed. I could rant, but don’t see the point!

The Xojo Roadmap is brilliant and has allowed me to synchronise my coding with its release order. This gives me less need to rant. For my paying customers, I never tell them what is on the Roadmap else they want it tomorrow, and rant against me. It’s better to promise little and deliver a lot.

I have now built a huge library of external Windows, Modules, Classes and Containers that are compatible across Desktop and Windows (identical duplicates in the case of Windows and Containers), and much of this works with the current iOS too. These are all used across multiple applications. Fix once, fixed everywhere.

Now I must add that my latest Web 2.0 Apps are not ready for release due to bugs, but ranting will not get them released any faster.

7 Likes

so do I. Well, honestly I had to learn it the hard way … :slight_smile: - In the past, over 10 years ago, I promised according to a vendor roadmap, I learned to wait and not to promise anything until I have tested it. Makes life much easier …

4 Likes

I personally love their bug system…but the gears in their system are not turning.

The fact that issues permanently gets stuck on “Needs review” gives the customer sense that he is posting into empty void where his issue is not even read. This has to be fixed. I know of several people that have just stopped submitting bugs and consider it waste of their time. If the intent is not to read every single bug report then to keep up good looks it may be better to skip the bug system totally.

For bug system to work then you need to read every single report and give it some status. Its fine if you dont plan to fix it or you put it somewhere way back in the queue but the customer needs to get sense that the report was read and the report got internally categorized.

And of course its absolutely terrible that you have to lobby for a bug to be fixed. The internal categorization and evaluation of the bug report should in perfect world be what tips it over or puts it on hold. (But I know t hat cannot always be the case since often they may not understand the full implications of the bug)

8 Likes

I appreciate that you wanting us to be your partner. I can only point to our history as an indicator that we have always pushed forward and we do respond to the demands of the user base. We can’t always respond when everyone wants us to or in the way everyone wants us to but if we weren’t doing things mostly right, we wouldn’t still be here.

I’ll contact you privately to hear more about your use of Xojo.

2 Likes

Don’t worry about that. We all agree that for a Canvas control a Pressed event without the position in the Canvas would be worthless.

1 Like

In a perfect world. Unfortunately, we don’t live in that world. Feedback is only used by a small percentage of users so we can’t tell (in most cases) if a bug is being experienced by many users or just the one user that reported it. That means we have to make our own judgment call until we hear otherwise from users.

If you check what I wrote then I am asking for exactly that. That the tickets actually get read and you pass judgement. That is the heart of the problem that many of them never get read.

6 Likes

I have to agree. Cases very frequently get stuck in limbo. Maybe Xojo should internally be tracking the number of cases that sit in “Needs Review” for more a few time periods, kind of like an accounts payable readout? Such as number of cases that needs review longer than 14 days, longer than 30 days, and longer than 90 days? Xojo would pick the specifics of course, but it could be a good metric to keep an eye on. Starting out, I’m certain the numbers would not be good. But might serve as motivation to actually DO something about cases that seem to never be acknowledged.

8 Likes

+100 for Björn. Feedback is broken.

Even if the bugs get to “reproducible” too many are never fixed. Without Christian my application would be dead. Okay, I was the only one to make Dates crash. But nobody ever looked at said crash bug.

Telling Xojo “bug has been fixed, close bug report” does NOTHING.

3 Likes

This topic is almost like “Rant HERE”, and people is responding the call.

Oh, this thread went in all directions !

My question meant "do we get anything (positive) from ranting ? Unfortunately many posts didn’t offer an opinion on this, and I found a lot of ranting :worried:.

So I will answer my own question: no, ranting does not bring anything POSITIVE, it doesn’t help improvement in any way. To me, looks like ranting is a new sport.

Forums like this one are there to let the members of a community communicate, newcomers ask questions about “how should I do that”, experiences developers tell about the tricks they have implemented, etc. What kills a forum is ranting and thread high jacking. It’s not specific to Xojo, but what a nuisance.

Looks like a lot of users lack discipline - hum is thing ranting ?

Bugs always existed, even way back in time. Let me tell you two I faced.

Around that second half of the 80’s, I was developing for DOS in C - you think today it’s hard do develop, in these times the word debugger didn’t exist. I was compiling a file and got that message “Something went bad while processing. Please contact Microsoft”. That was in a time when emails and web didn’t exist. What did I do ? I knew where the issue may have been and I simply reorganize my code and the compiler was happy.

In the beginning of the 20’s I was developing an embedded system and got a really out of this world issue. I stopped the program at some point and had a look at the memory. What I found out is that the compiler or linker set the beginning address of a number somewhere in the middle of the address space of another variable. The tools I was using hadn’t been updated for years and would not be anymore. What did I do ? I declared a variable in between the variables that were overlapped, a variable that I would not use. and that solved the issue.

So instead of ranting, how about users help each others and help Xojo by creating a bug in Feedback properly documented.

Thanks for your attention.

7 Likes

That was not my intention to call for ranting, please see my initial post. But looks like ranting is the nature of the beast.

2 Likes