![]() Take the logic from this application and re-architect it as a Google Workspace add-on for Calendar.It had a basic web app for the configuration. It ran on an EC2 instance and held the tokens for the OAuth connection to a calendar and the user preferences in a MongoDB database. I built a standalone server-side Node.js application that solves my problem a number of years back. The only way I can extend my calendar’s behaviour is by using a legitimate, approved add-on that is published in the Google Workspace marketplace. Organisations are getting more and more cautious with the privacy of user data, and my employer is no exception. Prefers the ideal time, but will slot in a different time if necessary, respecting the earliest and latest possible times.Looks ahead a fixed period of time (e.g.Takes an ideal time, a latest possible time, and an earliest possible time.I find this a problem though, because it reduces flexibility and makes it hard to coordinate with colleagues’ and friends’ schedules. Some people deal with this by setting a fixed time for lunch every day. ![]() I find it easy to turn up on a Monday only to discover that thanks to other people requesting meetings, I have no time aside for lunch in the week ahead. The business problemīusy people struggle to make time at work for regular needs like eating lunch, going to the gym, or just taking time to reflect. Most of the content in the marketplace is integrations with popular third-party applications like CRMs and other productivity tools, but there are purpose-built add-ons as well. Google Workplace has a marketplace where users can find and install add-ons that extend functionality of all of the applications. We also use it in my day job as our core office productivity suite. I use Workspace on my own domain for email, chat, and calendar for my family. ![]() It also includes Calendar, Google Drive and the Google Docs sub-suite. Gmail is the part of the suite most people are familiar with. Google Workspace is the latest name for the product formerly known as GSuite, formerly known as Google Apps. My add-on published in the marketplace Google Workspace Below is the production listing for JIT Time. In this story I’ll explain how I felt the fear and did it anyway □. For a solo developer it’s a no-brainer: the platform takes care of the requirements above, and when the platform has a marketplace, there’s even a ready to go distribution channel to take it to market! The only real reason I’ve resisted it so far is fear of the slog of platform approval processes and required collateral. I’ve long been interested in using one of the big office productivity platforms to build an embedded add-on. I’m not a good UI designer or front end engineer (design systems are great).I don’t have time for maintenance activities (no patching servers, automated scale-up).I don’t have a lot of time available for learning or building (no steep learning curves without substantial time-savings).I only want to pay for what I use (scale-to-zero).The technology I choose has to solve these problems: I’ve been assembling a tool-kit to quickly build against architectural patterns that I find keep coming up in tiny apps. I work four days a week in a “real job” and I spend about a day a week solving problems that interest me with tiny software applications. Building a Google Calendar add-on and publishing it in the Workspace marketplace
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |