We evaluated MirrorFly for an instant messaging project because it offers self-hosted deployment along with SDKs for Android, iOS, and web.
What stood out:
- Rich messaging features (one-to-one chat, group chat, media sharing, read receipts, typing indicators, etc.).
- Self-hosting was appealing since we wanted control over our infrastructure and data.
- SDKs covered the platforms we needed, which reduced the amount of work required to build core messaging functionality.
Challenges we encountered during evaluation:
- Integrating and customizing the SDKs required more effort than we initially expected.
- The documentation answered many common questions, but some advanced implementation scenarios required contacting support.
- Licensing costs became an important factor when comparing it with open-source alternatives.
- It is greater flexibility to modify server-side behavior than a commercial platform typically provides.
We are interested in hearing from teams that have used MirrorFly in production or migrated to another platform. Which solution did you choose, and what influenced your decision?
It seems likely that several teams in the community have explored MirrorFly for similar reasons—self-hosting, rich messaging features, and broad SDK support. My understanding is that folks appreciated the control and branding flexibility, but also ran into challenges with advanced customizations and the learning curve for SDK integration. Licensing costs and the need for direct support for complex scenarios were also common considerations, especially when weighing MirrorFly against open-source or SaaS chat solutions.