3 ms·
I like the initiative. The main concern is whether to stick to "proprietary" design framework, either it's Jetbrains Ring UI, Atlaskit, and so on. There are _
by RomanPushkin 4y ago
I like the initiative.
The main concern is whether to stick to "proprietary" design framework, either it's Jetbrains Ring UI, Atlaskit, and so on.
There are _lots_ of community-driven alternatives, and it feels much safer to pick something that doesn't belong to a corp.
I'm willing to hear pros for choosing such UI framework.
- MarathonSeeker 4y agoThe main reason you would want to pick such a proprietary library is to achieve a homogeneous look and feel (often behavioral UX as well) when your app must work within another product - this product/organization is usually the one that also provides the library in question, and more often than not, uses the same design system if not the library itself. We built https://github.com/freshworks/crayons https://github.com/freshworks/crayons for the same reason - apps published to the Freshworks Marketplace can be built using Crayons. We also ended up building our own user facing SaaS applications using Crayons.