Welcome to the latest installment of the Ionic Bonds series, with regular updates on Ionic’s Platform Services.

The latest batch of updates for the Ionic Platform have landed, and I am very excited to introduce the new web client! This new service module has a lot going for it: future-proofed ECMAScript 6 support, no dependencies, and it’s all bundled as a single include for your app!

We weren’t happy with the way the ionic-service components were being handled, and because a unifying update was in order, we decided to take it a step further. Not only is the entire Ionic Platform library housed in a single repository, we’re leveraging the future of web standards with ECMAScript 6 (don’t worry; no change is needed on your end). With the new Platform library, we’ve set up a great foundation for future services and updates.

But why should you care?

You told us you want things to be easy. Easy is good.

Check this out:

var push = new Ionic.Push();

See that? point-up-ssm That’s a completely functional Ionic app leveraging the push notification service. Gone are the days of managing API keys by hand. No more remembering injections for your controllers! It Just Works, and we’ve done the same thing for every single Ionic Platform service in this update.

You may also notice the code above doesn’t use Angular. Don’t panic. All of the Angular factories you’re accustomed to using with the Ionic Platform still exist; they’re just not required anymore.

What you can expect

Quite a bit, actually. A lot of improvements are now live, and we think you’re going to love them. Here’s the short list:

  • Streamlined Installation. There’s only a single module to install, no matter what service you’re using.
  • A new Push class that integrates with the latest phonegap-plugin-push and provides a consistent interface between iOS and Android.
  • A new User model that puts you in control of your users and even gives you the ability to store your own custom data.

How do I get started?

First of all, update your CLI:

npm install -g ionic

Now, check out our new docs, and jump in!

So, what’s next?

Looking forward, we’re going fully heads down to document and expand the Platform APIs. We want to give our docs some love, to make sure the Ionic Platform is as easy to jump into as the Ionic Framework.

