It can use existing C libraries, and embed those libraries into the binary and therefore the snaps.It is designed to create self-contained binaries that are easy to deploy and update.Go seems perfectly suited to writing software in a snappy world. None the less, I’m experiencing intense NRE with Go. Snappy is totally polyamorous when it comes to languages and libraries, of course. First with Python on the desktop, and then with QML on the phone. I’ve been through two other big linguistic love affairs so far with Ubuntu app writing. GoĪ word about my language of choice for snappy.

I’ll leave it others to cover how to convert your existing software to snaps. Of course, what I like to do is write new apps, so that’s what this post is about. Therefore, there was a lot of writing new apps for the phone, whereas for snappy, there are new apps, but also there is making existing app available as snaps. Ubuntu phones are somewhat more limited in terms of the software that they can run. Namely, in snappy Ubuntu Core, you can make any existing software run as a snap so long as you modify it to run in snappy’s application isolation model. So, in this blog, I will provide an introduction to the developer workflow that I am currently using to create my own programs for devices running snappy Ubuntu Core.īefore I do, please note that there is one big difference between Ubuntu on the phone and snappy. If you are like me and have a Beagle Bone and a Raspberry Pi 2 and several old netbooks and laptops lying around, than snappy is quite the playground. Like the Ubuntu phone two years ago, snappy is a bit of a green field in terms of IoT related apps. If you are anything like me, you love to write apps for Ubuntu.

Snappy app video