Adapting to Build 3088 of Intel XDK


So, I upgraded to Intel XDK build 3088 today (from build 2893).

And I’m in the middle of building an App.

But I’m brave.



Here’s some things I learned:

  • You may have to rebuild your app. I’ll just say it. Rebuild your app. This article still works as to how (you don’t get “enoent” errors anymore – instead you can expect all new and improved errors).
  • My favourite way to install custom plug-ins no longer works. That’s OK. There’s a solution here.
  • When your build is successful – on iOS at least – the file extension is no longer included. I’m adding ‘.ipa’ manually in order to install my adhoc build to iTunes for testing on my phone / tablet.
  • When starting again, I used to like building a new project sans-Cordova, and then upgrading the app on the fly to a Cordova version (it used to be ‘cleaner’ that way, if you will). No. Not any more. Now, it is best to build a new project as a HTML5-Cordova project from the outset. Or, no “onAppReady” for you…
  • “Is Tablet” plugin is only going to work if I seek support from the developer as it turns out. There are pure JavaScript equivalents however. This one seems to be pretty effective.
  • screen-orientation plugin only works in CLI 5.1.1. Reference to solution here. Except in my testing, it no longer seems to work consistently.

If I find out any more sneaky quirks or problems, I’ll let you know. Frankly though, Intel XDK continues to march onward in the right direction. Sure it’s annoying to rebuild my project from the ground up, but from the most part that’s a copy and paste in the files system and a manual copy-and-paste of the content of js/app.js and a manual copy-and-paste of the content of index.html. And yes, I’m not wild about the RSI that I get from clicking on all those icon and splash-screen settings – but if I was less lazy I’d hack the XML direct. Or something.




Best Practise App-Development – A Discussion Paper

For those who are not yet up-to-speed: cross-platform-app development is a reality. Sure, it may not (yet) have all the fancy-pants bells-and-whistles of native App development kits. But it’s really close. Unless your App absolutely requires a particular feature only found in a proprietary software-development-kit, consider XDK’s (cross-platform development kits).


  • Intel XDK or PhoneGap / etc.
  • Research (complexity / competition / App-store policies)


Folder Pattern

Once the prerequisites are completed, create a sandbox of your App on your local machine. My folders follow this basic pattern:











The Mighty Sandbox

My SANDBOX folder holds my ‘sketches’. The screaming upper case of the sandbox’s root folder name is purposeful. It can’t be missed.

Now follow these steps:

  1. Build the user interface and as much functionality as is feasible that can be performed without the use of Cordova plugins. (Cordova plugins work on a smart-device, not in a sandboxy, webby environment).
  2. Make a backup of the sandbox environment at least once per day. Generally, this can be done by zipping the project folder. The zipped sandbox project can then be versioned and copied to a cloud service as a further backup.
  3. Once the sandboxed App is complete (and the last backup has been safely archived), I will then copy the semi-working to working file assets to a folder outside of the SANDBOX folder, but now directly under IntelXDK (I build in Intel-XDK’s environment).
  4. On an at least daily basis, I’ll create backups of the production-space project, same as the sandbox’s naming pattern. These zip files will be placed on the cloud, but in a production backup folder (and not in the sandbox’s backup folder).
  5. Once the App is complete (and by complete, I mean for sale on App stores), I’ll then clean up the archives by deleting all of the old sandbox and production zips – except for the most recent zips. So, I’ll keep one sandbox version (the very last before moving to production), and the last production version. These are now renamed to ‘v01’ of the App. Should I create an upgrade, the last production zip will be where I start, and the user interface and code that doesn’t rely on Cordova will be placed into a sandbox location, where the cycle will start anew. The next released version will be ‘v02’. Probably.


What I’ve learned from this process

  • Research is not foolproof. I’m using Web Audio API in my current App. What was working in the sandbox is not working in the App builds. At all! Really frustrating, and it cost me a day of further research to figure out why. And a large number of JavaScript libraries.
  • Toggles in fancy frameworks are not working for me – still! Buttons it is. Sigh.
  • Apps can be moved back to the sandbox if necessary.
  • Working code can be retrieved from any previous version, including from the sandbox. Yay!


What’s not perfect?

Do I make a backup every day? No… Shame, shame, shame. Seriously, don’t be tardy on backups.

Where is my code? I’ve got, like, 20 backups to choose from (six backups always feels like 20)! This scenario happened to me on my very first App. I’m sure it’ll happen again.


Got any tips or advice? Feel free to comment below!

Enoent When Installing A Plugin in Intel XDK

So, I was minding my own business, doing my own thing. Working on my current-est app. In Intel XDK.

