Earlier in the summer I shared an update on Ionic Cloud and explained that we’re going to be deprecating the Cloud solution and replacing it a powerful suite of tools & services called Ionic Pro, focused more on development and testing rather than mBaaS style services. At that time, there was some uncertainty around the future of two Cloud services – Push and Auth. I wanted to update the community on where we landed with these services, explain our reasoning, and provide some helpful information to anyone using Push and Auth.

What’s happening with Auth and Push

Let me get to the most important stuff first: As of February 1, 2018, we will no longer provide Push and Auth services. Anyone with an existing Cloud account can continue using Push and Auth through January 2018. After that, you’ll need to find an alternative provider.

The Ionic community is already using a number of leading push and auth providers today.

For Push notifications, we recommend AWS Pinpoint, OneSignal, and Firebase, based on their overall popularity and the number of helpful tutorials and docs that should make it easy for you to get set up. Additionally, OneSignal has created a landing page specifically for Ionic Push developers.

For Auth, AWS Cognito, Auth0, and Firebase area all great options. The AWS Cognito team has put together this great guide on using Amazon Cognito with Ionic. Auth0 has a great Getting Started with Ionic and Auth0 blog they recently put together as well.

Finally, the 2017 Ionic Dev Survey is a great resource to see which backend service providers are most popular among Ionic devs.

Why we’ve made this decision

First, we know this sucks – and for that we’re sorry. Changes like this are never easy. Because of that, the decision to make this change is not something we’ve taken lightly.

With that said, we think this is the best decision in the long run for the success of Ionic as a long-term business, and for the value we think we can provide to our users. While Push and Auth have been popular services, there are a lot of other providers out there that did it a lot better than we did. As such, it would be difficult for Ionic to really stand out and deliver something unique that solved a problem someone else wasn’t. At the same time, we felt like there were areas that no one was doing at all, that would help make Ionic the most efficient developer experience in the industry.

So, instead of providing a sub-par mBaaS, we’re choosing to focus on areas of the dev lifecycle where Ionic can make the most impact in the lives of our developers, while letting them choose from a range of highly capable backend service providers for basics like auth and push services. By allowing vendors like AWS, Firebase, Auth0, and OneSignal to focus on the backend, Ionic can better focus on tools & services that make it easy to design, build, test, deploy, and monitor Ionic apps in a way that only Ionic could.

Next steps for Auth and Push users

If you’re an existing Auth or Push user, look for an email follow up with more details on transitioning to other platforms. If you are using Cloud today and have questions about how this could impact your apps, send us a note at [email protected]

Is this it?!?!

Lastly, I wanted to address a perfectly valid question that a number of people have asked lately: is this it? I understand that with so many changes, there’s concern that other services may be next. Let me assure you that this is indeed it. While you may expect some minor changes to how we package up Ionic Pro, we’re really happy with the direction Pro is taking and the early traction its getting from the Ionic community, and don’t plan to make any more changes. It’s extremely painful for us and our users to announce an end of service like this, but we feel it’s best to get it out there and move on – and provide you enough time to plan accordingly and recommend some great alternatives. At this point, I wouldn’t expect any other big changes to Cloud or Ionic Pro.

With that, let me say thanks to the entire community for your support through this difficult, exciting, hopeful chapter in the Book of Ion. We’re thrilled and humbled to have your support. We know this is difficult, but we also know that it’s paving the way to a better world for Ionic and all of its passionate users. Thanks for being an amazing community!

