chat-builder VS react-virtuoso

We're pretty similar to Chatwoot in some ways - Kam described some differences here: https://news.ycombinator.com/item?id=26503697

To reiterate some of the differences, or why people might choose us at the moment:

- A lot of our users really like our Slack integration. For small teams, this means they don't even really have to use our dashboard if they don't want to, because they do everything from Slack.

- We offer a live screen sharing feature [0]

- We're working on a library to offer complete customization of the chat UI on your website [1]

[0] https://storytime.papercups.io/

[1] https://github.com/papercups-io/chat-builder

Thanks for the mention:

Like Pranav said we think the space is good to have multiple players and we've had many friendly conversations where we have traded notes.

I think our vision is very similar in terms that we eventually want to focus on omni channel customer communication.

A few things that chatwoot has that we don't at the moment like they mentioned are:

1. Omni channel through messenger and Twillio integration

2. A Mobile app to chat with your customers

3. Shared inbox for teams - for team management

1. We have a Reply from Slack + Reply from Mattermost integration where you never have to leave your dashboard (We believe you should never leave your work place)

2. Highly customizable [chat widget](https://github.com/papercups-io/chat-builder) with react and flutter components

3. We have a live screen sharing feature that lets you debug issues with your customers through the browser

Our goal is to build out omni channel communications too but at the moment we want to make our chat widget experience amazing and we believe that your chat widget should look like your website and not an ad for your tool.

If we limit the number of rows rendered to only show the visible items, we can limit the cost of re-rendering the table. Even if there are a large number of rows in the table, only the ones on the screen will be rendered. That can be done by virtualization. I will use react-virtuoso for the app.

react-virtualized is very old and unmaintained. I will plug my fairly popular solution, https://github.com/petyosi/react-virtuoso.

Try virtualization inside your dropdown. For sure it will improve the performance. Check https://virtuoso.dev it's very easy to implement

Shameless plug, I am the author: https://github.com/petyosi/react-virtuoso

I would take a look at React Virtuoso

if it is group chat that many users can write messages into one group means it will be a lot from some point. and suppose there is another list for example user contact list in aside along with chat section, size of dom will grow in app. when user select some contact item react gets sluggish from its rerender aspect. but I don't recommend to start with it unless you are not observe performance issues and app layout is simple to implement this feature there is also https://virtuoso.dev/ for virtualization FYI.

react-virtuoso is a relatively new package for virtualization, published first two years ago. It comes with all the necessary features and support that one might eventually require in a developing project.

So far, react-virtuosso https://virtuoso.dev/ is the only library that supports this.

In many large companies, development becomes slow and incredibly expensive. If an engineer costs 10k a month, the fully burdened cost to the company is often 5-10x that. While the costs increase the output usually goes down. This is something I’ve been thinking about a lot over the last months. As our startup keeps on growing I want to hold on to that startup level of productivity. Petyo just joined as our 100nd team member, so as we reach this initial level of scale this is becoming a more urgent concern.