And I was installing a plugin. It was the insomnia plugin (a featured plugin). Nothing special about it. Other plugins failed too (whether featured or core).

But I got an error. It was saying that that the plugin.xml file could not be found (in my personal directory). Which is surprising, because this file is located on a server on GitHub. Of course it’s not on my disk.

Why did this happen? To me of all people?

I think it’s because I removed a couple of plugins. Or maybe Intel XDK shut my project down in some kind of ‘unclean’ manner. I really am not sure.

I wish I had taken a screen shot of the error. Anyway, the applicable Google search is “intel xdk install plugin enoent plugin.xml”.

Except, this search suggests reinstalling Intel XDK. And not much else.

There’s another option to try first. In the Intel XDK project list:

  1. remove your project from the project list
  2. use your operating system to make a zip (backup) of your project
  3. use your operating system to rename your ‘old’ project folder (eg. to “v02_ProjectName”)
  4. use Intel XDK to create a new project from scratch with the same name as the old one with the same basic starting properties as last time (eg. from the same base template etc.)
  5. convert it to a Cordova project
  6. add the plugins that you need, the normal way. This should now work.
  7. From the www folder in the old directory, copy over everything except for the index.html and the xdk directory
  8. just in case, open the old index.html file and copy and paste the contents into the new index.html file – being careful in particular about the JS library script links. They might be different, you never know. Worth visually inspecting.
  9. Your project should now work. You’ll need to rebuild your XML files and other files directly above the www folder manually.
  10. Don’t copy the www\xdk files from the old project to the new project at all. I’m not sure if this is important or not. It doesn’t hurt not to… [SEE CORRECTION BELOW]

Well, this worked for me. See how you go.

CORRECTION TO 10: According to Intel, the following applies: “do copy the init-dev.js file from the old (XDK directory) to the new project (inside the www\xdk directory) if you are using the “app.Ready” event to trigger your app or if you are using App Designer (which uses this event). You may also find some custom services code in that directory, if you were using that feature.” Thanks for the advice Paul!

Intel XDK, Or, How I Finally Built My First Multi-Platform App

wiilo on all platforms

I have to admit up-front: I have a over a decade of experience developing applications.

I’ve written applications largely for enterprise businesses. This meant that I used commercial software programs and proprietary programming languages – mainly driven by the policy of the organisation I was developing for, employed by, or both.

In the meantime, open source languages grew up. And, whilst I had a smattering of JavaScript and CSS and HTML skills, my skills within these areas wasn’t good enough to migrate directly to a job in web development. Which I have recently chosen as a career option because:

  • someone hid my cheese, so re-skilling became necessary
  • there’s a lot of people who want web sites and stuff like that
  • there is this promise of multi-platform app development for smart devices

So, I started re-skilling. I chose freeCodeCamp, or, it eventually chose me. I’m honestly not sure which. The “how” I jumped into freeCodeCamp’s waters is not important to this story. It is important background information though.

The other important piece to this story is that promise of multi-platform app development.

I’ve tried for two years, or maybe more, to locate a decent tool that lived up to the promise of multi-platform app development. I’m sure if I stuck with some of the tools I’ve tried in the past that maybe something useful could have come of it.

But, here’s the rub: I’m in a huge hurry. I don’t have time to learn. I really need a development tool that actually works out of the box with minimal effort. I guess I’m used to commercial products in that regard.

Back to freeCodeCamp. All I’m going to say is, I got to the zipLines. And I finished those. I’m also a little attention-deficit. Once I’d completed the zipLines, I realised that: “Far out, I can build web-based apps now”. I was now proficient in open source languages: markups and scripting languages like HTML, CSS and JavaScript. And I needed a break from school by this stage.

So, I looked around again for tools that might live up to the promise of multi-platform application development. And, after a bit of try-and-flick, I reacquainted myself with Intel XDK (yeah, I had this installed on my machine for about 6 months or so, sitting idle). In fairness, my scripting skills were somewhat lacking when I first installed it way-back-when (despite my comprehensive understanding of VBA, object oriented coding and relational database integration).

Intel XDK had also improved a lot, and before I built my first app with it, I upgraded to the (then) current version.

