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

  • North McCormick

    This is so exciting! I think that these are all great decisions. Break down those walls! 🎉

  • a7medo778

    this is awesome,
    i wish ionic team could work with firebase to bring official support to the platform, that be huge for us

    • Mike Hartington

      Whats missing from something like angularfire? What would you like to see?

      • a7medo778

        Dynamic links mainly.
        But stuff like crash reporting, performance, app indexing and analytics are all welcomed as well

      • David Frahm

        As for the Firebase Database, the biggest thing by far for us is offline handling.

        However, since Google I/O 2016 (last year) Firebase is so much more than the real time database. You need a plugin to do all those other awesome things.

        In that scenario AngularFire doesn’t really make sense, so Ionic working with Firebase to make the plugin great would be 💯. And they recently announced their SDKs going open source, so now might be a great time for all this to come together.

        What do you all think?

      • Mike Lallemont

        The killer app I see is Ionic Creator with everything ionic has, plus Firebase as the persistent data store, complete with automatic CRUD forms creation based on models. A man can wish right?

  • a7medo778

    Dynamic links mainly

    But stuff like crash reporting, performance, app indexing and analytics are all welcomed as well

  • eric cugota gomez

    “Auth will most likely be changing into a user profile meta data system for Push, and we’re planning on removing the actual user authentication features”> NO! WHY? this is Auth’s best feature!! can’t you just leave the authentication code and *let devs choose* ?

    • yesimahuman

      There is certainly an opportunity for us to make the native/client side easier and I think open sourcing those local auth libraries into an add-on library makes a ton of sense. What we no longer want to do is be the authoritative database for your users. It doesn’t make sense because you’re not using Ionic for a database.

      • eric cugota gomez

        so you put the burden on us to keep all the oauth stuff in place, while the native auth plugins, no matter how hard you make them easier, will still be a pain to configure? i had less trouble finding a way to trick google web auth that i was not a mobile browser trying to login into G+ than trying to setup g+ native login with all the damn messed up certificates and firebase. This is a big leap backwards for ionic cloud, i’m afraid it’s the only reason we were using it in our company, every other feature is already fast and simple to achieve with a quick fastlane integration.

  • Purusothaman

    Phonegap has a mobile developer app which can be used to test the changes live in real device with all native features. I wish we have something similar.

  • Benedicte Raae

    This all sounds amazing and such good use of the actual phone part of the phone (ref

  • agilitynerd

    I’m glad the features “formerly known as Cloud” are getting some love.

    As someone working on my first beta test with offsite users anything to simplify the process of deploying to them (especially for iOS) would be great!

    As far as crash reporting goes Rollbar has the native and JS sides pretty well covered, except I can’t figure out how to configure them to read source maps yet… Though if you had a similar system that made it trivial that would be nice.

    Ionic Deploy really makes Ionic killer apps. Avoiding the AppStore/Google Play deploy for the majority of releases sets Ionic apps apart from native apps. I like the git push idea to trigger the tool chain too.

  • Jedidiah Weller

    Transparency is key – right on guys and gals, keep up the great work!

  • Matthieu Drula

    Many decisions there, glad to see that you have the maturity to pivot and focus.
    Really like the “Heroku for Mobile.”, it’s catchy ;).

  • Sagiv Frankel

    Thank’s for sharing and letting us know where things stand.
    While I can understand that a startup needs to experiment and evolve I think your going about it the wrong way and I will explain.
    Firstly – you build an awesome service like Cloud, stop 95% of the way there, freeze it for months/years and then partially kill it, which is awful for users like me who have little room for constantly switching things around. I would even prefer you charge more then original intended then this, at least that way I have more options and time.

    Regarding each service:
    – IonicDB was handled well, it was shut down before production which is good. This is also the only area which I agree Ionic doesn’t have much of the edge on the other vendors.

    – Analytics was not a good product and needed a lot of work, so shutting it down made sense, although it could have worked in the long run.

    – Auth and push are great products!!! They offer great integration into the frameworks code and are a pain to manage on you own as far as the different plugins and setup. They are also a great “gateway drug” into the other services.

    – Deploy and package are super and I hope it works out, but they are very risky because of Apple.

    In my opinion the ionic cloud has a great future as a suite of stable services that offer ease of development and ease of integration with the vast community of Ionic developers.

    I started of with Ionic1 and the cloud in it’s beginning, rewrote my app in Ionic2 which was a good call but took forever and broke all the time. Went through several iterations of ionic cloud while it matured and changed and broke. And know this. please have some mercy 🙁

    • yesimahuman

      Appreciate the feedback Sagiv. The only thing on this list that is changing is Auth. It doesn’t make sense for us to manage your users if we don’t have services like Database to use them on. However, we will still be moving forward with Push and the user abstraction will be useful then, but we won’t be the authoritative database for your users.

      We’re learning as we go, and we want to make sure we’re set up for success. We felt like the current direction needed some big tweaks, both to product but also to marketing and tie into Ionic framework. I think you’ll like the changes once they’re live!

      • Sagiv Frankel

        Hey Max, i’m so happy you are taking the time to read the comments and respond :+1
        I read your other comment regarding open sourcing the native/client libraries. That would be awesome!! Would you perhaps also open source your server side stuff? I use node and rethinkdb and it would help out a lot.

        Not sure how this would work, but you guys have done so much great work and if you would make it easy for me to use my current setup and just add some code to save the users on my db and also easily integrate it with push, that would be even better then it is now!

        I know it would take some work/documentation but that would help out so much and I think would be fair towards those like me who have done a lot work around the current setup. It would also defiantly serve Ionic and it’s ecosystem.

        Thanks again

  • Urs

    You are looking for something uniquely to Ionic? Isn’t Ionic unique already?

    Open Source doesn’t mean “at no cost”, so we would agree to pay for Ionic.
    Why not ask for “donations”? You still can add other payable “cloud” services.
    We all have so much interest that Ionic continues…

    • yesimahuman

      Part of this effort is to put a lot more resources into Ionic. However, we don’t think we can build a strong business charging one-off for UI components, and our developers struggle with more than just UI.

  • Daniel Aparicio

    quote:[The first app (and the one that will be paid-only), will be the new Ionic View, focused on beta and client testing] If I want to deploy a beta version of my app to be tested by… let me say… 10 beta-testers… each of them has to PAY to install Ionic View in his/her phone?? If I’m right this would be too much cost to deploy a beta version to a “decent” group of beta-testers. Bad decision 🙁

    • yesimahuman

      Users won’t have to pay to install View. The team/developer using View will need to be on a paid plan, but they can invite any number of free testers to use it.

      • Daniel Aparicio

        OK, great!! Sorry, I understood wrong. These are good news!!

  • Reza Rahmati

    It’s a bad news for business that take ionic Auth serious and developing their app based on that. I hope this service will be continued.

  • Lim Heng Cheun

    Just for my own opinion. Ionic can just keep the services that are not unique but is useful for the market, even outside market already have the better service. As a user point of view, I will use the platform that includes all in one package (even the services is not the best in the market), rather then I need to login thousand admin panel (ionic, google analytics, jwt etc…) to check different kind of report.

  • Faizaan

    Will the new Ionic Developer App still allow someone other than me to use a code to access the app?

  • Alberto

    Hi. I need prompt about this. I have an app built with Ionic Auth, basic + social (Facebook) which is suposed to be live in the inmediate future. I’m talking in about a week? Or so. Please, how is this afecting me? Will my app be broken? The development stage is finished, I cannot redo NOW the auth module with other provider. Thank you very much.

  • Doug Justice Jr.

    Great update and I think exactly the direction Ionic needs to go. However, I am getting a lot of pushback from some of our larger enterprise customers who are hearing the buzz’s about NativeScript and using views that are not just browser-fied, but more native and true mobile views for the android and ios platforms.

    Can we expect Ionic to have a “choice” as Nativescript does in the near future? PWA’s and quick creation and deployment will always have a place I believe, however in terms of speed, responsiveness and a more true “native” experience, just wondering where Ionic is going to land with this.

    • justifyer24

      I don’t know. I’ve developed for Nativescript and for me it’s actually isn’t as good as it looks. I’ve did 2 NativeScript and boy it’s so much pain compared to ionic 2 beta I did a year ago. I’ve even revamped 1 of it back to ionic 3 cause of how much it sucks.

      • Doug Justice Jr.

        Since my posting we’ve decided to go completely Ionic with our development, mainly because of things you had mentioned in your comments. I’ve heard some really painful stories about Nativescript (especially in the UI interfaces). I suppose if you’re doing a game or really need some native-like performance, then just code the app in the original platform’s language. For us, we’re going full speed ahead with ionic and couldn’t be happier with the decision to do so. Thanks @justifyer24:disqus for the post. It’s a good confirmation we’ve made the correct decision for our company.

  • Chris Madsen

    So Ionic View will be a paid service? Will there be any other options? I just a freelance designer learning to build simple apps, and I will probably only build a few simple ones a year. So I will have to pay to be able to see them and show them to my clients? Any idea how much this will cost?

  • Sebastián Rojas Ricaurte

    Please please, mpore about Auth service, I’m developing the v2 of my app, and we use nativa auth and basic auth

  • ihadeed

    It’s sad to see Auth service go 🙂 … it was great. Very easy to use and very useful.

  • Joseph Chambers

    Goodbye Ionic, hello React Native. $49/mo to use ionic view? c’ya.

    • yesimahuman

      Ionic Framework is still just as free as it was before, and just as free as react native (in fact, more free because we don’t have a PATENTS clause). We aren’t changing that at all. Ionic View will be free to use for public apps (which is how it works today for the most part). To use private sharing and manage tester groups, etc. that’ll be part of the paid tier.

      We are adding new features and capabilities for teams, and will be charging for those.

      • Joseph Chambers

        You scared me with the ionic view. Thanks for replying.

        • yesimahuman

          Of course! It wasn’t very clear, but we are adding a lot of new features and services that we think are missing from the market and will help Ionic developers work a lot more quickly.

          Some of these features will help bigger teams, and we think it’s fair to charge for those (and Ionic making money is really good for Ionic Framework!) While, at the same time, enabling smaller teams and individuals to continue to get a lot out of the offering.

          This is going to be a process and we will continue to listen and make sure we are hitting the mark. Thanks for the feedback!

  • javier Aladid

    I’m happy to see things moving forward here, but I think the pricing is terrible. How on earth are single developers gonna be paying 50$ per month? it’s just crazy, in my eyes. Maybe no need for a free tier, but a entry level tier that allows people to get started and use the cloud services moderately. Something like 5$ a month to get very few but some packaging.
    I feel this change is pushing out all the devs that are just trying to make apps and not yet making any money with it.
    600$ a year is the entry tier? I think we all lose with that change.

  • Nick Franklin

    I’m confused as I have just read a blog post by Matt Kramer regarding the development of a New Ionic Creator App removing the web based drag and drop designer in favour of this new app and file level access to code. There appears to be mixed messages coming from you guys as to which way Ionic is going. Can you clarify what’s happening.

  • schiffbruechige

    I hope that before the Auth service is cut off, that we get either migration tutorials, or a library we can just add that does something as simple – happy for you not to want to store my details, it was just the easiest possible thing, when I wanted to have Auth then get on with developing..

  • Ivan Jordan

    Hi everyone, we just published our app. I’m very concern about the new changes there would be a way to transfer the users from ionic Auth to other services? Most of our app is based on the auth service. Thats really bad news for us.

  • soto352134

    Good lesson you share about word press technology and i hope every people are like this education in here. To know more information and guide line such kind of education is more helpful for us.

  • DavidD

    Like tons of people, those next steps are at first tough times you have to go through !

    I am using IonicAuth/IonicPush on Ionic V1 to generate a device token. I have my own authentication process.

    What are my alternatives since I am not using the push service at all. I do web downstreaming from my web server but I still need to display in-app push notifications.


  • Difa Sanditya

    Let’s say I’m new on Ionic. Regarding to Auth being removed, will Google Native Authentication be removed too?

  • reallyquitetoby

    May I ask how the changes to Deploy and Push will affect apps currently using those services in Ionic 1. We have quite a few live apps and some currently in production using those features and we are wondering what will happen when January 2018 comes around and (according to what I’ve read) the legacy Cloud dashboard will no longer be available. Will there be a migration path that will allow us to continue using Push and Deploy (albeit paid) in our existing Ionic 1 apps?

    Redeveloping these apps into Ionic 2 to use these features is not really an option for us as the client will not fork out for a major redevelopment into Ionic 2, but they will still want to use the features (certainly Push) that are currently working in their production apps.