We have added an exciting new feature: if you were previously using Trello, you can import that data, completely, into Kerika!
We have been testing this as a convenience feature and based upon positive feedback we have expanded this for everyone.
New users will be offered this as an option when they set up their Kerika accounts:
All users will have this option whenever they want to create a new Kerika board:
We built this feature because we have heard from many people switched over from Trello and really liked Kerika’s user experience, features, and support. In the past they had to manually recreate their work inside Trello; now that’s all automated!
Everything is handled nicely: your Trello cards, lists, people, task details, etc. come over. Once you are done, a single click can then send out invitations to all your old Trello colleagues to join you in Kerika.
An Account Owners can now designate other members of their Account Team to be Account Admins, which will allow these people to also manage the subscriptions and membership of that account. This can help where the actual ownership of the Kerika account is someone from outside the user community, like a purchasing department.
Managing Account Admins can be done from the Manage Account screen, by the Account Owner:
Once you are in the Manage Users screen, select one of the Team Members on the account:
In the Team Member details dialog, select TAKE ACTION:
And select Make this user an Account Admin:
There’s a confirmation step, since Account Admins have tremendous power over the Account:
And your new Account Admin is set up:
An Account Admin can set up other Team Members from that Account to also be Account Admins.
Account Admins have a lot of power over the Account; they can:
- Access any board
- Add people to, or remove from, any board
- Change people’s roles on any board
- Add people to the Account and buy subscriptions
- Change the subscription plan
So be careful who you add as an Account Admin!
We have a lot of different website pages, but we still need a better understanding of how people actually view them, and which parts seem to be most important to our users.
Google Analytics provides some of that information, but not enough, and it looks like Microsoft Clarity will help us optimize our website content.
Let us know if you have any questions or concerns.
With the new version you will notice that Kerika has become much faster on the desktop than previously: now any board, regardless of size, should load in under 3 seconds if you have a fast Internet connection.
With the old version this wasn’t true: the time to load a board was proportional to the number of cards (tasks) that were on the board, and while most users didn’t notice any lag, people who were using Kerika at a large scale, e.g. with boards of a thousand cards, would have to wait a while for the largest board to full open.
With our old code, every board was loaded sequentially column by column, starting with the leftmost column, and within each column every card was loaded before another column’s loading started. This approach didn’t scale well, and the flaw of this approach became all to obvious when we built our mobile apps, which used a “lazy loading” approach.
To fix this, we rewrote the desktop app from scratch, an effort that took nearly nine months for our small team to complete, from design, implementation, testing and endless refinement.
With lazy loading the system prioritizes which cards to load, rather than trying to load all of them one by one. If your board has 15 columns, for example, not all of these can be viewed at the same time: most displays will show just 5-6 columns at a time. Kerika keeps track of which part of the board you were last viewing, and then intelligently loads the board from that point of view.
All the other columns are loaded only as the system senses you are going to need them: as you scroll to the left or right, for example, the system automatically (and quickly) fetches more columns into view. If the system does this fast enough, the user never realizes that her entire board wasn’t loaded at the very beginning, because no matter where she is looking, everything she needs is always in view.
We took a similar approach to loading columns with a lot of cards (tasks). Instead of loading all the cards that exist within a column — and these can number hundreds, for large boards — the system considers how many can be displayed at a time given the user’s particular device: laptop, desktop, tablet, or phone.
Having calculated how much of a column can be actually viewed by a user, the system loads just those many — and a few more in anticipation of the user scrolling her view of a column. As the user continues scrolling down a column, the system races to fetch more cards from the server so there’s never a gap in the user’s view.
But lazy loading alone wasn’t enough, we also had to deal with the speed at which a browser can display a bunch of cards. This speed varies by browser type, as well as device. A low-powered computer, perhaps running an older browser, can’t render cards as fast as we need for the user to have a true real-time experience.
We use Log4J mostly in our development environment, where we write new code; less so in our test environment, where we use our new code ourselves to make sure it works well (a philosophy known as “eating your own dogfood”); and only rarely on our production environment, which is where our users are.
That reflects the normal approach to debugging: you want to find problems well before they reach users.
And we are aware of the guidance from the United States Cybersecurity and Infrastructure Agency about a recently discovered critical vulnerability in the Log4J software. Naturally we acted promptly upon getting that news and updated our software on all our environments!
We have added tablet support for iOS and Android devices, as you can see:
The tablet experience is like that of the desktop, not the phone.
For the phone app we had to redesign a lot of the user interface to accommodate the limited screen space, but with most tablets today there is enough screen resolution to support the more extensive desktop experience.
We have made it easy for you to preview documents that are attached to cards or whiteboards, regardless of how you sign up for Kerika.
You could have signed up using a Google ID, a Box ID, or just your email: it doesn’t matter how you signed up, nor how other members of your team signed up.
Previewing documents just became really easy.
When you click on a link to a Kerika board or card in an email, that link will now automatically open in the Kerika Mobile App instead of opening in a browser tab.
This makes it a lot easier to respond to emails sent when your team members do chat on boards that concerns you: you can either do a quick reply as email itself, or, if you need more context, click on the link to open the card inside the Kerika app and see all it’s details before deciding upon your reply.
Our development team is based in India, and starting about 4 weeks ago we started getting hit hard by Covid-19. Eventually everyone in our India team was affected one way or another, either by falling sick themselves or having a spouse or child fall sick.
Thankfully that’s over now. We are back up to speed.