DEV Community: Nivedita Bharathy

The buyer-seller conversation nobody owns

Nivedita Bharathy — Wed, 23 Sep 2026 07:12:47 +0000

Buyer-seller chat sounds simple.

Until someone sends their phone number and suddenly the conversation is happening outside your marketplace.

That’s where things get interesting.

You’re not just building a chat UI anymore. You’re dealing with contact sharing, message history, disputes, moderation, deleted messages, and giving support teams enough context to figure out what actually happened.

And there’s a bigger question underneath all of it:

Who actually owns the conversation?

If the chat is part of the transaction, it probably needs to be treated as more than just another messaging feature.

We got into some of the engineering problems around this here ↓

https://www.cometchat.com/blog/the-buyer-seller-conversation-nobody-owns

Classroom chat is a moderation problem

Nivedita Bharathy — Wed, 23 Sep 2026 07:06:21 +0000

Classroom chat is a UX problem until you have to moderate it.

Then the engineering questions start piling up.

Who can message whom?
What happens when a student sends something inappropriate?
Do teachers see every message?
What gets flagged automatically?
What happens across different roles, channels, and age groups?

The chat UI is the easy part.

The hard part is building the moderation layer underneath it without turning the experience into a maze of restrictions.

We dug into what that actually looks like when you're building chat for classrooms ↓

https://www.cometchat.com/blog/the-classroom-chat-is-a-moderation-problem-wearing-a-ux-costume

Your Chat SDK Reached End of Life. Now What?

Nivedita Bharathy — Mon, 07 Sep 2026 12:54:29 +0000

An SDK reaching end of life sounds like a vendor problem.

Until you realize you're the one migrating users, conversations, message history, attachments, read receipts, threads, mentions, and everything else that makes chat actually work.

The difficult part isn't picking a replacement SDK.

It's making sure the migration doesn't quietly break the conversations your users depend on.

We broke down what teams actually need to think about when migrating chat infrastructure, including:

• Bulk migration vs live migration
• Preserving message history beyond just the text
• Handling attachments, mentions, threads, and receipts
• Why migration order matters
• What zero-downtime migration actually involves

If you've ever received an "end of life" email from a vendor and immediately thought, well, this is going to be a project, this one's for you.

Read the full breakdown:(https://www.cometchat.com/blog/what-happens-when-a-chat-sdk-reaches-end-of-life)