So, why did I choose Intel XDK over its competitors. Over the years I’ve tested and thrown away around about ten different tools. Here’s a summary of my experiences:

  • One competing product did not enable the end-user (me) to edit my own app. I could start building one, but then there was no known way to edit it. This isn’t a problem one expects – ever. You know, after a break, like, I don’t know, shutting my computer down so I could go to sleep, and then coming back the next day to continue building my app – but no way to access my work on my machine? Guess how long that development tool lasted on my machine… Yes, I looked for support. The answers I found disappointed me even more than not being able to edit my own code. Grrr…
  • Documentation: I tried another tool where the documentation was 12 or so months old (according to the published date). In that time, Cordova had moved light years past where that stale documentation was left. And, like so many things covered in dust, the instructions on how to use this particular tool I’m thinking of really wasn’t that relevant or useful. In the bin it went.
  • Other server-based tools kind of make me nervous. What happens if the server goes down or the responsible organisation goes bankrupt? How do I get my damn code back? I don’t like that much risk. The world turns too fast. Things fall off all the time. I don’t need for my IP to be flung off the world due to a poor choice of application hosts on my part. And server-only-based solutions tend to cost a lot more than I can afford. And who really owns the IP when the code I write is hosted on somebody else’s machine?

More About Intel XDK

When I played around with this version of Intel XDK, I found out, pleasantly, that I could get my app to run. First go. And it’s not a simple app – it uses geolocation in order to look up some stuff. And other trixy things. I knew in advance that I’d need some plugins. Playing around with PhoneGap earlier in the piece got me introduced to Cordova (PhoneGap used to be free, now owned by Adobe, not so free). This was months ago. Looking at Intel XDK suggested that some stuff could be done by Intel’s proprietary code, and maybe some would need to be handled by third-party plugins (by Cordova for example).

It turns out, when I started, that some of Intel’s proprietary code was in the process of becoming deprecated (but this wasn’t clear to me, the end-user, at the time). The bit of code I chose (on.device.ready – not it’s full name – because I forget that already) was on the way out.

I love Intel XDK – because it works – but, like many tools these days, the documentation does not keep up with the functionality. And it’s not that the documentation is necessarily far behind. In Intel XDK’s case, the documentation is comprehensive – and accurate (yay), but, a little hard to find (aww).

So, yeah, I’m trying to use this call, and my app is working-ish. And I can’t remember – did I upgrade to the next release and my app broke, or did my code simply not work perfectly and I also upgraded to the next release (yeah, Intel pump out an upgrade to Intel XDK about one to two times a month – try keeping up with that schedule as a sole trader).

In truth, I nearly gave up on Intel XDK. But, I thought: “Bugger this” (I’m Australian). And: “I’ve nearly finished this app. I’ll tough it out.” And so, I found some information indicating that the ‘on.device.ready’ call was not yet dead, but, it’s family of friends were dead and buried (deprecated, in capital blue letters). No point crying over loved ones. It’s time to change gears and aggressively move on.

So, I quickly learned about Cordova plugins, and how to use them in Intel XDK. Not that hard it turns out. In my first App, I’m using fairly well-used and well-known plugins.

And yeah, the good news is that once I’d figured out how to plugin Cordova plugins, I haven’t looked back.

So, here’s some short-cuts to building an app with Intel XDK. My pearls of wisdom to help you, the reader, to avoid the darker paths I took, and stay well in the light:

  • I don’t care what app you’re trying to develop, tell Intel XDK to build a Cordova version. Just in case you need to use a plugin. And, yes, you’ll probably need StatusBar. Because iOS.
  • You’ll need, at a minimum, HTML and CSS skills. Plus some JavaScript in order to use the plugins properly. Yes, you can use JQuery instead if that’s your thing. How much JavaScript or JQuery depends on the app you’re building. You’ll need to be able to build web sites in order to use something like Intel XDK. You don’t know how to build a web site yet? Here’s the solution: join up to freeCodeCamp, and learn as far as and including the zipLines. Once you’ve done that, you’re ready to play with Intel XDK. Yes you are.
  • For your first app, tell Intel XDK to build using one of their templates. This will give you some ready-made code, which will help short cut the “wait, now what?” part.
  • index.html: this is the first user interface that your App’s eventual end-user (customer) is presented with. Your knowledge of web site development that you acquired up-to-and-including the freeCodeCamp zipLines will help you figure out what to do with this file.
  • GitHub: you will want to follow the instructions for each plugin you use. To find your plugin’s documentation, Google “github cordova [plugin]”, where “[plugin]” is the name of the plugin you’re searching for. For example, the search “github cordova statusbar” should take you to the statusbar plugin pretty easily. The cordova plugin documentation on github is excellent.
  • StackOverflow: ask your “dumb” questions here. Don’t forget to search for answers to your question first. The vast community of mentors on StackOverflow make a particular effort to point out that your question has been asked (and answered) already.
  • Intel XDK product forum: ask your “dumb” Intel XDK specific questions here. The guys at Intel are your friends (happily). And the other developers using Intel XDK are also happy to help if they can.
  • Intel XDK builds three packages when building for Windows devices. I’m still trying to understand why it builds three, but I only need to upload one to the Windows store. Check the Intel XDK forums for the answer. I asked. It’s documented now. Not the complete answer. Just the answer you will need in order to continue. It’s enough.

