simple-media-converter VS react-chatbotify

Simple Media Converter is a Telegram bot created for easy media conversions in my university days when lessons and submissions were mostly online due to covid. Initially, the bot was deployed via Screen and I had to do manual deployments after every code change. When I moved to Docker, I automated the entire deployment flow with GitHub Actions to simplify this process. You can find the workflow files on the project repository.

For those who are interested to take things further, you may also wish to extend the functionalities of the bot into a project. In case you need some inspirations, I've open-sourced a handful of Telegram bots such as TeleQR, Simple Media Converter and Simple Transcriptions.

Anddddd it's a wrap! In this tutorial, we've gone through detailed steps of setting up our GitHub Actions workflows to automate the deployment of a Telegram bot. If you are keen, you can go further and explore the adding of a test workflow as well as using matrix strategy to run against multiple versions. For reference, the workflows for a chatbot project of mine can be found here.

React ChatBotify is a React library that allows users to effortlessly integrate a highly customizable chatbot to their websites. Available on npm, it is slowly gaining adoption and there is an increasing need to ensure its reliability and consistency for users. While the previous project had a single build workflow, this project contains 3 separate workflows for lint, test and build.

I hope this article along with the code snippets I shared above will be helpful to anyone out there grappling with similar issues. While I've shared my journey in tackling the pesky problem of media controls showing up on mobile devices' notification trays, I'm still open to ideas, suggestions and feedback - especially if you know a better solution!