|
|
|
|
|
|
by charlesTwenty
1068 days ago
|
|
|
Thank you for the feedback. What you said resonates with me a lot. Standardized APIs: While we are designing Twenty, we have in mind to provide three APIs: a GraphQL API (headless), a Front-end React API and a NodeJS API that engineers could use to build their own plugins. We imagine that you could build your plugins in your own repository using SDKs maintained by Twenty. Then on your twenty instance you would be able to install a plugin from your custom repository or a shared marketplace (this would maybe imply a vetting process)
There are many challenges around that, especially in resources monitoring and security given we are going into the multitenant architecture API that don't assume custom business logic:
Here, we might have a slightly different opinion: we think that Twenty should come by default with a quite opinionated behavior. We will likely introduce a rich library of standards objects and fields that would have pre-defined behaviors. However, we would also enable the users to create custom objects and custom fields if they need that can be customized in whatever makes sense for their business. So: Standard objects/fields + Custom object/fields. We don't know yet if they share the exact same API |
|
|
It's perfectly fine to have opinionated behavior as long as there's a way to override it. Companies which don't have 15 years of tech debt have to start from somewhere, and it's nice to have good defaults.