A small bug fix we did recently: when you do an Export of data from a Task Board or Scrum Board, you get a notification from Kerika when the export completes: that’s because the export could potentially take a long time, if you had a very large board, i.e. with hundreds of cards on it.
(In practice, most exports take just a few seconds, so the notification comes very quickly after you start the Export.)
The notification comes in two forms:
By email, with a link to open the file containing your exported data.
In your Kerika Inbox, on the top-right of the Kerika application, looking like this:
Export Notification in Kerika Inbox
There was a bug that clicking on the “Dismiss” button on Kerika Inbox didn’t make the notification go away: it would reappear after a page refresh.
Sorry for not having posted in a while; we have been swamped with a new UI design that has consumed all of our time.
The new UI, by the way, is all about making Kerika more accessible, particularly to people who are new to visual collaboration.
Our user feedback had revealed a couple of uncomfortable truths that we needed to address:
Very few users were aware of all the functionality that already exists in Kerika. Which means that we didn’t need to focus so much on building new functions as we did on making sure people understand what Kerika can already do.
Our new users aren’t just new to Kerika; in most cases, they are new to visual collaboration altogether. Even though there has been a proliferation in recent months of all sorts of companies trying to recast old, tired products as exciting new visual collaboration (hello, Smartsheet!), our new users aren’t converting away from our competitors as much as converting away from paper, email, and SharePoint.
This, then, is the goal of our new UI: to make it easier for people to adapt from paper and email to visual collaboration, and to make it easier for all users to exploit all the great functionality that we have already built.
We will have more on this in the coming months, as we get closer to releasing our new user interface, but in the meantime we have queued up a bunch of blog posts to make sure you know about all the other great stuff we have been working.
Yeah, our biggest problem is we don’t tell people what we have already done…
Another great new feature: if you upload a file on any card, canvas or board with the same name as a file that’s already attached to that particular card, canvas or board, Kerika will automatically keep track of these as being different versions of the same file. This makes it even easier to organize all your Kerika project files.
There’s no limit to the number of files you add, nor any limit on the size of these files.
When you add a file, to a card, board or canvas, Kerika automatically uploads that file and shares that with everyone who is part of your board’s team. You don’t have to do anything: Kerika makes sure that all the Team Members have read+write permission, and all the Visitors have read-only permission.
These files are stored in your Google Drive, if you are using Kerika+Google, or in your Box account, if you are using Kerika+Box, or with Kerika if you have signed up directly with an email address.
That’s how Kerika has always worked; what we have added is an automatic versioning feature that checks when you add a new file to see if has the same name, and type, as a file that’s already attached to that particular card, canvas or board.
If the file name and file type match something that you have already added, Kerika automatically treats that new file as a new version of the old file, rather than as a completely different file. This makes it really easy to manage your Kerika project files.
Here’s an example: this card has a file attached to it called “Foo.docx”.
File attached to a card
If a Team Member adds another file to this same card, also called “Foo.docx”, Kerika will treat that new file as a different version of the same Foo.docx, rather than as a completely different file:
Uploading a new version
Accessing these older versions is easy: if your Kerika files are in being stored in your Google Drive, you can get the older versions using the Google Docs File menu:
Google revision history
If your files are being stored in your Box account, you can access the older versions from the menu on the right side of Box’s preview window:
Box version history
If you signed up directly with Kerika, you can access the older versions from within Kerika’s file preview:
File preview
Clicking on the Older versions of this file link on the top right of this preview will give you a list of all the old versions of this file that Kerika has:
Older versions
So, that’s it: simple, easy, automatic tracking of multiple versions of your project files! Brought to you by Kerika, of course.
We quietly released a new feature a couple of weeks ago that we now want to announce to the world: you can have all your Kerika due dates appear automatically on your Mac, Outlook or Google Calendar!
All you have to do is go to https://kerika.com/preferences (or click on the Preferences link that shows up under your photo in the top-right of the Kerika app), and then click on the Start Syncing button on that page:
Calendar syncing
You can sync to your Apple/Mac calendar, your Microsoft Outlook calendar, or your Google Calendar.
Pick your preference, and Kerika will show you detailed instructions on how to start syncing.
Here, for example, are the instructions for syncing to your Apple/Mac calendar:
Apple Mac Calendar syncing instructions
And here are the instructions for syncing to your Microsoft Outlook calendar:
Microsoft Outlook syncing instructions
And, finally, here are the instructions for syncing to your Google calendar:
Google Calendar syncing instructions
You will notice that we have deliberately obfuscated the actual calendar URL for this particular user, in all three images above.
That’s important: your calendar URL is unique and precious — don’t share it with anyone!
As your cards on your Kerika Task Boards and Scrum Boards get new due dates, Kerika will automatically feed these updates to your personal calendar: you don’t need to do anything.
Kerika due dates always appear as “all day” events.
Please note that it’s up to Apple/Microsoft/Google to determine how quickly these updates show up on your calendar.
On your Mac Calendar, for example, you can set the frequency with which these updates appear by doing a right-click with your mouse on the calendar and selecting Get Info:
Mac Calendar Info
And then setting the “Refresh time” for that particular calendar. (On Macs, the fastest that iCloud allows is every 5 minutes.)
For folks who sign up directly with Kerika, we store the user password (in an encrypted form, of course), which means that these users can change their passwords directly from within the Kerika application by going to their My Account page at https://kerika.com/my-account:
Changing password for Google sign up
For people who sign up using their Google or Box IDs, we rely upon Google/Box to manage their passwords: in fact, we never even see anyone’s Google or Box password, even for a second!
So, their My Account page looks a little different, like in this example of a Kerika+Google user:
Thanks to Steven Thompson, a consultant working with some of our users at the City of Kent, for pointing this out to us:
If a card is moved to Done, it preserves all its attachments, of course, but it is a little inconvenient to download these attachments directly from within Kerika itself: you would have to open that file in preview mode, and then download it.
We have simplified that process: now, if you hover over an attachment for a card that’s in Done, a “download” button will appear that will make it easier to download the attachment, without having to preview it first:
A user from Mexico recently wrote to us asking which technologies we currently use for the Kerika software, since he was in the early days of planning his own ERP product and was impressed with the overall speed and responsiveness of Kerika.
The question was hard to answer with a simple email in part because we use several technologies, and because we are in the middle of considering some significant changes for 2016.
So, here’s an overview of the current state, with a future blog post to talk about what we are planning to change in 2016…
Our own server software:
All of our server software is written in Java. That’s has worked well for us:
We have a lot of in-house expertise with Java (and none with PHP, Ruby, etc.).
Java is usually one of the first languages to be supported by other platform companies that decide to publish their APIs.
There is a rich ecosystem of open-source code, well-written blog posts and other knowledge sources that help us get our work done.
Open-source server software:
We use a few, well-established open source technologies on the back-end of Kerika:
We use the CometD protocol to provide real-time updates from the server to the browser client. CometD essentially works like a long-poll method, allowing for real-time updates to be pushed continuously from the server to the client without the client having to make new requests. We could, and probably should, switch over entirely to Web Sockets but there are still older browsers out there that don’t support Web Sockets. Hence, CometD.
We use SOLR for our search engine. SOLR is an implementation of the Lucene search technology pioneered over a decade ago by Doug Cutting who has since gone on to do other great work in the software industry. SOLR is widely used by some very large SaaS services like Salesforce.
We use Jetty for our web servers. Jetty is part of the Apache open-source projects, and is a well-established, robust web server that hasn’t given us any trouble in a long while. :-)
We use open-source OAuth for our direct signup.
We use the Java Spring and JBoss libraries for various features.
We use Log4J for error logging.
We use MySQL for our databases.
Platform Libraries
Given our close integration with Google and Box, we naturally use their Java SDK Libraries for authentication and file management.
We used to use Google Checkout, until Google yanked that service from the market (leaving us high-and-dry and more than a little pissed off…) as well as Google Contacts, until we realized this particular integration was scaring away potential users.
Client Software
All of our browser software is written in HTML5, which means a mix of (mostly) Javascript and (a little) SVG.
(Actually, the SVG is only used for the Whiteboards feature of Kerika. The rest is all Javascript and plain HTML.)
Open-source client software
The Javascript ecosystem is quite rich and well established, so there are a bunch of open source libraries we can make good use of:
JQuery is used a lot. A lot.
More recently, Backbone and Marionette have helped fill in the blanks left by JQuery.
The i18n.js library helps with internationalization, although we haven’t actually offered any language other than English so far, for the user interface.
Log4Javascript helps with error logging and debugging.
Bootstrap is used mainly for our website, to make it responsive on tablets and phones.
What changes in 2016?
Quite a lot, probably, but we haven’t finished doing our re-architecture planning.
For one thing, we are planning to use microservices a lot more to make our overall system architecture less monolithic, and we are also planning to use container technology to make deployments faster.
We might consider switching away from SOLR, which we never really mastered, to another search engine which we have more familiarity with, but haven’t made a decision on that either.
We don’t offer this as a regular service — because it involves some special back-end work that can be a little time-consuming — but we recently helped a bunch of users migrate their accounts over from Kerika+Google to the new version of Kerika that lets you sign up directly with us, and have Kerika store your files instead of linking Kerika to a Box or Google account.
This is the version that you sign up for when you click on the left side of our Sign Up page:
Signing up directly with Kerika
With this option, Kerika stores your files for you using our new integration with the Box Platform.
Migrating away from Kerika+Google to this new platform helps our users save money: they could discontinue their use of premium (paid) Google Apps which they had adopted only to use as a sign-up mechanism for Kerika.
Handling this migration isn’t something we do for everyone, but this is one of our oldest customers. :-)
