I’m comparing a few instant messaging SDKs for a project, and most of them seem to offer the basics like one-to-one chat, group messaging, media sharing, read receipts, typing indicators, and push notifications. Beyond those features, I’m curious about what developers actually prioritize in production.
While looking into how instant messaging works, I realized there’s a lot more involved than just sending messages—things like message synchronization, offline delivery, presence, and scalability can make a big difference depending on the application.
For those who’ve integrated an instant messaging SDK, what were your biggest challenges? Was it documentation, customization, performance, or something else?
Hi @kathrininfanta
Welcome to the Auth0 Community!
First, I would like to let you know that since your topic covers a more general inquiry regarding an Auth0 implementation and nothing specific, I will move it to the Dev to Dev Hub category in order for the topic to remain open indefinitely.
Other, since you are asking what developers usually prioritize when evaluating an instant messaging Software Development Kit for production use and what the biggest implementation challenges tend to be. I could not find relevant Auth0 documentation or community guidance on instant messaging Software Development Kits, because this topic is outside the Auth0 identity product scope covered by the available sources.
- Note that the available Auth0 sources do not cover production tradeoffs for third-party instant messaging Software Development Kits such as chat synchronization, offline delivery, presence, or media transport.
- Recognize that Auth0 primarily covers authentication, authorization, Single Sign-On, Multi-Factor Authentication, and related identity workflows rather than messaging platform architecture.
- Use vendor-specific documentation and engineering communities for the messaging Software Development Kits you are comparing, because those sources are more likely to address production concerns such as message ordering, delivery guarantees, presence accuracy, scalability limits, push reliability, moderation, and compliance requirements.
- Evaluate production readiness by comparing non-feature criteria such as offline synchronization behavior, webhook and event support, rate limits, regional data residency, end-to-end encryption options, observability, Software Development Kit stability, and migration difficulty.
- Test the messaging Software Development Kit under realistic load and poor network conditions, because production issues often appear in reconnection handling, duplicate delivery, message history consistency, and mobile background behavior rather than in basic one-to-one chat demos.
Kind Regards,
Nik