Oh, and one more thing. We’re gift-wrapping a special package for our Ionic Platform users, and we can’t wait to tell you all about it! Keep an eye on the blog to be the first to know what we’ve got up our sleeves!

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

  • giorgiofellipe

    whata improve guys!

  • Fábio Rogério SJ

    Perfect! Always evolving…

  • JC

    Great guys. Hope you watching them Badger games.

    • Ben Sperry

      Oh, we wouldn’t miss them!

  • Emerson Thompson

    Wonderful job!

  • Pijamoney Get Free Bitcoins

    INDEPENDENCE DAY for Ionic, YES! Such high quality work as Ionic should stand on its own feet just fine. When I want to build something for the web, I can always do it by simply writing good old ES5 JavaScript, without wasting my time with tons of new shitty documentation of cancerous corporate syntactic sugar like Angular, TypeScript or ES6. In fact, all of ES6 shit is still being transcoded to ES5 in production for every case despite all the propaganda. Everything ES6 does, ES5 will do just fine without the cognitive overhead. Language cognition must prevail over cancerous corporate syntactic sugar. ES6 make a lot of things ambiguous or too convoluted to be quickly recognizable. It feels like Perl and Java had a stupid monster baby who wants to be like JavaScript. I love JavaScript ES5 because it is already infinitely scalable with a powerful simple syntax.

  • jtanori

    Did you guys remove 1.1 documentation?

    • Rudy Pelrine

      Nope, you can still find the Ionic Framework 1.1 documentation at We made the decision to separate out the Ionic Platform documentation because it isn’t the same open source project, rather a collection of tools purpose-built to help Ionic developers build their apps.

  • Sagiv Frankel

    I would really love to get behind this. Unfortunately it seems like the wind it turning every other day… There are so many holes and issues with the current stack I wish they were addressed and documented, before jumping into new complications all the time, even if they are good in their core. I love ES6 and love Ionic, it’s amazing the amount of work you get done, but you keep jumping into the next thing, before the old one is stable.

    • Luis

      I have the exact same feeling about ionic and its ecosystem. A million new things happening at the same time makes me wonder how well everything is being maintained.

      • yesimahuman

        Hey guys, thanks so much for the honest feedback. I’d love to know if there are some specific things we could address that would solve this. Feel free to email me at any time: max AT ionic DOT io

        I know it seems like there is a lot going on right now, and a lot of change, but I see it as more a *hardening* of what we have, vs creating a bunch of new things. For example, Ionic 2 is pretty much the same markup as v1, but feels and enables a lot more native-quality apps. Yes, the way you write your javascript for the apps is changing slightly, but it’s also becoming more “normal” in the sense that it’s not full of angular 1 specific services and features.

        Additionally, we’ve realized that a major liability with Ionic is the cordova plugin ecosystem. Frankly, for something that is so crucial to ionic development, we could do a lot more to support it. To that end, we are bringing a number of plugins into Ionic proper as officially supported plugins. Ionic itself is becoming more “batteries included” rather than disparate.

        With the platform, we want an Ionic developer to be able to come into Ionic, and have everything they need to build and scale a great app, from the client tech and tools to backend services and collaboration.

        Trust me, things feel hectic to us over here as well, but it’s slowly starting to come together. Give us a month or two and I think you’ll agree the future of the Ionic world will be a lot more cohesive than before 🙂

        • Sagiv Frankel

          Thanks max for being so responsive, I have been using ionic for over a year now and would be glad to share the things I loved and the frustrations I have had, I’ll send it to you directly later.

          Generally speaking you are correct the cordova plugin ecosystem – (for example facebook/oauth login) as well as well everything around the native/browser development and deployment process (for example cordova-mocks which misses services and is poorly documented) has been the main cause of pain.

          Everything that has to do with angular and the web side of things has actually been pretty good and stable. (with the exception of history management and the back button which has been a huge pain).

          Since we’re getting so much for free (would be glad to pay later on), I feel it necessary to add a thanks for your awesome / hard / fun / amazingly fast work.

  • Eric Dos Reis

    Where is the 1.1 documentation?

    • Rudy Pelrine

      You can still find the Ionic Framework 1.1 documentation at We made the decision to separate out the Ionic Platform documentation because it isn’t the same open source project, rather a collection of tools purpose-built to help Ionic developers build their apps.

      • Eric Dos Reis

        Only CSS but not Javascript components

        • Perry Govier

          That was my mistake. I’m working on the v2 docs and accidentally broke the v1 docs menu in the process. They’re back now.

          • Eric Dos Reis

            No problem. Thank you.

  • Artyom Pranovich

    Should I include the link to this plugin in my index.html?

    • Eric Bobbitt

      This should be done for you automatically if you’re using the latest CLI version (1.6.5)

  • Eric Dos Reis

    The CLI is falling all the time on windows

  • Gary Fung

    Interesting removal of required Angular dependency. Is there any official support for say, React JS?

    • Eric Bobbitt

      There is no official support at the moment, but we are absolutely investigating other frameworks to support. Our goal with the Ionic Platform is to let web developers do more with their mobile apps. At the end of the day, we don’t care what you use on the frontend when it comes to the platform stuff, so we want to make sure it works with whatever you want to use.

      • Pierre-Alexandre Piarulli

        So… Can we say the door is open for ember in ionic 🙂

      • John Mitchell

        React FTW!

    • John Mitchell

      +10,000 for React!!

  • Alain Boudard

    Brilliant as always … you rock the hybrid world !

  • Asim Hussain

    1) So by web client i’m assuming it’s named because it’s a It reads like it’s going to create something on localhost:xxxx which we can access…. a “Web” “Client”.

    2) Is this in addition to ionic add ionic-service-deploy or does it replace them?
    3) Will our old push/analytics/deploy code work or will that break as well?

  • Robert Larsson

    Does this mean it’s possible to use ionic outside of iphone/android app? (web app)

  • Robert Larsson


  • Fred G. Vader

    new to Ionic and wondering if someone can point me in the right direction. I’m interested in going the Angular 2 route of all this. What version of the docs should I read to get a better grip on things? Anyone know of any good tutorials? Thanks!

  • Blake Dietz

    So what’s the plan for $ionicUser? Is this being replaced by Ionic.User? The documentation is not very clear. Your quickstart guide for Ionic.User is a complete departure of $ionicUser and does not mention whether or not the previous is deprecated.

    Also I’m a bit confused by the way you’ve documented the push usage it feels very incomplete For example you say “The Push service plays nice with Ionic even if you don’t use AngularJS, but we provide angular components as well if you wish.” where you then define a seemingly different api where you’re no longer calling

    In fact your documentation completely shifted out from under me while I was working on implementing some of the examples you provided within your quick start guide for push when they were using $ionicPush. Instead of completely removing references either delineate which apis are deprecated or equivalent.

    tl;dr, your docs could use improvement by referencing whether apis are deprecated (even if it’s alpha).

    Also, thank you for the awesome work, I’m genuinely excited for your push notification and analytics platform, that’s delivering some real value.

    • Harley Mcphee

      I agree, the documentation needs some serious work.

    • Jayr Motta

      I’m also waiting for clarifications on this, I’ve been participating on this github issue ( for a while and everything worked although there were some room to improvement and suddenly the angularjs integration code that you promise continue working stops working?

      I love what you guys are doing but you have to improve the documentation and think about releases consequences on existing code bases.