Last week, developers of Sparrow – an extremely popular email client for Mac that offers Gmail integration with multiple accounts, labels, Priority Inbox and a Unified Inbox had released their much-awaited app for the iPhone.
Unfortunately, the only downside to what would have been the perfect email app for the iPhone (at least for Gmail users) was the lack of push notifications. The developers had explained why their iPhone app doesn’t support Push Notifications.
We had noted that Sparrow for iPhone + push notifications is the native Gmail app that Google should have ideally released.
We have some great news if you were disappointed by Sparrow’s lack of push notifications support as IpuIpuApps – developers of popular jailbreak tweaks such as 3G Unrestrictor have developed a jailbreak tweak called Sparrow Push and as the name suggests, it brings push notifications to Sparrow’s iPhone app.
After a long anticipation the iPhone application “Sparrow” was released with a disappointing limitation through Apple’s restrictions: Users are not notified of new mails if the application is not running. The jailbreak tweak “Sparrow Push” enables this functionality using IMAP idle and makes Sparrow a complete replacement for the stock mail client on the iPhone.
Sparrow Push is available on Cydia for free.
It is not available in Cydia yet, but should be available via the Big Boss repo very soon. We’ll let you know as it is available.
If you’re a Gmail user, then we would strongly recommend you to check out Sparrow for iPhone, which is available for $2.99 in the App Store (direct iTunes link) along with the Sparrow Push.
Update 1: Sparrow Push is now available on Cydia. IpuIpuApps plans to add Notification Center integration in the future.
Update 2: Please avoid installing the jailbreak app, it seems to be causing problems with other background apps such as music apps stop working after installing this jailbreak tweak. If you’ve installed it, then we would recommend you to uninstall it.
Update 3: Kim developer of Sparrow Push has confirmed in the comments that the issue has been fixed (version 1.0.1-1). Thanks Kim for the update!