The app got some nice updates in the last sprint! First of all, there's dark mode now ☀️/🌙


And addition to that, headers, text color, and text highlighting are now fully supported in the notes editor 🎨


Also, camera and import from photo library can now be used when editing notes 📸



Zoom has some shortcomings, e.g. not being able to start a call when the room owner is on a vacation, or unpaid users having to restart the meeting every 40 minutes. Therefore, we decided to try moving to Jitsi. Since Jitsi is an open-source solution, we decided to self-host our own Jitsi server for calls within the company. The service is up and running now, although it is intended only for meetings hosted by ourselves at the moment. If you'll see some screenshots of discussions by us held in Jitsi now, don't be surprised :)

Schema improvements for dynamic use

In the last weeks, we noticed some downsides to our current data types / Schema design. While being practical on a small scale, it started to clog once we had various integrators, frontends and backends working together. We realized we need a redesign rather sooner than later. To do that properly, we started with analyzing our requirements. A Schema should:

  • Guide the user on inserting data that can work well together with other integrators, e.g. by catching typos or common mistakes early in the process;
  • Be flexible enough to allow the user doing what they want, e.g. insertion of new types that were not previously defined in the Schema;
  • Easily inspectible, e.g. a user or integrator developer should be able to see where each change comes from;
  • Should allow for "upgrading", including a situation where the user has multiple front-ends that need to work on the same data

We created a plan that covers most of our requirements, and we are confident that we will meet the other ones too, while implementing the design in the coming weeks. We will start documenting the new Schema design, but the quick take-aways are that 1) for integrators the picture does not change much, and 2) front-ends will store data dynamically and in a generic format. We'll keep you posted on our progress!


We strive to make development of integrators as easy as possible, and at the same time we aim for deployment to be as reliable and reproducible as possible. During this sprint, we discussed the impact of having a multi-container setup on our hosting infrastructure. A multi-container setup is an integrator that needs multiple services to run simultaneously, e.g. a Synapse server and an importer that communicate with eachother. We plan to document and implement it during our first integration with Synapse, which should work well with the already existing API (though some parts will enjoy polishing).


One of the things we've been working on in the last weeks, is an update to our consumer oriented website

For those more interested in the technical specifics, the central place is still ;-)

Community manager

Ending our search for a community manager, we are excited to welcome Karl Hütt to our team! We already did some work together with Karl in the past, which was a very positive experience, so we are happy he decided to join us.

Some of the most notable responsbilities of the community manager are:

  • Bringing the voice of the community to us;
  • Creating a positive culture in the community's public places;
  • Improving our onboarding experience for new team members.

Naturally, it's a collective effort to ensure we are in touch with our community, as we believe this is essential to create a product that really serves the user.