jackjiang2011/mobileimsdk

原创全平台IM通信层框架,轻量级、高度提炼,历经10年、久经考验。可能是市面上唯一同时支持UDP+TCP+WebSocket三种协议的同类开源框架,支持 iOS、Android、Java、H5、小程序、Uniapp、鸿蒙Next,服务端基于Netty。

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 32 minutes ago
Added to GitGenius on September 11th, 2026
Created on October 7th, 2015
Open Issues & Pull Requests: 18 (+0)
GitHub issues: Enabled
Number of forks: 1,382
Total Stargazers: 6,088 (+0)
Total Subscribers: 233 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.4 days
Mean response time: 28.0 days
90th percentile: 88.1 days
Tracked items: 15

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 12
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 711 days
Stale 30+ days: 12
Stale 90+ days: 10

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • 作者已回复 (12)
  • 最新动态 (7)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Mobile IM SDK is an instant messaging communication framework that supports multiple platforms and protocols.

The project addresses the need for a unified messaging layer across diverse client platforms and network conditions. It implements support for three transport protocols—UDP, TCP, and WebSocket—allowing applications to choose the most appropriate mechanism for their environment. The framework is designed as a lightweight abstraction over these protocols, with server-side components built on Netty for efficient handling of concurrent connections.

The tool suits teams building cross-platform messaging applications that need to support iOS, Android, Java, H5, mini-programs, Uniapp, and HarmonyOS Next clients from a single codebase. It is particularly valuable for projects where protocol flexibility matters: UDP for low-latency scenarios, TCP for reliability, and WebSocket for web and browser-based clients. The framework's maturity across a decade of production use suggests it has addressed many edge cases and stability concerns that emerge in real-world deployments. Organizations evaluating this should consider whether their architecture benefits from unified protocol handling across all client types, as this multi-protocol approach distinguishes it from frameworks that typically standardize on a single transport mechanism.

The project maintains a stable codebase with infrequent but deliberate updates. Development activity shows selective engagement with issues and pull requests rather than continuous churn, suggesting a mature tool in maintenance mode rather than active feature expansion. The repository demonstrates long-term commitment to supporting an expanding platform ecosystem, evidenced by the addition of newer targets like HarmonyOS Next alongside established platforms.