Signup for the Ionic Newsletter to get the latest news and updates!

  • Matthew Jensen

    Sorry to be that guy but when you’re listing auth, I think after firebase you want that “area” to be “are”.
    Super stoked on the new stuff coming.

  • Sagiv Frankel

    I really wanted to bite my tong here, but I feel like I have to say something.

    At least for me there is no way I can give Ionic Pro a chance after this move.
    Worse over I don’t think I will ever be able to trust any similar solutions as the risk is just to high.

    Push and Auth where great, but you guys never gave it your full attention so it never had a real chance of succeeding. I see the logic with Ionic Pro, but I just don’t see the logic in throwing something away when you could easily charge for and slowly improve. You haven’t put any effort in it for over a year now and although it can be improved, it works well. The other providers will never integrate as well as you can.

    • yesimahuman

      We totally understand, and we know we’re going to have to re-earn the trust of users of these services. The unfortunate reality is that, at the end of the day, Ionic the company wouldn’t have been sustainable if we continued the way we were going. You’re right that we did not put as much effort into the services as we should have. We made a lot of mistakes. I do believe that push and auth would have been very hard businesses to grow in the way we were approaching them regardless.

      There’s a really positive part of this story. Pro is doing really well so far. Ionic’s future as a company that can continue to invest in Ionic Framework, Stencil, and other open source and not-open source projects is considerably stronger as of August 2017 than it was before. That is a major win for the community and for Ionic the company.

      We had to make a really tough decision that we went back and forth on internally and argued for over a year. We know we weren’t providing a great quality of service and we didn’t approach Cloud the way we should have. We’ve done a 180 in that regard and we’ve learned a lot.

      Finally, one thing I neglected to mention is that we are doing a lot more with major vendors today than ever before. For example, we are working closely with AWS to help target content and developer experiences that will be as deeply integrated as Push and Auth were, only now those services are provided by a leading, enterprise ready cloud provider. We think that’s going to be a stronger solution for our users anyways in the future and as Ionic grows our ability to work with partners like this improves.

      We hope we can win you back with Pro, we’re giving it our all.

      • Sagiv Frankel

        Hey max, Thanks for being responsive and patient as always.
        For me this has been a tough year, as RethinkDB shut down(still alive but unclear) and now this major change. There are enough challenges as it is with running a business on mobile.

  • Mat Bettinson

    This is a bit frustrating, not the least because I just spent a couple of days hacking a fix into the Deploy plug-in. It was a bit conspicuous that not much was happening with it.

    That said, I totally understand that these services have a commercial angle and I’d rather see some solution that’s sustainable.

    • yesimahuman

      Hi Mat. The deploy plugin is actually a big part of Pro. If you’d like us to get those changes into the new plugin (that we forked from the current one) can you point me to them?

  • http://www.iziuse.com Reza Rahmati

    I don’t believe that it will be the end for announcing discontinuing a service, if you do it once you will do it again
    I try move all of the services out of Ionic and rely on more reliable providers ;(

  • Ross Rawlins

    Great move! Focus on your core strengths and keep making ionic great.

  • eric cugota gomez

    As i said before, i find the lack of official seamless social auth disturbing. having to work with 2-8 non official most of the time lightly supported and almsot always requiring addition setup plugins is NOT dev friendly. that was the only reason we started using cloud, and it took you two weeks after i started the integration to kill it ( not your fault we decided to try it late). Not gonna lie, this throws me out of the possible client’s list for PRO, as none of the features (except creator maybe, but we do specialized apps, not drag & drop generic templated stuff like the one i’ve seen it outputs, and maybe monitor, but i haven’t seen it and 30$/mo for a single platform’s error report doesn’t sound intersting) fits me.

    • yesimahuman

      We do understand the frustration and apologize again. We’re confident the other options in the market are a better fit for Ionic developers long term.

      Thanks for the feedback about Pro, we hope you do give it a try as many of the users on it are finding it a big improvement to their workflow.

  • http://agilitynerd.com/ agilitynerd

    It looks like Auth0 doesn’t work with Ionic and WKWebView https://github.com/auth0/auth0-cordova/issues/42 and I’ve heard Firebase authentication has the same issue. Can anyone in the Ionic team assist with this issue?

  • Aashish Soam

    what the fuck bro…..???? pro doesnt work at all..

  • Aashish Soam

    problem with native plugin of linkedin and instagram for login.

  • Marcos

    Can you make public the Push service source code so we can run this service on our dedicated server?

  • Vinícius Santos

    Dear lord… I can’t stop laughing.
    Not only my trust in you guys have shaked, but there is no way I’ll would buy ionic pro.
    I was going to buy ionic pro to use push notifications and then I see this message… It’s like a joke for me, for real.

  • Eddie Cheng

    Make our company look bad when this suddenly shuts down. Apps starts to break without the login. Customer blame us for providing shitty apps that stopped working .