We hope everyone had a productive March and a energising easter vacation, at least we did! During the short month of march we released a handful of improvements, but maybe more importantly the team behind Skyra grew from 2 people to now 4! We have had multiple releases as detailed below, all were a result of specific customer requests.

Alexander joins the team as a talented fullstack developer who (for now) shelved his master thesis in computer science in order to join Skyra. Just one month into his tenure he have contributed several improvements that are already live and in your hands. Alexander lives in Bergen and works out of Startuplab Bergen with Raymond.

Tor brings 15 years of experience doing UX for startups, agencies and government across Norway, Germany and Ireland. Tor joined as our UX lead just a week before easter but his fingerprints are already on some of the improvements released, and you should notice his presence over the coming months by an increased level of polish across Skyra. Tor lives just outside Oslo and is working with Jon day to day.

Finally we have a generic multi select card type. A multi select card is used to “cast vote” and remain specific for only one survey.

You can set min/max items to toggle, you can sort them, randomise them and pin specific items to specific positions. The multi select card is also the first card to introduce keyboard shortcuts for selection, something we expect to add to segment and task cards in the future as well.

Multi select vs segment card

The multi select card is different from the segment card, despite their similarity. Where segments are cross-cutting and shared between surveys, multi-select is specific for only one survey. A segment card is also single select, while a multi select card, as the name suggests, allows multiple selections.

Segment cards finally supports “pin to position. It is useful to pin one answer option, such as “other” to the bottom of the list while keeping the rest randomized. This was quite overdue!

Creating top task surveys with 50-100 tasks, or more, across two levels was a tedious process, so we improved it to make it clearer and faster.

Now you can easily add all tasks that share a parent task with one click. We also made customising and pinning tasks on a task card clearer and more obvious.

Also, using “Select all” will not include hidden tasks no more.

Previously, the results from a likert scale questions has a limited view in the dashboard. You can now see a more detailed report. You can also edit the name and description for your likert scale. This view is a release-early view and it will see further improvements in the start of April.

You can view results from a likert scale under Segments. Go to Segments > choose your likert scale.

We are slowly exploring how to connect ux-metrics for specific pages. Now you get a list of your top 10 pages with the most responses and their completion rates (if you use that) on the dashboard. This is a step towards reporting ux-metrics for pages, not just tasks. It helps you answer questions such as: Where do most users respons to the survey? How is our top 10 pages performing.

You can view your top urls under Dashboard.

Now you can easily export all survey responses to a CSV file. This is how: Go to Surveys >Click the three dots in the survey list and export.

On the night of 13th March we deployed a big revamp of our infrastructure, including encryption of data at rest. We our encryption is AES-XTS 256 bits.

Why wasn’t this done earlier? As a startup company we’ve followed the path of first building a minimum viable product, having just in time delivery and iterating based on customer needs. Our first year focused on high speed and pilot customers, so encryption at rest and infrastructure upgrades was postponed.

We try to remain honest and transparent, and the fact is that with our focus on GDPR/privacy meant that we were unable to find an acceptable managed database solution for our constraints. However, we are happy to announce this major upgrade now.

A completely new feature, traits, was silently released. The background for this was a customer doing ab-testing. They filter their survey results based on which (a or b) page the responded saw.

Traits, or what you might know as “custom dimensions” from Google Analytics, or “custom properties” in some other analytics tools, let you add known information about a respondent in your integration code.

Its not something everyone needs, but if you do you already know 😃

Some example use cases could be:

Once you have some traits with trait values you can use the global filters in the menu to filter by that trait.

In order to use traits you first have to define them the under Settings

Once you have a trait User id defined you can send them in the snippet where you start Skyra, like this:

We've squashed some bugs to improve the overall performance and stability. Here are a few important ones: