Hope the Fibery team has recovered from what seems to have been a busy January.
Disclaimer: this idea/thought is a bit out there!
I was wondering if third-party extensions or plugins were ever a consideration. I know this is very tricky since this means running someone else’s code on your platform and machines, but I am wondering if anyone is thinking of how to make it work in this kind of an environment. I have been suggesting ideas from the sidelines, but I know many are these are not the development team’s priorities (and rightly so). An extension ecosystem might allow some outside programmers to fill in the gaps that the core product doesn’t currently address.
My thought was an extension library/store that is vetted by Fibery that could be installed as needed by users. It would be great if it wasn’t monetized since I think that complicates things and I hope that having an amazing platform would be incentive enough for most contributors.
Apologies for the crazy idea, but I thought I should ask anyway.
@mdubakov do you mean an app store for applications/templates like the one that is currently curated by Fibery staff (i.e. CRM, GIST Planning, etc.)?
What I was thinking of was a library of plugins/extensions that add new field types, views, etc. to the platform. Will that be a possibility at some point?
@mdubakov thanks for that extra insight. I would only ask that you guys take special care around the quality of this stuff. One of the reasons I am here with Fibery is most of the apps in the Atlassian Marketplace I tried were low quality - full of bugs, poor documentation, had bad UI and UX when using within Jira. I could never get much extra out of them to customize my Jira Instance, and ultimately that led me to leave Jira.
Here is the scenario, I am building out channels in certain industries that I am bringing Fibery to. These industries, have different needs then Fibery is currently not capable of supporting.
Some areas Fibery might eventually enhance, some areas, Fibery might never get to or prioritize. As such what I would like to do build custom development able to be resold inside the Fibery Eco System, which Fibery would taking a commission on.
Off the top of my head, here are a few areas that I anticipate developing around:
Custom Views - For example Fibery Forms are limited. However, enhanced forms might be an add on that others pay for
Custom automation actions - these might be used in connection with integrations, or as stand alone options.
Non editable formula fields that tie into custom development and automations. This is needed for data integrity.
Custom Widgets on Dashboards
Other Reporting Widgets - Fibery Reporting is great, but there are other chart types that aren’t supported
There are other tools I would like to be able to check for licensing, For example, Fibery has a product clipper, But it doesn’t do images. If we were to build another one that could clip images, we would want to check licensing and be an add on inside the Fibery subscription.
There are other areas that get more invasive with the UI and architecture. For example, enhancing the rules engine. These areas are too important to not have conversations with the Fibery Dev team prior to starting.