The First 3 Parts of a Calendar Tech Stack

You can think of the backend calendars as the engines of the calendar stack. It is the most common type of app you are probably already using if you use any form of digital calendar system. Because there are more than one calendar systems out there there is no reason you are limited to just one, and in fact, you may have no other choice but to use different ones, in particular if you are sharing calendars with other people.

2. Calendar Client

A client is what becomes your front end to display all the calendar engines in your backend. Ideally, you should have one that you interact with and use to display your information. Although you may want to have different clients for different purposes, such as some that work better than others for you on different devices.

This is analogous to email clients that can have different email accounts added. You may end up using a single backend calendar as your front-end client and add the other calendars to it. This will depend on your needs and the capabilities of the client you choose. Something more agnostic and purpose-built as a device-first calendar may give you more than a typical calendar app might that also has to support all backend features too.

3. Task Manager

A decent task manager should have the ability to add dates to tasks. This will include things like due dates, but also possibly start and defer dates as well as reviews of tasks.

Tasks by their nature should be intimately linked with calendars and scheduling and a task manager of any kind will either have a built-in calendar you can pull into or the ability to communicate and automate between the task manager and your calendar system.

Read this post and more on my Typeshare Social Blog

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store