Xojo Guesses for 2014

2013 was an interesting year for Real Software, Real Studio and the resulting Xojo company and IDE. After a long wait the new Xojo IDE with new branding and company name change was announced at the developer conference in May.

Xojo Release 1 occurred in June. It was buggy and the controversial Navigator was at the top of everyones list (mostly the naughty list but a few people liked it). The new Cocoa framework largely worked as promised and people rarely complained about it. Subsequent Xojo releases fixed most of the worst of the bugs in the IDE but even after the 4th release there are bugs in the IDE that obviously are not easy to fix (or they would have been fixed by now).

The change in licensing for Xojo affected everyone and mostly for the better. You can now use Xojo for free but you need a license as soon as you want to build for a platform. This made Xojo cheaper for many but a bit more expensive for folks like us that build for all targets. The only real issue that we had with the licensing change was that the licensing terms require non-builders to have a license if you want to save in the version control format http://www.bkeeneybriefs.com/2013/10/when-a-license-isnt-a-valid-license/.

2014 promises to be a huge year for Xojo. Many of the things they announced at the Xojo Developers Conference should be coming to fruition this year.

Xojo Cloud: Originally scheduled for June 2013 (as stated at the keynote address in May http://www.bkeeneybriefs.com/2013/05/xojo-cloud/ ) it looks like it will finally be released in 2014 Release 1. It promises to greatly simplify the deployment procedures for web apps. We already know it will be missing database server support in the initial release but it appears we will be able to purchase additional RackSpace options for that. I will be curious how this works for consultants like us that have multiple clients we’re writing apps for. Chance of it happening in 2014? 100%

64 bit apps: At the developers conference they said http://www.bkeeneybriefs.com/2013/05/xojo-64-bit/ it would be ‎summer 2014 for 64 bit applications. It will be an option to compile for 32 bit or 64 bit applications and eventually 64 bit becomes the default. This will be an interesting transition. At the conference they said they were 70% done with Cocoa and for Linux and Windows they just needed to do testing. Chance of it happening in 2014? 75%

.NET Framework Usage: Developing Windows apps is always an interesting experience. Since the Win32 API doesn’t have double buffered windows like Linux and Mac OS X has,  what looks good on those platforms can often (usually?) look awful in Windows because of flickering. There are ways to minimize flickering but it’s next to impossible to eliminate it entirely. I hope something can be done this year. One of the possible solutions is to hook the Xojo framework into .NET libraries. I am by no means a Windows expert but one of the possible issues with this is that Windows XP doesn’t have .NET libraries shipped with it by default (though Vista and above does). Does this mean the end of Windows XP support or appropriate error messages? Chance of it happening in 2014? 10%

iOS applications: http://www.bkeeneybriefs.com/2013/05/xojo-for-ios/ ‎ Using Xojo to develop and compile native iOS applications should easily be the biggest news item of the year for Xojo. To say that this might be huge for the company is an understatement – assuming it works as advertised and Apple accepts the built apps in the App Store. With the exception of a couple of demos we really haven’t heard much about iOS other than it’s progressing. If memory serves they are saying a beta will be available around the Xojo Developers conference in March with a summer release date. Chance of it becoming usable in 2014? 60%

iOS is going to introduce a new NameSpaced framework http://www.bkeeneybriefs.com/2012/05/new-frameworks/ that will eventually make its way into web, console, and desktop applications. iOS is a completely different beast which requires a different framework and their goal is unify the framework so that it can be used universally for all targets. There has already been much teeth gnashing over the proposed changes but I’m not too worried. First, it will only affect iOS (for now) and then maybe web by the end of 2014 and who knows how long it will take for desktop to get it. Second, the old (global) framework will be around for a while for a (hopefully) smooth transition. Until it starts affecting us I refuse to worry about it. Chance of it happening in 2014? Same as iOS – 60%

For a company as small as Xojo this list is rather daunting but they’ve been working on some of these items for years. I would expect something to slip into 2015 but we’ll find out more in March at the developers conference. What are your predictions for 2014 from Xojo?

11 thoughts on “Xojo Guesses for 2014

  1. I’d say you were quite optimistic in all cases. Subtract 20% from all your probabilities and I’ll be more likely to agree with you. :^)

  2. Can’t wait to see iOS Xojo in play. I’ve developed close to 200 apps for Apple and Xcode, however powerful it may be, just isn’t as user-friendly. I wouldn’t mind rewrite some apps from scratch using the new Xojo when it’s available.

    Best wishes to Xojo team and hope this is a productive year for everybody.

  3. “Does this mean the end of Windows XP support or appropriate error “messages?”
    It should, MS is ending support for XP in April 2014 and after that it will be over run with viruses and malware because the hackers that write such things will know the holes and exploits will never be fixed. Most programs that run on XP will run on Vista, Win7 and Win8 so there is no really compelling to reason to stay on XP unless you were trying to control the costs of replacing hundreds or thousands of XP machines at a large company. That may have been a viable strategy up until April 2014, but after that the security concerns will outweigh the cost benefits. Time for Xojo to stop worrying about XP as well.

  4. Until / unless the Windows framework requires changes that do not work on XP there’s no compelling reason to drop support.
    Hackers & viruses etc certainly may be able to target it but thats not a compelling reason to drop support for XP as a compilation target.

  5. What´s about LLVM ?

    If I understand the use of LLVM, it´s a virtual machine, that is running on many platforms. So if XOJO use LLVM for x64, then is the LLVM-runtime on windows for the display responsible.


  6. As Bob pointed out, LLVM is all about the compiler, not the display. The beauty of moving to LLVM is that Xojo, Inc. can concentrate on the Xojo language itself — the front end of the compiler. While LLVM takes care of the back end — compiling to i386, x64, ARM, etc. It lets Xojo, Inc. focus on their strengths while gaining all the heavy lifting from LLVM.

    A great move by Xojo, Inc.

  7. Can there be a chance for mobile app development in xojo. It will be great if the can incorporate that in their development.

    • This looks like a certainty. Xojo for iOS was shown off at XDC 2013. Since then they’ve updated us several times on progress. The real question with a 1.0 product is what it is missing and how painful that loss is going to be.

      As was stated on the forums several times Android development is a completely different beast. Lots of unknowns for the Xojo development team.

Comments are closed.