Re:Launch HN: Twenty.com (YC S23) – Open-source CRM
by jve on Thursday July 20, 2023 @12:50PM
(#36803264)
As for frontend - you could build reusable components and make possible to use them/build upon them. Microsoft made FluentUI to make consistent and usable components across product line. However each product customizes styling slightly and builds their own components that are not opened up... which is pity.
If you ever plan having different things, better keep them in mind at the beginning - bolting them in afterwards may be cumbersome.
Re:Launch HN: Twenty.com (YC S23) – Open-source CRM
by iFelix on Thursday July 20, 2023 @01:48PM
(#36804067)
Yes! We'll probably need to isolate some of the existing components and commit on their api stability so people know they can reuse them safely
Re:Launch HN: Twenty.com (YC S23) – Open-source CRM
by Kibae on Thursday July 20, 2023 @02:07PM
(#36804339)
I recently started building something similar to this in Electron where users can create their own (React) components and extend the application. I used `live-plugin-manager`[1] to handle installing these components, but when two components use different versions of the same package, they can't simultaneously be used.
Have you been able to figure out a way for users to create their own plugins/components?
The key challenges I foresee are:
- Backend: offer extensibility that is powerful while secure in our multi-tenant cloud service.
- Frontend: ensure that custom plugins don't feel limiting while not disrupting the unified design, as the overall software appearance, not just the core, shapes the end-users' brand perception/experience