Ionic 2 RC0
Well, hello there, wonderful people! You may have noticed that we’ve been a bit quiet since the last release of Ionic and may have been wondering where we ventured off to. We’ve been hard at work prepping the Ionic 2 Release Candidate! We’re happy to announce that it’s finally here, along with some major performance improvements and new features!

All The excitement

Now, before you rush off to update your dependencies, please take the time to read over this section of the changelog. There are several structural changes to the setup and build process that need to be made before your app can be upgraded. The changelog goes over the update process. Without these changes, your app will not be upgradeable.

Update to Angular 2 Final

Angular 2.0 final is out and ready for folks to use. Make no mistake, THIS IS HUGE!! The API has solidified! Final introduces some updates that make organizing dependencies in your app much easier. @NgModule allows you to declare all your dependencies up front, instead of having to declare them multiple times in an app. Other changes in Angular include internal API changes, so any custom components will need to be updated accordingly. Give the Angular Changelog a glance for your updating process.

Ahead of Time Compiling: Simply put…faster apps

With the updates to the core version of Angular used in Ionic, we’ve been able to take advantage of the Ahead of Time (AoT) compiler in our build process. This was a big change for the internals of Ionic, but the payoff is well worth it. Instead of compiling your templates in the browser and on the fly, which can be very slow if you have a large view, AoT allows for the templates to be pre-compiled in a build step. With AoT in place, you can expect to see a big improvement in your app’s boot-up time, as well as in view switching. The compiled code that is created by AoT is highly optimized code that can run much faster than code any of us could write.

Don’t believe us? Take a look! We used our tabs starter as a base point for testing Beta 11 and this release.


Beta 11 on the left, RC on the right

A New Build Process

Now, with AoT in place and Angular’s API finalized, we’ve been able to look at Ionic’s build process and really see how we could make it better. We took our time and looked at all the available build tools and fell in love with Rollup. There are many build tools out there, and they all do a great job, but for us, Rollup provides some nice technical features, like much more optimized code that tends to have fewer closures. This enables code to be executed much faster in the browser. There’s also tree-shaking, which allows you to include only the code your app needs to run, making the bundled output much smaller.

With this new build process, we’ve also started to move away from a Gulp-based workflow. We’ve started moving over to NPM scripts, since they offer the same flexibility that Gulp tasks provide. This also means that there’s one less dependency to install (which ultimately turns out to be many many less dependencies) when you build the app. The new NPM script build is heavily inspired by the amazing work done by the Create-React-App team, where all the configuration and build scripts are a package that gets called. For users, though, nothing changes. You can still run ionic serve and have the entire build process run before launching a live-reload server. If you want to customize your build, thankfully, everything is configurable and very straightforward. We think this strikes a good balance between “Batteries Included” and “Bring Your Own Build Step”.

It’s worth noting that the updates to the CLI to make this possible also include backwards compatibility for older Gulp-driven projects. So even as these new features become the default, Gulp will still be supported for older projects. And if you still want to use Gulp in new projects, no problem! Go for it! Any task runner, or even straight node calls, can execute these scripts.

We’d also like to point out that Ionic is not tied to any one bundler or our @ionic/app-scripts package. If you’re happy with your own build process, there’s no reason you can’t pick and choose the tools of your liking to customize your own Ionic build scripts.

Cleaning up the App Structure

Now that Ionic and Angular themselves have finalized their APIs, we now have a solid sense of “how” Ionic apps should be structured, such as the directory structure, filenames, and file locations. We’ve also made some changes to the default app you get from ionic start, which will make a lot of sense when you see them. We’d like to point out that the new structure is the structure we’ll recommend moving forward. But just like our recommended build scripts, you’re welcomed to adjust it however you like, since Ionic itself is not tied to a specific structure.

With @NgModule being introduced, we decided to rename the top source directory to src (mind-blowing, we know!). All of the files related to the root app component and @NgModule get stored in an app folder, while pages and providers sit in src/. We’ve also added an assets directory to house things like images, manifest.json, and a service worker file.

Parting words

This release brings Ionic 2 very close to its final form. Between each alpha and beta version, we’re sure you’ve noticed significant changes to the API…but no more! The API for this release candidate is the same we hope to ship for our final (which isn’t far behind). Now, with the RC out, we’d like to ask for assistance from our awesome community members to really beat on the framework and break all the things. As always, please report any issues you find. Once we’re confident there aren’t any major show-stopping bugs within our release candidate(s), you can expect to see 2.0.0 out soon afterwards.

