Ora as a snap: ensuring users are benefiting from the latest version

by Sarah Dickinson on 24 April 2018

Ora is a user-friendly task management service with integrated time-tracking, reports, list view, git integrations and many other features. Often referred to by users as ‘the sweet spot between Trello and Jira’, Ora provides almost a complete match of Jira’s feature set but in a new and more accessible way.

Last month, Ora launched their application as a snap and thereby broadening out their reach across the Linux user base. We spoke to Nikolay Mihaylov, co-founder at Ora, who told us more about their reasons to publish a snap and how it will help Ora move forward.

Like many software vendors, Ora discovered snaps in their quest to simplify shipping their application to several Linux distributions while removing the troubles of maintaining multiple packages. For Ora, this was their biggest reason for adopting snaps and what Nikolay calls a ‘game changer’. In addition, Nikolay comments “we ship updates every week and the automatic updates are significant for us. It is nice for us to see in the statistics how each new version reaches almost all users in a day or two. That is the biggest benefit for our users – they are using the latest version of Ora anytime.”

Although early days, how has the snap been received so far? “Our snap is still young, but we can already see some results. Every day the number of the active users increases, and there are a lot of registrations coming directly from the snap” Nikolay explains. Ora’s snap is available in the store and although that wasn’t originally a factor in their decision to adopt snaps, it has led to the increased discoverability in addition to their own website. Looking forward, Nikolay suggests some improvements to the store and specifically categorisation of snaps to aid discoverability.

In terms of the internal benefits that Ora has benefited from, Nikolay can see the level of customer support already decreasing thanks to the automatic updates as their users aren’t stuck on previous versions. Plus the inevitable reduction in development time of building one snap compared to packaging for 3+ Linux distros as per their previous ways.

“Just do it” would be Nikolay’s advice for anyone thinking of building their first snap. “Automatic updates every day, only one snap to maintain. What else do you need?” adds Nikolay plus stating building a snap was easier than it was for the Mac store.

Newsletter Signup

Related posts

Popular snaps per distro

From a distance, Linux is one big, confusing ball of passionate users and hardcore technical jargon. But as you zoom in, you can start seeing patterns – and differences. Indeed, the individual and vastly varied choice of a favorite distribution has played a major part in shaping the community conversation in the Linux space. But […]

Management of snaps in a controlled, enterprise environment

Few enterprises want all their computing devices to be fully exposed to the internet. In an environment of ever-growing security threats, isolating internal networks from the wider internet is not simply best practice, but borderline essential. However, with all the benefits that restricted networks provide, it can pose challenges for ent […]

A technical comparison between snaps and debs

How are snaps different from debs? This is a common question that comes up in technical discussions in the Linux community, especially among developers and users who have just embarked on their snap journey and are interested in learning more details. Indeed, the introduction of self-contained application format likes snaps has created a […]