Keep It Simple Stupid

OK, here’s the basic advice that your Mum and Dad should have told you before you left home:

  • create the least amount of code possible.
  • this includes asset files. My first app had too many CSS files and too many JS files. Seriously. The “aww, snap” that I was having with “on.device.ready” gave me an opportunity to consolidate my IP into fewer files and to throw away bits that weren’t actually used anywhere. It’s a best practise thing.
  • Use other people’s code (not in the plagiarism sense) – use the ready-made templates that Intel XDK provides to short cut the learning curve. At least for your very first app.
  • Stuck on a “how to”? Ask Google and you’ll find the answer in StackOverflow. Modify the learning for your purposes, and then move on to the next problem. You’ll know for next time.
  • Read books. Ha ha ha. Like I have the time. Seriously though. Find the time.
  • I’m still reading about the Swift programming language… It’s not even related. But it’s about code at least.
  • Use other people’s assets. For my first App, I found a CSS animation library, and a neat font library. I made sure my App attributed these libraries in the “About” information page of my App. Per the license conditions. And because it’s the right thing to do.

Using Intel XDK to Create Your First App

Download and install Intel XDK.

In Intel XDK:

  1. Click “Start a New Project”.
  2. Choose “Templates” and then “Layouts and User Interfaces”.
  3. Choose Tab View App (or you can choose another template type if you like). Tick “Use App Designer” (this will install some ready-made code to build from and start with – yay).
  4. Click Continue.
  5. In the Project Window, click the Upgrade to Cordova button.
  6. When the project is created, add the following Cordova plugin (back at the project menu):

The plugins you choose will depend entirely on what you’re building. The plugins help you use the features of the devices your app will run on. It’s likely you’ll need at least one. Because iOS.


I’m on a Mac. To develop the HTML bits, I used Aptana Studio. To develop the JavaScript, I used Eclipse. And sometimes TextWrangler. My CSS was either developed in TextWrangler or Aptana Studio. Sometimes I used Intel XDK.

Here’s another handy tip: make a choice and stick to it.

Intel XDK is a little clumsy (at time of writing) for user-interface building. Hence my preference to use other tools.

That said, Intel XDK has some nice tidy-up features that even eclipses Eclipse. Yeap, I went there.

Beware: it’s very easy to write some code in one tool and write over that very same code in another tool when you’re running when you should be walking.

The tools you use are up to you. I use very high quality, very free tools.

Building Your App

Apart from Apple’s over-engineered requirements hoops (which frigging certificate do I need again???) and the “Windows choice of three packages”, the build process in itself is simple. Go to the Build tab. Upload your code, build your package, download your package.

I don’t know about you. I’m poor. I can test my iOS package. I can’t test my Android or my Windows packages. One day I hope to be able to test on more than one platform. Sorry test guinea pigs (ie. all my customers on Google and Windows devices).

For you, the Developer: the emulator in Intel XDK should be thought of as a guide only. You’ll figure it out. March on. Take no prisoners. This is no time to be frightened by the fear of: “what if it doesn’t work”. Have some faith. Be damned for trying. Don’t be damned for failing.

For Android, you’ll want to build using the “Crosswalk for Android” option. Two words as to why: “flex box”. If you need to know more, check the documentation. Flex box has a way of sneaking into every project (in my limited experience).

What can’t I help you with?

  • Apple’s way of doing things is heavily over-engineered. You have to create your own certificate using a convoluted method. Everyone gets it wrong. At least once. Persevere.
  • Apple’s review period is long. About 7 days (that’s not a misprint, it takes days!). It’s a nail-biting first experience. What if the app is rejected? Will I know what to do if it is rejected? Why is it taking so long? Does that review status mean that Apple is going to review it or that I’m supposed to? Aaaargh! Is it ready yet? What’s going on? Oh, and the sleepless nights. And the minute-by-minute checking of the email. That never comes.
  • Google takes a few hours. The same App will be reviewed and deployed within 24 hours. Maybe a little longer. Less than 48. That said, if you write a monster complicated app, maybe longer.
  • Windows takes a few hours. And then about a day to become available for download in the Windows store. But, you’ll have no customers. So it’s a moot point. Build for Windows Phones anyway. It’ll round out your resumé.

What Am I Doing Now?

I’m building another App.

Useful Links


Intel XDK

Intel XDK Docs

Intel XDK Forum