Learn more.Ĭonfigure and apply almost any type of license or activation process to your software in minutes with the Xojo Plugin. Protect the software you create with computer specific activation. Learn more about XojoApp Desktop and XojoApp iOS.
Save project time and money with proven software components for programmable grids, charts, large text editing, drawing views and tool palettes, string and file management, simply high-speed XML.
Extract source code files and UML diagrams from a Xojo project file. Learn more about tools for Xojo developers:ĭesign software with UML diagrams, then click to generate Xojo code. To build a profitable business, use design tools, reusable components, protection and licensing and a Code Signed installer. But not only out of this reason, also because we find no developers using it or even want to use it.To build great software, start with a solid IDE like Xojo. We rewrite a working piece of software, because we fear, that it could break our business some day. The reasons were always, that Xojo is to small to be the backbone of companies with the plan to grow to 50+ employees, that the community is to small, that the dependancy is way to high and that the open bugs (I think they get that from the forum here), were to risky. Some of them were even impressed, that Xojo can perform so well in some cases. Not because of the language it self or the technology behind. In every three reports of their technical due diligence, the Xojo system was listed as “technical dept”. This was the only one, which didn’t told us to instantly rewrite the system, but to plan it’s rewrite within the next 3-5 years. Reason was the same: Licencing, lack of support, lack of open source and community and dependence from one small company. Xojo was on that list next to Perl, Elm, AppGuyver, Ninox, B4J and such, Smalltalk, Livecode and Filemaker. They told us, that they have a list of technologies, which they don’t want to have in their company-portfilio. As they saw that we have internal tools built in Xojo here, they couldn’t hide a smile (honestly). The second Investor made the tdd by them self. They said, that the licence, the release modell, the small team of Xojo, the closed source, the bugs and the tiny community is a huge risk and we should redevelop all systems which are currently in Xojo asap. → In the end they told the potential investor to implement a second CTO here since it looked like we tend to make bad IT decisions. The outcome was, that they like the approach, but they made also some research, talked to Xojo-Users here on the forum (I read the chats).
One tdd-contractor didn’t know Xojo at all, which is not a good sign, since they are extremely experienced and they do hundrets tdds each year all over the globe. We now had three technical due diligence (tdd) and that is story I wanted to tell you. Now we are negotiating with bigger investors to collect a 5M+ funding. And also, some of us began to like it somehow. While we don’t start new projects in Xojo, we always kept the software which was developed in Xojo maintained. First of all, because no one wanted to go back to the VB days which are gone and what we think is okay. A part of our internal tools are build in Xojo, cause a former consultant of us used it to fulfill our contracts. We are a Hamburg based IT company/ software startup with about 20 developers. However, this time I write because it may be interesting for you guys to. This is the first time I write, cause we usually have a company account without personal informations.