Link to Changelog

Link to Rollup

Link to Ionic 2 RC0 Docs

Link to NgModule

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

  • Douglas Godinho

    Greaaaat news!

  • Malkiat Singh

    Nice …. I am waiting for this …. Good works guys

  • giorgiofellipe

    Amazing news! Hope it get out asap

  • Tom McLellan

    Congrats! Sounds like an awesome set of improvements. Really glad you went straight to RC and that this is based on Angular 2.0.0! Nice work!

  • Sohelelite

    ‘Let’s roll up our sleeves, get down to work and get the job done’

  • jabrantes


  • Michael Olukoya

    this makes me too happy

  • jrwhip

    Wow. I wasn’t expecting you to go straight to RC. Awesome work guys. Just Awesome!!!

  • Jon

    Why does the Steps to Upgrade say to Change any uses of the private TypeScript keyword to public?

    • Josh Thomas

      This is specific to the Angular2 AOT compiler. Component variables need to be public so that Component Factories can access them.

      • Josh Garwood

        So just to be sure, we can’t use private variables/functions *anywhere* as a result of this?

        • 0v3rst33r

          ONLY the members your template needs access to. Everything else you can still keep private (this is how I did my porting last night and works well). Better yet, don’t make any changes, let the compiler guide you with its errors feedback, and this way you can change JUST the necessary ones, instead of having to go guess and try and remember and figure out all the Compoment members your template uses.

      • masimak

        Can you please clarify? Are we talking about variables used in the template that need to be made public, so that the compiler knows are used somewhere, or ALL variables no matter their use inside components should be made public for some reason I cannot guess?

        • Josh Thomas

          This is specific to components.

      • Pavlina Drosos
        this gives an answer why all Component properties must be public. It
        doesn’t seem to be valid for services, so can we assume it’s valid only
        for Components?

        • Justin Pierce

          Thank you for this. The upgrade document really should be updated, as the requirement as stated is pretty ridiculous.

    • Pavlina Drosos this gives an answer why all Component properties must be public. It doesn’t seem to be valid for services, so can we assume it’s valid only for Components?

  • Ricardo Bertolín

    Great news!!!!

  • Juarez Filho

    Way to go! Keep rocking guys. I’m really proud to be an Ionic enthusiast. ?

    • Mike Hartington


  • Alex

    Can we get an update on the wkwebview plugin? I see it was not included in this RC. Is the current plugin production ready? I still see a list of issues on GitHub, when will there be a finalized version?

    • Mike Hartington

      The WkWebview plugin is independant from the actual framework. The plugin is still usable and we are encouraging people to test it out.

      • Young Park

        loving wkwebview except one thing. cookie.

  • Ramzi Youssef

    Congratulations ?

  • Fernando Herrera

    Ionic is amazing! love every part of it! Keep going!

  • Juan David Nicholls

    Hi Ionic Team! Thanks for your hard work!
    One question, Can you guys create an Ionic 2 Starter Template with some examples and recomendations like my Ionic 1 Starter template?

    Thanks for all, Nicholls

  • Moataz El Gamal

    Makes me super happy ? . I have been waiting for this. This brings hybrid development way forward!! I will test and get back to you.

  • rob3c

    Congrats, and thanks for all of the hard work – this is awesome news!

    I noticed that the NPM version for ionic is 2.1.0 without an rc0 label. Is that intentional? How will the final release be distinguished?

    • rob3c

      Oops – I was looking at the ionic-cli version (2.1.0). It’s the ionic-angular version that’s at 2.0.0-rc.0 🙂

  • Thọ Nguyễn

    Awesome…great work! Thank you Ionic Team.

  • samba

    great news !!!
    It took more than a month but it’s finally here.
    Mobile Hybrid development has reached a new level today.

    thanks guys

  • Youssef

    Wonderful news!
    Keep going guys to achieve the final release launch soon to allow us to start building stable Apps 🙂

  • Diego Trujillo

    Hi ionic team! i love ionic, thank U so much to bring this tools. i am trying this new version and i have the next mistake

    Error: ENOENT, open ‘/Users/diegotrujillo/Documents/Ionic/testv2/www/index.html’?

  • Jay Cambron

    Love it. Great work!

  • Hugh Hou

    Amazing! Lots of change tho from beta 11…. mmm, lots of updating…

    • danbucholtz

      Angular had some large breaking changes to get where they needed to go with AoT compiling. We are following suit with them.

      Please let us know if you have any challenges updating.


  • Marc Syp

    This is great! However — after upgrading my ionic CLI and starting a fresh app, I get TS errors. Specifically:

    [15:35:58] Error: Could not resolve ‘@angular/platform-browser-dynamic’ from C:
    at Error (native)
    at C:[email protected]
    at C:[email protected]
    at C:[email protected]
    at process (C:UsersmsypDocumentsBitbucketimmersive-projectionnode_modu
    [email protected]_modulesrollup-plugin-node-resolvenode_modulesreso
    at ondir (C:UsersmsypDocumentsBitbucketimmersive-projectionnode_module
    [email protected]_modulesrollup-plugin-node-resolvenode_modulesresolv
    at load (C:UsersmsypDocumentsBitbucketimmersive-projectionnode_modules
    at onex (C:UsersmsypDocumentsBitbucketimmersive-projectionnode_modules

    etc etc

    Updating Angular manually with npm didn’t help. Am I missing something?

    • Gevorg Harutyunyan


    • Mike Hartington

      This error doesn’t really tell us anything. Please post an issue on githup with the necessary information needed to recreate the issue.

      • Marc Syp

        Ok, that sounds great. However, this comment doesn’t really tell me anything. 🙂

        What is the necessary information needed to recreate the issue? All I know is I created a fresh app using “ionic start myAppName sidemenu –v2 –ts” and the code doesn’t build using ionic serve. Meanwhile, I posted a new message on the forum with some additional info on my system (“ionic info” output)… what else do you need? (Not being snarky — just need to know what else you need to know.)


        • Mike Hartington

          The forum post will be enough, thanks!

        • danbucholtz

          Hi Marc Syp, can you run `npm –version` and make sure you’re on version 3? Ionic 2 will require `npm 3` going forward.

          Here are instructions on updating npm.


          • Vinay Uppin

            Hi danbucholtz, I was facing same issue. solved it by updating npm to version 3, Thanks a lot. 🙂

          • Marc Syp

            Thanks everyone — I was on the right track, trying to update npm… but it wasn’t working. I see that I need to update node as well, before I can update npm! Will try that and report back on the thread referenced above.

  • Rick Li

    Awesome Ionice Team

  • Gevorg Harutyunyan

    Awesome news!
    Just wondering why did you moved away from gulp to npm scripts?
    I’ve took a look at ionic build scripts and it felt like reinventing grunt 😀

    • Mike Hartington

      We opted to move to npm script as it allowed us to remove more dependencies. With the internal app scripts and npm hooks, we didn’t really need gulp anymore.

      • Gevorg Harutyunyan

        Makes sense. Thanks for reply!

      • peb7268

        Good choice on that. Been doing it in my own projects for a while now.

      • masimak

        Yeap good choice guys. Been doing it in all my projects for quite a while now and couldn’t be happier

  • Chakraveer Singh Sandhu

    Ionic Team is amazing! I Love it.
    Great work team,We were waiting for this.

  • Evandro Junior

    Hi! Does it fix the white screen of death?

    • Rokas St

      Death screen is still apearing (both white or black randomly)
      This happens after clicking back button insanely and going trough nav like psy.

      Also, In this release I’ve encountered some weird content blink issue before alert/popup is being shown

  • Boris Gastelú

    Awesome. Great Work Ionic guys!

  • Sundara Vel

    Great Update..! Keep it up

  • Young Park

    Fabulous ~! performance… that’s what i was looking for.

  • Julian

    Awesome! Now to migrate all my existing apps

  • Patrick Matthews

    Awesome!! Can’t say much more as I want to go and play.

  • IrfanAmir

    Congratulations!! and Thank YOu

  • Prashanth

    Awesome. Great work Ionic Team!

  • Edy Avendaño

    Awesome!!!!! Thanks Ionic Team.

  • chandan das

    I have been trying to create an app using ionic-cli since yesterday but without success. ionic-cli just does not work. No proper help and suggestion on github as well.

    I see very high excitement here while basic thing does not work!!!

  • Sagar Mahajan

    Cheers for Ionic, News made my day

  • Umut Topuzoglu

    Can we use the Angular Component Router now?

    • Malkiat Singh

      why you need angular router navigation stack works awesome 🙂

      • Umut Topuzoglu

        I want to build browser apps with ionic, pwa’s. I want to use url routing. So how do I activate this?

        • Malkiat Singh

          I think you can register app route providers

          providers: [appRoutingProviders],

          and create a app.routing.ts
          import { ModuleWithProviders } from ‘@angular/core’;
          import { Routes, RouterModule } from ‘@angular/router’;

          import { LoginComponent } from ‘./login/login.component’;
          import { RegisterComponent } from ‘./register/register.component’;
          import { ToDoComponent } from ‘./to-do/to-do.component’;

          const appRoutes: Routes = [
          { path: ”, component: LoginComponent },
          { path: ‘login’, component: LoginComponent },
          { path: ‘register’, component: RegisterComponent },
          { path: ‘todo’, component: ToDoComponent },

          export const appRoutingProviders: any[] = [


          export const routing: ModuleWithProviders = RouterModule.forRoot(appRoutes);

    • danbucholtz

      We will have more to share on URLs soon 🙂

  • Sagiv Frankel

    Warning – rant ahead… Ive been using Ionic for more then 2 years. The Ionic team has always been very hard working and Innovative, but the constant breaking changes have been a serious set back to my productivity.

    Breaking changes are sometimes a necessity and sometimes not a necessity but still a good call. But I’m afraid you’ve dropped the ball on this gulp and rollup change In my opinion. For a few reasons:

    1. There are already lots of breaking changes In this release, this adds more that are not a necessity.
    2. It would have been nice to get a heads up and more conversation from the community before pushing this in.
    3. You say we can still use Gulp but thats beside the point. Ionic is/should be more then a UI framework. it should be a build tool of it’s own and as we have seen before once you deviate from the main path, your in for a world of hurt and zero support. Switching away from Gulp is a pain for me personally as I have some custom stuff like custom Icon building ionic2-custom-icons/gulp-plugin, custom scripts and so on.
    4. Gulp is battle tested, easier to debug then npm-scripts, more people know it and has a rich plugin ecosystem. Now on top of anguIar2, Ionic2, Typescript, Webpack I also need to learn Rollup 🙁
    5. I’m not against learning but part of the promise with Hybrid apps was to leverage existing knowledge. Seems like this has been completely forgotten.
    6. Isn’t The angular team going for Webpack? why not consolidate?
    7. If the fact that the product is in beta legitimises every single change, my conclusion would be never ever use a beta product and that’s a sad conclusion.

    So in conclusion. please please please, stop breaking every single peace of the tool chain every other day.
    I know I sound tough but just like my boss expects me not to spend my time on fancy new tools every other day, I hope you guys treat us the same. Hybrid development is challenging enough already…

    • Andreas Hegenberg

      Sorry, but your own conclusion is correct. Don’t use beta software if you can’t handle breaking changes. Ionic 1 is perfectly fine if you want to leverage your existing knowledge.
      The Ionic team clearly communicated that things will change and I really like what they are doing with this new version. Webpack 2 isn’t stable yet and treeshaking is important to improve performance.

      • Sagiv Frankel

        Your probably correct, that’s a mistake I will never make again.
        That being said my frustration is with the fact that things use to brake a lot with Ionic1 and when it finally started stabilising they jumped to Ionic2.
        Frankly Ionic1 is not up to par. The UI kit is stable but all the stuff around it is not, so staying on Ionic1 is not a very good option either.

        Almost 3 years of having stuff change left and right. I don’t think the Ionic team is to blame, most of there decisions where tough but correct. But since this is the reality I would expect stability to be a higher priority – even in a beta product. I don’t feel it was a good call in this case, but I might be wrong…

        • Andreas Hegenberg

          Mh I never had big issues with Ionic 1 (and I build many apps with it). But of course the code is much nicer now with Angular 2 and Ionic 2.

          I believe that now that Angular 2 is final and Ionic 2 has reached RC, stability will become more of a priority.

          • Sagiv Frankel

            I believe that will indeed be the case.
            Just trying to raise awareness to the problem.

          • Sagiv Frankel

            And I have to say that it’s pretty crazy that a front end developer who wants to use angular2 and Ionic2 (makes sense you probably don’t only do mobile development) – kind of has to know webpack and roollup and npm-scripts and probably gulp and grunt for other projects. Javascript fatigue anyone?

          • Mikkel Bonde Christensen

            And hopefully that will improve the skills of the average front-end developer. No more “I can do jQuery, can I haz job?”, just because you’re seeking a “Javascript developer”

          • yesimahuman

            The goals we had is that you don’t need to know this stuff. We failed in that goal with RC0 as you needed to configure rollup. We are making some changes such that you should only need to know how to run “npm run build” and your app works, leaving it open for you to run other tasks on build. It’s a major priority for us to fix this, stay tuned.

          • Mateo Tibaquirá Palacios

            Definitely, RC is synonymous of Stability, and personally I clap the Ionic Team to make these moves showing good results. Things weren’t decent enough in the Beta to be able to develop competitive hybrid apps.

    • danbucholtz

      We moved away from gulp because it is effectively deprecated. Installing gulp comes with loads of warnings today, and the tool has not seen a lot of maintenance over the past year. You’re free to use it and roll your own build, or even call our build scripts.

      I won’t speak for the Angular team but we settled on Rollup over Webpack because in our testing we saw apps start up in about 350ms with Rollup and 1150 with Webpack. Nolan Lawson did a great post on it here:

      As for the breaking changes, there may be a few small ones but the big ones are out of the way.


    • u_glow

      I agree that not using Webpack 2 – as Angular 2 does – is not a brilliant decision. All of the tooling that people had working with Webpack is now useless. Feels like more magpie development on the part of the Ionic team rather than creating some stability before the final release. Just another reason to consider React, I guess.

    • yesimahuman

      Hey Sagiv, thanks for the candid feedback and our sincerest apologies to everyone for the trouble with this release. We have built this release with the goal of moving to a simpler build chain where you can continue to use the tools you want to use but where we have fewer dependencies on things that were constantly breaking underneath us. We think, in the long run, this will lead to fewer dependencies that no longer function due to updates outside of our control, as well as making it easier for us to adapt to changes in the JS ecosystem. To continue to use gulp, just add the gulp build to your package.json under the “build” command in scripts. Npm makes it easy to call other tools when the generic build command runs.

      As for rollup/webpack, we’ve listened to all the feedback over the last few weeks and are currently reconsidering and will have an update shortly.

      Finally, some of the challenge with this release has come from us moving to ngc and Angular AoT which is more strict and slower than before. While this gives us an improved boot time, it comes at the expense of a slower debug cycle and adds another tool with its own opinions. This is an issue across the Angular ecosystem and is not localized to Ionic. We’re working with the Angular team to share our thoughts and figure out ways this task can be improved.

      Again, I’m very sorry about the trouble and we have been listening to all the feedback and we are making changes as we speak.

      • Mateo Tibaquirá Palacios

        Rollup seems like a good move IMHO, the bundle size is a big issue and people usually complain without enough experience. Keep up the good work 😀

      • Sagiv Frankel

        Hey Max,
        Thanks for listening and responding.

        I feel stability and continuity are extremely important, I really don’t mind which build tool is chosen as long as things are stable.

        One more thing to think about:

        We all want Ionic to succeed – your success is out success and vice versa.

        From what I know a big part of Ionics business model is the Ionic cloud.
        Most paying users of the Ionic cloud will be big apps that have a long lifetime and lots of traffic. These type of apps are the ones that need stability more then the other one off apps which are able to be changed.

        Thats also why Ionic native is a huge win and kudos on that!

        Each day I spend changing my build and dealing with compilation errors is a day my business/startup is not moving forward and a day less I am able and happy to pay for the Ionic cloud 🙂

        Thanks again,
        and lots of luck with you tough but challenges ahead.

  • 0v3rst33r

    I am 90% done with porting our app to the RC (been busy 7h straight). To the Ionic guys: GREAT JOB! My initial tests on an Android P8 Lite already indicates that things have sped up at least 3 times. I kid you not, this is a project life saver!!

    • danbucholtz


  • Gregor Srdic

    step “9. Remove any use of the providers, pipes and directives entries in @Component, and their corresponding import statements, from your pages.” confused me, because of the removing imports for providers I thought there is some other way to access them in your components. Obviously you need the import, if you are going to access the provider in the constructor?

    • Henrik Merlander

      +1. Wonder if there is something I missed…

  • ekoz

    o/ Awesome! I can now sell my house to finance my revolutionary app 😉 the day has come 🙂

  • Obi

    Interesting. Can’t wait for the final release. I have an upcoming mobile app project, and I don’t want to use a release candidate for it.
    Then again, if I do decide to go ahead and use this RC for it, do you know what’s involved in upgrading to the final version once it’s released?

    • danbucholtz

      We have all of our major breaking changes in. There should be minimal, if any, breaking changes.

  • William Vega

    It is amazing. I was expecting to see a beta 12 before even thinking in a RC0. However now that the final release of Angular 2 is live, I imagine that very soon we will have a final Ionic 2 release! woo-hoo! hopefully we won’t see many breaking changes from this point which would be awesome.

  • Marco

    I started a boilerplate to enhance this rc with karma tests, e2e (not implemented yet), envs injected, and other stuff.
    Hope it helps to get started faster after those big changes.

    • danbucholtz

      Way cool!

  • abets

    Nice 🙂 Cheers.

  • jolver

    I can not install ionic 2: this error
    Installing npm packages…
    Error with start undefined
    Error Initializing app: There was an error with the spawned command: npminstall
    There was an error with the spawned command: npminstall
    Caught exception:

    Mind letting us know?

  • Guilherme Rodrigues

    How do I disable typscript for this new version? I want to build my app using js instead of ts.. hanks

    • danbucholtz

      We are only intending to formally support Typescript as of right now. Many of the features from Angular like AoT require Typescript.


      • Eyad Alshabaan

        so I can only build apps on Ionic 2 using typescript? I cannot use just JavaScript as in ionic 1?

  • Sridhar Tirumala

    is the latest beta version is @2-beta.39 or higher?

  • Jose Vargas

    How I can debugger in this new version ???

  • Siyu Zhang

    my global.scss is not working… Plus, it seems to me that customizing html tag is no longer possible and I can’t use ion-content as a tag in my css.

  • Umashankar Arora

    Congratulations Ionic Team.

    I have an issue with this build, don’t know what I am doing wrong. My rest is returning response in hindi which was getting displayed in previous version but now it is not. Not sure what I am doing wrong. In index.html I have defined.

  • Mat Bettinson

    Congratulations, I continue to be blown away by your efforts.

    I’m hoping there’s some payoff to rollup that isn’t apparent to me now. Took me six hours just to figure out how to get firebase and rxjs working right, complete with hacks directly into ionic-app-scripts. Still, that’s the price of the bleeding-edge eh?

  • zenw0lf

    Thank you!

  • Ron Farko

    Congrats to the Ionic team! I’ve been waiting of this moment for months. After reading your blog I was so excited to start learning about the new Ionic 2 but I couldn’t find any tutorial!
    is there an updated tutorial and starter templates to help us learn Ionic 2?

  • Tiago Silva Pereira

    Congratulations Ionic Team!!
    If i update the Ionic, but not my app (beta 11), this runs correctely? Because I need time to make tests, and I need maintain my App, that in the moment uses beta 11.
    Thanks a lot!!

  • Lucas Conrado

    Awesome, I’m here in Brazil waiting anxiously for the stable release of ionic 2!

  • Appie

    How many release candidates are we going to have? Because the transition from beta 11 to RC 0 has been very painful, and I would like to have some light shed on how the transition might look like from the last RC to the final release.

    • Mateo Tibaquirá Palacios

      don’t compare the pain of the BETAs with the RCs, I’m sure the final release will be painless to move from any RC, that’s the idea of software development. I think the “hard moves” were done releasing the RC.0 and moving to Rollup, etc. Have fun

  • Illimitato Dal Vivo

    Amazing!!! i began early a project using the last version of ionic but i felt disappointed because ionic does not supports NgModule, so i start to work using my own modular system, luckily i stopped the project, but now with this improvement i can now work my modules like i want!! very thanks by her continuous work, keep forward 😀

  • Anuranjan Srivastav

    Thank you so much Ionic team..

  • Himanshu Upadhyay

    Hello Ionic guys,
    Brave work…
    Any idea when you guys will be rolling out the GA.?