Pushwoosh Blog



What’s happened?

This Thursday the entire developers’ community was shocked to find out that Facebook is shutting down Parse, their mobile backend as a service. “We have a difficult announcement to make. Beginning today we’re winding down the Parse service, and Parse will be fully retired after a year-long period ending on January 28, 2017,” Kevin Lacker, co-founder of Parse, said in a blog post.

What does it mean for developers?

It won’t be an overstatement to say that Parse has been a reliable backbone for programmers. Parse helped developers spend more time coding and less time on keeping up the back end, so it was indeed the sharpest tool in the shed for independent programmers and startups with online-enabled apps.

Sadly, starting today developers will have to migrate to other platforms or build their own Parse-compatible service, as provided by Parse. This is definitely bad news for those who invested their time and money in publishing BaaS apps. The good news is that developers are given a whole year to find a solution.

Why did Parse appear to be a real tidebringer causing a migration tsunami?

Back in 2014 when Urban Airship deprecated its developer program, Pushwoosh provided a warm welcome for all its ex-users. Developer Program was a starter tool for developers letting them build their first Push Notifications campaigns with a generous, but still limited number of pushes. Once it was closed, those developers came to our safe harbor looking for acceptable pricing and reliable service with all the respects given. That was the first significant migration tide, and the reason why we had to create the Migration Tool.

In November 2015 Zeropush team joined Twitter to work on new challenging projects and announced their push platform deprecation. In order to help developers reach out to their users through a simple, web-friendly API we provided a truly easy integration, required no painful integration and code changes. We even built a custom API adapter allowing Zeropush users to continue their Push Notifications campaigns as if they keep using Zeropush platform. That was the second migration tide, and truly seamless one.

A couple of years back, Parse concentrated a lot of efforts in the most important niche for us: push notifications. Now, when they are slowly but surely shutting down the service, the third tide will run all over the push ecosphere. Users, previously tied to Parse Backend, are now free to choose the way they going to set their sail. And we are offering them a win-win collaboration.

Reasons to choose Pushwoosh above all others

This year Pushwoosh is celebrating its 5th anniversary, and most of the heartbroken users are looking for something to safely rely on. The push notifications part is already covered by our Migration Tool, and takes mere minutes to import.

However, unlike many other services, we are not planning to stop there. Own plans for 2016 include, among other things:

  • Parse API adaptation in order to help proxy existing services.
  • Possibility to host your Parse Server on Pushwoosh premises (as a part of Enterprise package)
  • All in all, we guarantee a flawless migration based on the top of proven experience. No one will leave disappointed as it’s not our first time we help users move on when the time comes.

    We welcome everyone aboard!

    There’s a brief yet important release note concerning our Unity plugin update we’d like to share with you today.

    We changed the Public API of the plugin to make it more comfortable to use.

    • We simplified the initialization process. From now on you can call Pushwoosh class methods immediately without waiting for OnInitialized event.
    • Now it is possible to set Application Code and Project Number externally, from outside of the plugin.
    • Now you can select when to subscribe for push notifications. It’s become possible due to the new method called RegisterForPushNotifications. Pushwoosh.Instance.RegisterForPushNotifications (); Don’t forget to call it!

    We advise you to carefully review the new guides and samples before using new sources. We expect that these changes would help us provide more customizable experience for your future Unity campaigns!

    Good news for Windows-lovers! We’ve recently updated our plugin for Cordova integration!

    Previously we provided support of Cordova-generated projects for iOS, Android and Windows Phone 8 only. Now our plugin supports the whole Windows platform: Windows 8.1, Windows Phone 8.1 and Windows 10 projects as well. Our new plugin works with WNS instead of MPNS, but the changes won’t affect users of the previous plugin version somehow. Though, we recommend those of you who use WP8 a migration to Windows as the way to stay up-to-date.

    Integrate Pushwoosh SDK to your Cordova project and broaden your audience!

    It turns so that latest version of Unity (5.3) has stopped the support of Windows 8/Windows Phone 8, as they were deprecated in Unity 5.2. From now on Unity supports only Windows 8.1/Windows Phone 8.1 and upper versions.

    Considering Unity upgrade, we updated our SDK in order to integrate with Windows 8.1/Windows Phone 8.1. It means that we won’t support Windows 8 any longer. Previously, when Windows 8 was in use, we used Microsoft Push Notification Service (MPNS) to deliver push notifications. With the advent of Windows 8.1 and Windows phone 8.1 we switched to Windows Notification Service (WNS) to stay up-to-date.

    As Unity has already deprecated Windows 8, Microsoft is about to switch fully to WNS and our SDK will no longer support MPNS, we highly recommend you to upgrade as well.

    No More Restrictions Using Push Notifications For HTTP Websites!

    Jan 19, 2016

    Usually Chrome Push Notifications require your website to use SSL certificate. In other words, your website has to be on HTTPS to receive push notifications. SSL (Secure Socket Layer) is the standard security technology, which is used to establish an encrypted link between a web server and a browser. It maintains privacy of the transferred information and protects user against poor validation of HTTPS certificates and man-in-the-middle attacks between your server and the push provider.

    So, not all websites are using SSL yet, but you may need to send pushes to them. Pushwoosh has made it possible to send push notifications to non-SSL websites. So users are able to be subscribed even if their site is not on HTTPS. For a thorough description of how you can integrate Pushwoosh Notification Service to HTTP website visit our guide.

    It’s worth mentioning that major browsers like Chrome and FireFox are planning to gradually deprecate non-SSL websites in near future, as we have been informed by our partners. Though, as long as HTTP resources are widely used, Pushwoosh will help you to broaden your audience by reaching out to a wider number of websites.

    To sum up: secure or not, we’ll deliver your message, if you need it. Just remember: safety first. Always!

    hello_http_2
    Pushwoosh https://www.pushwoosh.com/wp-content/themes/pushwoosh/img/logo.png support@pushwoosh.com