Thoughts on the "Fibery approach to integrations" article?

@B_Sp Thank you for the insightful reply. Let me shed some light on Fibery future. I’m going to write a longread about our vision soon, but at least some highlights so far:

  1. We have to find and secure good niche first. On our opinion this is a product development company from 10 to 100 people, and we put all the effort into this direction at this very moment.

  2. But we are trying to not hardcode things, but analyze cases deeply and build framework solutions. Like we needed bi-directional links to connect feedback and work, but people use them for all kind of connections. Or we needed Intercom and GitHub integration. We did not hardcode them quickly, but created a concept and framework that will work for other integrations as well. So we are improving Fibery as a platform. In general we are reluctant to hardcode things for specific cases.

  3. When product niche will be secured (or when thus experiment will fail, we are not sure yet), we will try another niches, like consultants with unique processes, etc. We have some in our backpack.

  4. You are absolutely right when speaking about lack of important things like better notifications and activity history. Indeed they are requested by many people, but here is the aggregated feedback from all accounts thus far. Note that Notifications are not even in top 20, so we are listening and focusing on the most frequent and important areas. Right now these are Permissions & Sharing, and Integrations.

and here are the most requested features/ideas/things. Note that most of the top things are in progress.

  1. Our ultimate goal is to augment teams and companies intelligence and not stuck in Product Companies niche, but we have to start from something from a strategic perspective.

I hope Fibery will work well for all of you, but we need more time to make it great.

7 Likes