Hi there, (full disclosure - i'm an employee of bit, but i'll try as much as possible to give the facts and not advise which tool to use or not use)

Storybook is great for demo-ing your components and rendering their UI - including toggling the various states and sharing the renders with colleagues.

Bit is a tool for creating, managing and distributing components, so does things like dependency resolution and management, shareable tooling, component versioning, hosting, discovery etc. As part of a component's page, there's also a compositions section which looks like storybook - hence the comparison developers often make.

The Composition feature is not as rich as Storybook (at least not yet), so if you need features like knobs, and accessibility testing, then you should keep Storybook for your component rendering. (Compositions do have other differences to storybook - each composition is its own mini-application, so you can essentially build integration tests to other components or applications, as well as set contexts across all compositions, and work on different tech-stacks in the same workspace. But these are probably less relevant to your question)

The two tools can also work very well together, so if you want all the UI features that storybook provides, as well as the component creation and management features of Bit, then the two can be used very nicely in conjunction with each other.

Hope that helps!

We're using Bit by our own.

You can develop UI components in isolation for Angular, test it, document it and deploy it also as standalone app. (Check out Bit Aspects https://bit.dev/aspects)

e.g. a Button: https://bit.cloud/myliang/fish-ui/button You see there the code for different frameworks like Vue, React and Angular. And you see there is also a live preview. So you could also change the code for testing purposes directly in the browser, and see how it changes.

Furthermore, Bit is not stopping there. With Bit you can build your whole Application as components (Including Backend - currently only Node.js, but support is growing), that you compose to a standalone App (https://bit.dev/docs/apps/apps-overview/). They're currently working on something called RippleCI, that will take the headache of integrating and testing components between different teams. Given you have a component "Button", and this component will be used in another Component "Card". If you change something in "Button", Ripple CI will run your tests for "Button" and if the tests passing, it will send a PR to your repository to upgrade the dependency "Button" in your component "Card". (Comparable to Renovate, but smarter) With that, you can enable true component driven design with independent developer and teams.

If you go on bit.cloud you see on the top left a search field. With that, you can search all open source components existing on Bit. That way you can also check out, how it could look like for other components. The company Bit has also shared all their components as open source. So you can see, how they use Bit by their own: https://bit.cloud/teambit