I incorrectly assumed that some of the features that were - and in some cases continue to be - in development would be available sooner than later. I've certainly made a lot of mistakes.įor example, I became so excited about Xojo that I wanted to use it for everything, and in some cases, I tried to force it to do things that it simply isn't designed or ready to do.įrom a business perspective, I made assumptions about Xojo's development roadmap, and more specifically, about the timeline.
![xojo for android xojo for android](https://blog.xojo.com/wp-content/uploads/2017/11/1.png)
I've been critical of Xojo over the past few years, and I think some of that criticism was justified.īut I can't place all of the blame on Xojo. I was sad to see that, because, as I wrote at the time, I was "still rooting for Xojo."Īfter having been away from Xojo for quite some time, I've started to get a different perspective on it. But based on what I was seeing in the community, it had appeared that things had only gotten worse. However, I continued to keep an eye on Xojo, in the hope that things would change. By then, I had migrated all of my Web-oriented solutions from Xojo to PHP, and all but one of my clients' solutions from it as well.
![xojo for android xojo for android](https://xojoblog.files.wordpress.com/2018/04/lhlg155.png)
I last wrote about Xojo in September of last year.
![xojo for android xojo for android](https://pbs.twimg.com/media/E65dPU3WYAcFEAG.jpg)
It was as if I were parting ways with a good friend. But there was also a sort of emotional pain, of sadly and reluctantly giving up on the platform. It required redesigning and redeveloping many of the solutions that I had developed with it, which was extremely time consuming. I was worried that I had bet my business on Xojo, and that the platform - and company - might not be as stable as I had thought.Īs a result, I started making plans to shift my focus, and go in a different direction. I was concerned by changes that were being made internally at Xojo as a company. I was disappointed by what appeared to be a lack of progress from the prior annual conference. I was accused of being a "fan boy" at the time, and if that means that I was a big fan of Xojo, well then that label was correct.Īfter attending XDC in May of that year, my excitement started to diminish quite a bit.
#Xojo for android android#
Things like interops, Xojo-based plugins, Web 2.0, and at the top of my list, Android support. I wrote about all of the things that I assumed would be coming out in that year. Going Off the Rails, But Holding On to HopeĪs recently as January of 2019, I was still excited and enthusiastic about Xojo.
#Xojo for android code#
I referred to it as a sort of "development swiss army knife." And as my enthusiasm and excitement grew, I started writing about Xojo, shared Xojo code and solutions, gave webinars on it, and even spoke at a few Xojo conferences. I quickly developed my own frameworks, and started using Xojo to create Web apps, Web APIs, and more. But it wasn't long before I was using Xojo to develop all sorts of things - including console apps, which was a big surprise to me. When I first started using Xojo in 2015, I was primarily interested in it for its (then somewhat new) support for developing iOS apps. It "clicked" with me, and by that, I mean the Xojo IDE, how projects were structured, the Xojo language, etc. And I was glad that I did, because it was Xojo that resonated with me in a way that no the other platform did. I even explored the SalesForce platform, and dabbled in things like ServiceNow.īut it was at the encouragement of my friend Hal Gumbert that I gave Xojo a try. I looked at all sorts of things, including LiveCode, Delphi, OutSystems, and more. I've written in the past about how, after I decided to stop doing FileMaker development work, I went in search of a new rapid application development platform to work with.
![xojo for android xojo for android](https://www.saashub.com/images/app/screenshots/7/fd17f050aa90/landing-medium.jpg)
It was the same amazement that I had experienced when I first started using Xojo back in August of 2015.Īm I back to marketing myself a Xojo Developer? No.ĭo I think that Xojo is "out of the woods?" Not yet.īut I'm giving Xojo another try. I haven't used Xojo in well over a year, but was amazed at how quickly I was able to get a proof of concept built with it. It needed to run natively on macOS, and so I decided to try developing it with Xojo. Recently, I wanted to work on a personal project that I had been thinking about for awhile - a utility that would make doing NetSuite development work easier.