Table editor collaboration request

Dear Confluence Cloud Team,

On behalf of the TechUp team I am reaching out to you asking for a collaboration request with your team around one of our Confluence apps Smart Tables currently on the Marketplace.
We believe that by building flawless and user-friendly experiences, we provide our customers the means to increase their teams' efficiency and engagement towards the Atlassian tools.

Why Smart tables?
Confluence users are eager to leverage native Confluence page editor's capabilities in order to perform their day to day tasks. Thus, building out tables in a few clicks by enriching the native confluence table using powerful operations and functions in the page editor experience is the main use case we addressed thanks to Smart tables.
As opposed to the other app's design and data scheme, we decided to lay the emphasis on a "Confluence page editor" experience avoiding the use of macros, or importing an excel sheet in Confluence bringing therefore to the end-user the closest experience to the native confluence comfort level they are used to and more importantly an outstanding User experience by reducing the number of possible clicks to achieve their goal.
Smart tables has today more that 700 active instances on server in less of two years from the product launch and our customers shared the same feedbacks: "ease of use" , "user friendliness"....

[check here|https://marketplace-cdn.atlassian.com/files/images/aaa9eafa-3d02-4b8d-af27-96c8c580664c.png]

New confluence editing experience:
As a Marketplace vendor and fans of Atlassian toolset we totally support the company's growth shift to cloud-based services and products and are working towards this common objective.

The new editor of confluence pages, currently available in the Atlassian cloud relies on a React implementation of ProseMirror (the @atlaskit/editor). This new implementation does not allow us to interact with the editor instance in order for example to modify the content of cell when is formula is set.
That is a probably is a React / Component pattern which forces the state of the Editor component to be managed by the internal renderer. That is why, we would hope that you guys expose an Access point / bridge allowing extensions to be made on the new editor.

We are available to go through the technical details together maybe through a conference or any other format that is convenient for you.
We are looking forward to working together in order to support our customers with the new editor experience in the Atlassian cloud.

Cheers,