SystemTek just published an article on the top free project management tools, and we are pleased to note that Kerika ranks #1 on the list, ahead of Trello, Asana, Clickup and Todoist.
The article notes that Kerika comes with:
Mirror Review features Kerika in an article on lesson planning! From the article:
Choosing the right lesson planner is important as it directly impacts your ability to organize teaching materials efficiently and save time in the long run. Kanban tools have gained popularity among teachers due to their visual and flexible nature. There are many tools available in the market like Clickup and Trello. But if you’re looking for a cost-effective tool that caters specifically to educators, Kerika is the standout choice.
An article on the Top 10 Challenges to Effective Time Management that features Kerika. The Top 10 Challenges are:
The article goes on to say
Task management tools are your allies in the battle for effective time management. They come in various shapes and sizes, each offering unique features to help you stay organized and on top of your tasks. One such tool is Kerika, which offers flexibility by working seamlessly on all browsers and platforms, making it a versatile choice for individuals managing tasks across multiple devices.
“Kerika just got better…” is a message you are seeing almost daily, and that’s thanks to the massive 2-year effort that overhauled our old backend and made it much easier to push out changes.
We are now rolling out bug fixes and feature improvements on a daily basis, using our modern architecture. Previously we had to batch these up and do large upgrades; now we can push out the smallest changes, when we feel they are ready to go.
Under the old architecture taking the servers down for maintenance was a painful necessity; now changes can be deployed without any downtime.
All changes still go through extensive internal testing, and new features go through a lot of usability testing in particular, before anything gets pushed out.
An effort that took 2 years finally completed yesterday when we updated the Kerika app.
This massive project involved rewriting everything on the back-end of Kerika in order to modernize the architecture and set up us for a more rapid development of end-user functionality, as well as making it easier to release new versions in the future using Docker container.
Our old backend was not well designed: everything ran as a single monolithic server. Over the years we moved slowly away from that, by building new features as microservices, and while that helped a little, it wasn’t enough.
We had reached a point where it was taking exponentially more time to build new features, and we were facing operational risk as well because the old backend was poorly understood and document.
A complete rewrite was necessary, and we bit the bullet on that a couple of years ago. There was significant cost and complexity but our great team powered through all the challenges, particularly when it came to transitioning our main database away from MySQL (hosted as RDS, by Amazon) to a NoSQL model using Google’s Firestore service.
Now that we are done we can start delivering more functionality, starting with support for non-English languages.
Stay tuned for our first non-English language, which will be Hindi, to be offered in a couple of weeks.
Once again Kerika is featured in an article, this time on the 6 Project Management Techniques For Work-Life Balance at Namaste UI.
The techniques include:
To quote from the article:
Tools like Kerika can help you see and analyze how your projects are going, so you can find patterns, things that slow you down, and ways to get better.
Windows Techno recently featured Kerika an article on the 8 Steps for Planning an Email Marketing Campaign. The steps:
We had always treated our customers data as confidential, and have never shared that with anyone else. At the suggestion of one of our users, we have updated our Terms of Use to make this a written commitment.
We have added Section VI to our Terms of Use:
“Confidential Information” means information identified by you as confidential at the time of disclosure or that a reasonable person would consider confidential due to its nature and any confidential, proprietary, or privileged information disclosed while creating or modifying the Kerika boards.
Kerika shall preserve the confidentiality of your Confidential Information and treat such Confidential Information with at least the same degree of care that Kerika uses to protect its own Confidential Information, but not less than a reasonable standard of care.
Kerika will use your Confidential Information only to exercise its rights and perform obligations under these Terms. Confidential Information will be disclosed only to those employees of Kerika with a need to know such information in connection with Kerika’s use of the Confidential Information in accordance with these Terms.
Kerika shall not be liable to you for the release of Confidential Information if such information is divulged pursuant to any legal proceeding or otherwise required by law, provided that, to the extent legally permissible, Kerika will notify you promptly of such required disclosure. Kerika agrees to promptly notify you of any unauthorized access to or disclosure of the Confidential Information.”
We have been lax in updating this blog, sorry, but not lax at all in working on improving Kerika, especially for mobile browser users. We are also getting close to releasing our mobile app, which will contain the same functionality as you get today when you access Kerika on a phone, but it will be packaged as a traditional-looking app for folks that want an icon on their desktop.
Here’s a short list of things that have been improved and added in the past few months:
There’s more of the desktop functionality now available on phones as well, including:
We have started purging defunct accounts: users whose email addresses don’t seem to be valid anymore.
We are not doing this in a hurry, but instead are trying to be methodological about it: if someone’s email bounces, and we see they haven’t logged in during the past 6 months, we are going to assume this user doesn’t exist within that organization anymore, i.e. has probably left the company where they were previously working.
(The 6 months of no-activity helps us avoid temporary email problems, such as when someone’s email server is down for a day.)
Also getting purged are new users with invalid emails: this can happen when an existing user mistypes a coworker’s email address at the time they invite people to join their teams.
An account is created at the time someone initiates the invitation, but if we find the email associated with that account is bouncing, we will delete that account.