A server-side .NET library for sending push notifications to iOS (APNS), Android (GCM/FCM), Windows (WNS), Amazon (ADM), and Blackberry devices.
PushSharp is a server-side .NET library that simplifies sending push notifications to multiple mobile and desktop platforms. It provides a unified interface for developers to reach iOS, Android, Windows, Amazon, and Blackberry devices without managing the low-level complexities of each platform's notification service. The library handles transport reliability and platform-specific quirks internally, allowing developers to focus on payload construction and business logic.
.NET developers building server-side applications that need to send push notifications to a variety of mobile and desktop platforms, including iOS, Android, Windows, Amazon, and Blackberry. It is particularly useful for teams managing cross-platform notification systems in C# environments.
Developers choose PushSharp for its comprehensive multi-platform support and modern async architecture, which simplifies notification delivery across different services. Its event-driven error handling and broker-based queuing provide reliable, scalable notification management without requiring deep integration with each platform's APIs.
A server-side library for sending Push Notifications to iOS (iPhone/iPad APNS), Android (C2DM and GCM - Google Cloud Message), Windows Phone, Windows 8, Amazon, Blackberry, and (soon) FirefoxOS devices!
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Unifies notification sending across iOS, Android, Windows, Amazon, and Blackberry through a single interface, reducing integration complexity with multiple SDKs.
Built with async/await and HttpClient, enabling efficient, non-blocking notification delivery suitable for scalable server applications.
Event-driven system provides granular control over notification failures, including platform-specific exceptions like rate limiting or expired tokens, as shown in sample code.
Broker-based design handles connection pooling and queuing automatically, ensuring reliable batch processing and reducing manual implementation effort.
Key features like HTTP/2 for APNS and XMPP transport for GCM are listed as in development on the roadmap, limiting access to modern protocols.
Migration from v2.x to v3.x requires significant code updates, as highlighted in the README, which can disrupt existing implementations and increase maintenance.
Each platform requires separate setup with certificates or API keys (e.g., .p12 files for APNS), adding overhead compared to more integrated solutions.