TLDR (By Chat GPT):
I’m looking for advice about using the Monday API to run software subscriptions. Its unconventional data structure and recent breaking changes raise concerns about long-term stability and frequent updates. While Monday’s front-end would benefit our Ops and Sales teams, we worry about the service’s pace of change. We aim to avoid recurring disruptions to our licensing feature. Guidance on the API’s reliability and its potential impact on our operations would be invaluable.
I’m considering using the Monday API to manage software subscriptions for Applications that my company develops and sells access to. I write seeking strategic advice more than technical instructions. Ideally, I’d also like to connect with a Monday product owner who’s interested in this use case, willing to vet it, and available for support or questions.
I’m a Director of Product and Technology at a small VR Training startup. While I’m relatively new to Monday, our team relies on it for various project management and operational tasks. Here’s a snap shot of my situation: we maintain four VR applications (Android / Unity /C#) and we own or manage around two hundred VR headsets worldwide, using an MDM system for access control. To accelerate our growth, we’re looking to implement a licensing system into our apps. Currently, we rely solely on the MDM for access management.
The license feature will work as follows: on first launch each app will report a unique hardware identifier, user-defined hardware name, and trial start date to a central repository. The repository will notify our teams, and our sales team will set appropriate expiration dates for each piece of hardware. Subsequent online launches will save the updated license locally. The sales team will update the repository are licenses get extended.
Initially, I considered running my own LAMP stack, then started researching CRUD services, looking for a stable cost-effective, user-friendly, back-end. Finally, I discovered that Monday might have the solutions I need. I’ve already created a fully functional prototype using the 2023-10 API through the API playground.
However, I’ve found the data structure for accessing values from specific items and columns to be a bit unusual. To retrieve the necessary data, I’m using expressions like “items,” assuming that the order of the table structure won’t change. I’ve also seen the notices about recent breaking changes. Additionally, support for the 2023-10 version, which was in preview just a few weeks ago, is set to end on April 1, 2024. And when I searched for API reviews, I found mostly complaints from a few years ago.
So, my question is: Will the Monday API become a recurring challenge for me? Will I need to constantly rewrite my licensing feature every six months? While the front-end provided by Monday would greatly benefit my Operations and Sales teams and the API seems to have good uptime, I’m concerned about its stability. We’re a small team. The functioning of this feature is crucial to ensure our users aren’t locked out of their paid applications, but I want to avoid frequent updates just to keep it running due to rapid changes from the service provider.
Your insights and advice on this matter would be greatly appreciated.