Over the past several months, the Ionic team has been hard at work on the next generation of Ionic. We took everything we learned from building Ionic 1 and made significant improvements to the way Ionic apps look, how they perform, and their ability to adapt to future technology shifts. If you’ve been paying close attention, you may have seen us sprinkle a few hints here and there about the next generation of Ionic, but for the most part, we’ve stayed relatively quiet about the next version of Ionic.

Today, all of that changes. We are thrilled to announce the official Ionic 2 Beta release and the release of our all-new docs!

The Ionic team spent the better part of 2015 on Ionic 2, and we’re so excited to open it up and share it with you. In Ionic 2, we’ve focused on performance boosts, architectural improvements, cross-platform theming, support for Angular 2, support for the mobile web, and so much more!

It’s the best version of Ionic we’ve ever made, and we know you’re going to love it.

Why Ionic 2?

It’s been so humbling watching Ionic take off around the world. When we started working on Ionic in 2013 (when iOS 6 was king, and Android 2.3 was still a major factor), we had few mobile-focused browser APIs, some seriously underperforming devices, and a crazy vision of bringing the web to native parity on mobile. In hindsight, it feels like we had so much stacked against us.

Fast forward just two years, and so much has changed! Browser APIs and devices have drastically improved, and the hybrid approach to building native apps has been validated. Ionic has seen widespread adoption, with over 1.9 million apps built by everyone from individual developers to small startups to large enterprise businesses from around the world. Ionic is one of the top open source repositories on GitHub and powers some incredible apps. A few of our favorites include the official app of the Rio 2016 Olympic Games, Sworkit, the New York MTA Bus Time app, Adobe Social, Meerkat Movies, Card.com, and our very own Ionic View (to name a few!).

With all those apps and your feedback, we’ve learned a thing or two about how a great web-based mobile framework should well…work! Let’s dig in and see exactly how Ionic has changed:

Angular 2 Power-up!

One of the single biggest improvements to Ionic 2 is the way it leverages the power of Angular 2. We’ve been fortunate to have the opportunity to work closely with the Angular team and build Ionic 2 with their weekly feedback. Angular 2 brings incredible performance boosts, especially to mobile, and we think you’re going to love it.

Along with a significant bump in performance, Angular 2 brings a simpler, more standard way of building Javascript apps. Angular 1x was developed back in 2009, before ES6 and before the modern JS app that it pioneered. Unfortunately, that meant a lot of custom approaches to things like state management, dependency injection, components, and modules. These custom solutions are no longer necessary with today’s JS standards.

Today, an Ionic and Angular 2 app is just TC-39, standards-compliant JS. While it may look different from what you’re used to, the benefit is the entire web industry is moving towards this standard set of technologies, so your skills will adapt to other projects beyond Ionic and Angular 2. That wasn’t the case with Angular 1.

A lot of developers are worried about their Angular 1 skills transferring over. I think it’s important to realize that Angular is largely a set of opinions around how JS apps should be built. Those opinions are still the same despite a change in underlying implementation and language. We still store state on our components, use HTML in our templates to render them, and use familiar “directives” like ngFor (new ngRepeat), ngIf, etc. We’re finding that ng1 developers pick up ng2 quickly because the core concepts are the same.

There are some other big improvements that Angular 2 gives us that we will be taking advantage of down the road, including server-side rendering, cross-platform views, and web workers for improved performance. Stay tuned for those updates in later Ionic releases!

Overhauled Navigation

Few things have changed as dramatically in Ionic 2 as navigation. In Ionic 1, navigating between a standard page and a tabbed page was particularly difficult, and trying to navigate to the same page from different pages involved duplicated code and complicated UI-Router definitions. Trust us, we’ve felt your pain here.

Navigation in Ionic 2 is easier, more powerful, and much more flexible. It now works like a stack—you push a new page onto the stack to go to it and pop from the stack when you want to go back. Pages can be nested infinitely and a page can live anywhere in the app without having to define unique routes for it as in v1. For example, navigating inside modals and tabs Just Works with zero extra router configuration required. Hurray!

Since Ionic 2 treats all pages the same, you can navigate to a page from any other page. This resolves a ton of the problems we had with the Ionic 1 router navigation. Pages are not tied to specific URLs. However, if you’d like to continue to use a router, Ionic also supports the URL-based Angular 2 router.

For way more info on the new navigation changes, see the Navigation docs.

Side Menu Improvements

Using a side menu in Ionic 1 required the content to be wrapped by the side menu structure, which made it difficult to use multiple side menus, or to combine side menus and tabs together. Ionic 2 completely restructured the side menu so that it’s a sibling to the content. Now you can have as many menus as you’d like, reference a menu from anywhere in the app, and enable or disable specific menus!

Side menus are also customized to look and animate uniquely, depending on the platform they’re running on. There are now three types of menus available, including the Android “overlay” style. The default menu for each platform is different, but still highly configurable.

Learn more about the new Menu component on the Menu docs.

Platform Theming and Continuity

By default, Ionic styles the UI components based on the platform in which it’s being displayed, in order to provide users a familiar native experience. We want developers to be able to write once, deploy everywhere, and have the visual experience feel right at home, regardless of the platform. We call this Platform Continuity.

Ionic 2 takes this concept to a new level. We streamlined and simplified our iOS-styled components, and brought Material Design support front and center for Android apps. We’re especially excited about this, because full support for Material Design styles is a long-awaited, much-requested feature!

Alongside the visual changes are some awesome new and/or refactored components, like alerts, segment control, search bar, tabs, and select inputs. To see what we mean, checkout the new Component docs, and toggle the preview device to Android mode.


We built Ionic to be a blank slate that you can easily customize and modify to fit your brand, while still following the standards of each platform. We believe the best apps in the app stores are fully customized, and we want to make it easy for you to do the same with your apps.

We worked to make theming Ionic 2 apps easier than ever. Since Ionic is built on top of Sass, we’re able to set some default styles for your app but also make it extremely easy for you to change those defaults (and that’s the point!). Theming your app to match your brand is as simple as changing the pre-defined colors for the app. Basically, we define a few “starter colors” for you, but these can all be removed or renamed to just about anything you want. Some Ionic 2 components will even change their style based on the color specified to them, which makes customizing your app across multiple platforms super easy!

You can easily customize the styles for each platform by changing the default value of a Sass variable. Many of the platform variables get their values from a shared variable, so in certain cases, you can change one variable and override the style on all platforms. The application can further be customized by setting the configuration. Change the back button text for a specific platform, set the tabs to the top for iOS…the possibilities are endless. The Sass files themselves are even more modular now, allowing you to import one component at a time, if you want to.

To get started theming your Ionic 2 app, take a look at our new Theming docs.


Ionicons 3.0 is now live and its own NPM module! We overhauled the whole project, and there are now over 900 icons. Ionicons is MIT licensed and can be used on its own or inside any number of Ionic UI components. One awesome new feature that comes with Ionicons 3.0 in Ionic 2 is that the actual icon can change, depending on the platform from which the app is running.

For example, by simply using the “home” icon, Ionic will automatically show the appropriate icon, depending on the platform. Android devices will display the Material Design home icon, and iPhones will display the iOS home icon. This one-for-one icon match to each platform is yet another feature that makes it easier for developers to quickly create a familiar experience for users.

To use the new Icon features and see the whole set of Ionicons, check out the new Icon docs.

Build Tools

We want to make sure Ionic developers can get up and running fast with the Ionic build chain, but it’s no secret that the JavaScript community has seen an onslaught of new tools this past year. Trust us, we have been experiencing this firsthand as well! With modern JavaScript and all the cool new possibilities that come with it, it can quickly become overwhelming just to understand what tools you need, why you need them, which ones are recommended, and which ones are even compatible with others.

This is a major way in which we feel Ionic adds value: by providing an organized build system based on our experiences of what works best, so you can worry about building your app, rather than wasting time wiring up tooling. If things change in the build tool space down the road, Ionic will adapt to give you what we think is the best set of build tools for building Ionic apps.

That’s why all of our starters come preconfigured and ready to go with the Ionic CLI. Each starter uses Webpack for bundling and transpiling, Sass for CSS compilation, and NPM for package management, along with TypeScript, if you want it, or vanilla ES6/ES2015, if you don’t. New to some of these terms? Head over to our Glossary for a comprehensive list of many of the technologies involved, and stay tuned for an upcoming blog of why we chose the tools we use.

Along with the changes to Ionic tooling, there are some exciting features coming down the road from our friends as well. While still relatively young, we’re looking forward to the Angular CLI streamlining the development workflow and making packaging lightweight apps for production extremely easy. We’re excited to be working with the Angular team to ensure that Ionic 2 and the Ionic CLI maximize the benefits of the Angular CLI.

On the IDE front, because Ionic 2’s core is already built using TypeScript, the framework comes with support for powerful editor features like Intellisense out of the box. We’re happy to say we’ve been working with Microsoft to make the development experience for Ionic 2 with Visual Studio and VS Code as easy and powerful as possible, with more exciting improvements planned.

Web all the way down

It’s no secret that we’re passionate fans of the open web at Ionic. We think one of the most important technological efforts today is in bringing open web and browser standards to parity with native, proprietary mobile technology. If mobile continues to dominate as the primary way people spend their computing time, it’s crucial that apps can be built in an accessible, standards-compliant way that works on all mobile devices, not just a chosen few. We’re proud that Ionic is based entirely on open web technologies, and we are doubling down on this.

Going forward, we’re making the mobile web a first-class platform in Ionic. Any Ionic app today will work as a mobile web app with zero code changes required. We are working on a new web-based theme to adapt to some of the intricacies of mobile web browsers, but we’re already seeing major brands use Ionic for mobile web apps today.

This is especially important today as Google starts to prioritize sites that provide great mobile web experiences. For example, if you use app download interstitials instead of a mobile web app, Google will no longer consider your site mobile friendly which could severely impact your search engine ranking. Additionally, Google is adding new features in Android to allow mobile web apps to function as native apps, and we are working hard to make sure Ionic can thrive with those changes.

Ionic is pretty much the only major mobile framework out there that lets you adapt your app to the app store as a native app and put it on a web server to provide a great mobile web experience with no changes required. We’re proud of this and want to do more to make the mobile web a top Ionic platform. Stay tuned for that!

But Wait, There’s Moar!

There are just too many changes to talk about in depth here, so we’re going shorthand on these honorable mentions, all of which deserve their own blog post:

  • TypeScript support – Optionally write your project using Typescript. We find this is a major benefit for large apps and teams.
  • ES6 – The new version of JavaScript. You might find yourself wondering WTF you’re looking at, but what you’re really seeing is the next version of standardized JavaScript.
  • Animation System – Completely revised, customizable, and highly performant animation system.
  • Ionic Native – A thin wrapper for Cordova plugins, so you can easily import and wire up native functionality.

Looking Ahead…

We have a ton of features in store for Ionic 2 and couldn’t resist offering you a sneak peek…

  • Windows 10 – platform continuity support, with Windows-specific designs.
  • Webworkers – Multithreaded JavaScript! Essentially places the app’s logic and renders the UI onto two different threads.
  • Further performance improvements – in both Angular and Ionic. Additionally, Angular 2 itself is in beta, with many large performance improvements on the way, such as:
    • Offline template compiling: Compiling templates in a build step, not on runtime.
    • Drastic file size reduction: The Angular team has a stated goal of bringing their Hello World app down to a 10KB payload size.
  • Extra Themes – Currently, there is only the default theme, but we will be adding more, such as a dark theme, with the ability for users to contribute their own.
  • More – For more information about what’s next, we recommend taking a look at our roadmap here.

Thank you!

We wouldn’t have Ionic 2 to share if it weren’t for the community’s incredible embrace of Ionic. There are over 150 worldwide meetups, an extremely active forum with hundreds of thousands of registered members, nearly 5,000 members in our Ionic Worldwide Slack channel, many online courses, books, and more. You are the reason Ionic is such an inviting and supportive community and we are so grateful for your support.

Also, I want to give a huge “congrats!” to the Ionic team. It’s been an incredibly challenging and exciting few months at Ionic, and I’m so proud of your hard work and hustle to make Ionic 2 a reality. There will be bubbly!

Now, go take Ionic 2 beta for a spin! Check out the new Getting Started docs, and read up on all the new APIs. Make sure to submit any issues to us through our Issue Form. We welcome any and all feedback and welcome your assistance as we make Ionic even better!

P.S. Check out a very special Ionic Show covering the Ionic 2 Beta!

P.P.S. We’re hiring if you want to come help us build awesome things like Ionic 2

P.P.P.S. We’re hosting a live Q&A tomorrow on Blab at 12:00PM CST. Come by and say hi!

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

  • http://www.pdsullivan.com Patrick Sullivan

    Very exciting. Great job ?

  • Anze Klancar

    Wooow, that’s huge! Super excited about nested views and navigation improvements! Can’t wait! ?
    By the way, with Olympic Committee of Slovenia, we’re also building mobile app with Ionic! Any feedback will be really appreciated.

    Check it out here: https://itunes.apple.com/si/app/team-slovenia/id535486258?mt=8 or here https://play.google.com/store/apps/details?id=si.datastat.oksoi2012&hl=en

  • http://www.insightiitb.org/ joy014

    Sorry for stupid question but Is Angular 1.x supported in ionic 2.x or it is exclusive Angular 2?

    • yesimahuman

      Right now it’s exclusively Angular 2. However, we are thinking about ways to possibly bring ng1 support to ionic 2. Long ways off though (if ever)

    • Oscar Perez

      Hi joy014, I think your question is not stupid, I’m asking the same one but I guess does support it because you choose the Angular version in the dependencies files, so I think you can… hoping to receive a confirmation from the big guys, otherwise you can try installing Ionic 2 and add Angular 1.x files.
      Hope this helps

  • http://yahyazini.com/ Yahya Zini

    Wow guys, really excited about this. Keep up the hard work and thanks a lot for this awesome framework!

  • http://www.be-codified.com Žiga Vukčevič

    Great job! 🙂

  • Emerson Thompson

    Yuuuuuuh! very nice, great job ionic team!

  • http://www.ian-b.com Ian Brown

    Totally stoked!!

  • http://ardalan.me Ardalan.me

    I took a look at the top reviews on your “favourite apps”.

    Rio 2016 Olympic Games (ios): “1/5 — Almost nothing in this app works. Tap anywhere, and 99% of the time either it doesn’t work the way it should, or it does’t work at all. It’s really too bad. They obviously were unable to hire competent developers.”

    Rio 2016 Olympic Games (android): “1/5 — Doesn’t accept info then locks”, “3/5 — Not able to see or update my profile”, “1/5 — I am so disappointed!! I was so excited about this app. I have a Galaxy Edge. So far everything I try to do in the app results in my screen freezing. (Complete my profile, click the link “like” a FB page) I have to reboot my phone to shut it down. Boo!!!”

    The New York MTA Bus Time app: Overall rating 2.5/5

    Adobe Social: “not enough ratings”

    Meerkat Movies: “4/5 — Can’t login Usually love this, so easy, wanted to go to the cinema tonight and every time I click ‘login’ it says there’s a problem. Clicked on the link to reset password and that says unavailable also.”, “2/5 — Selected the product I have purchased and will not activate my tickets for me. Not a very good sight. Will not use this sight anymore as it has been brilliant in the past”, “3/5 — It is good when it’s working. I tried uninstalling and re-installing but it still won’t connect – message says loading problem.”

    Card.com: Seems to be doing okay. 4.2 overall rating.

    Would you admit that the performance of Ionic Framework 1 is very inconsistent across devices? I hope you would, because that’s the first step you had to take in order to fix it in v2.

    • Steve S

      I’ve used Ionic and had none of those problems. Are you sure it isn’t stupid developers that are the issue here? I haven’t had performance issues either; I haven’t used Ionic to create real fancy apps, but everything is responsive to taps/drags/swipes. I need to include fastclick.js – but that’s true of every project I’ve done, and it takes a mind-boggling five seconds to add fastclick to a project.

    • Volodymyr Bilyachat

      I cant tell you one thing. I have seen many apps slow apps they were written in different platforms. So what i mean if developers hand growing somewhere from ass this app will be shit.

    • Henrique de Castro

      The WebService of Rio 2016 Olympic Games is down, that’s all. The problems cited by the users have nothing to do with the Ionic.

    • Young Park

      Not all ionic apps have bad ratings… check this out:

      One Verse Bible 4.8 average – built with cordova / ionic 1


      • Young Park

        To make better ionic apps, understanding cordova is critical.
        Most hybrid developers I’ve seen they don’t think of having two different versions for android one for x86 and another one for armeabi-v7a

        That’s why people are complaining that their device is not supported. if x86 is not supported 10% of your users will complain.

    • Palle Simonsen

      The Rio problem might be a failure to check for WebService availability and perhaps caching on the device to overcome availability issues – i.e. a developer issue.

      Can recommend the ng local storage lib for caching if you need a very fast way to cache webservice results between invocations.

  • David Vera

    You are amazing! Great Job!

  • Gurbakhshish Singh

    I was about to start on our startup MVP app in ionic 1.2. Is v2.0 stable enough to make the app in it instead of v1.2 ??

  • Gurbakhshish Singh

    I want to create a MVP app using Ionic for a personal project that i am working on. Is it too soon to chose v2.0 for this ??

  • http://kylefox.ca Kyle Fox

    Ionic2 looks simply awesome, great work Ionic team! ?

    One thing I’m curious about (since I haven’t it it discussed much) is testing Ionic apps. I know testing is a pillar of Angular (https://angular.io/docs/ts/latest/testing/) but I haven’t seen it talked about much in the Ionic community. It would be great if there was an “opinionated” approach to testing & tooling baked into Ionic2.

  • Jack Guy

    This looks fantastic! To those of you who are skeptical about Angular 2 – it’s tricky switching over at first but once you get the hang of things it really is a fantastic tool to work with. Plus it sounds like Ionic is handling the tooling for us which takes away half the battle. 🙂

  • Andreas Strauß

    can ionic1 projects been easily updated ?

    • Dennis Bishop

      In my experience over the last week… No

  • nerdcombr

    Awesome job! Thank you!

  • Lars Jeppesen

    Congratulations, guys!! Amazing job!

  • http://blog.oxiane.com Alain Boudard

    So excited with ionic native ! i mean … like I’m already crazy of the whole ionic 2 anyway 🙂
    You rock guys !

  • http://ronanconnolly.ie Ronan

    Great job guys, I’m looking forward to making some apps with the V2!

  • Gabriel Santos

    Yes, fucking good, indeed.

  • Inspired

    Woo Hoo! (very exciting!)

    Thanks Ionic team for being awesome.

  • Darryl D

    Nice job. Only reason I still entertain the use of a angular 2 is ionic.

  • Kyle Roach

    Finally!!! Native material design support. I had to use angular material with ionic, but I had to override a lot of css. Thanks guys!

  • ThomasDalla

    Great news!
    Any plan to provide Polymer components as well?

  • Sean Hill

    It seems the Ionicons are not compiling 🙁

    ✗ node_modules/ionic-framework/fonts/ionicons.scss

    Error: File to import not found or unreadable: ionicons-icons

    Parent style sheet: ../node_modules/ionic-framework/fonts/ionicons.scss

    on line 9 of node_modules/ionic-framework/fonts/ionicons.scss

    >> @import “ionicons-icons”;


  • Sean Hill

    Is swipe to go back still disabled?

  • http://chariotsolutions.com krimple

    Congratulations Ionic 2 team! Now a Reactive data tracking app I’ve been working on with Angular 2 will be something I will try on Ionic 2!

  • https://www.noodl.io Noodlio

    I can just say… wow!

    Just a small thing: where are the Ionicons of v3.0? The current Ionicons website shows that v2.1 is the latest.

  • Saber Alyousef

    CLI generate command need –ts option to generate TypeScript new page.

  • saoron

    Awesome! Great job!

  • Aderito

    I’ve been using Ioinc 2 for two weeks now. It’s super fast and snappy on my iOS device but just when I started to have a look at it on Android, it’s HORRIBLY sloooooow! It doesn’t even do much, it’s mostly UI

  • guy katz

    I have been a long time user of sencha touch and I love and appreciate everything they did. some issues came up with regard to licensing etc as they changed their model.
    my app is a production app built with PGB using mainly push notifications plugin.
    is this a good time to start and develop using ionic 2 and port my app? should I wait a bit?

    • Simon Lucas

      I would start now, I tried migrating a few of my Sencha Touch projects and it was actually pretty easy once you get ur head round the structure. It really is an awesome framework I wouldn’t wait! I’ve also jumped ship from Sencha (think I recognise you from the sencha forums actually, gkatz right?)

      • guy katz

        yeah Simon that me 🙂
        I do not have any ionic 1 nor angular experience. did you have any? what would you say your learning curve was?

        • Simon Lucas

          Thought so! My username is digeridoo on the sencha forums :-). It’s so quiet over there now I thought I’d join the fun over here! Feel free to message me and we can share some code if you like. I had no angular experience before, although I did learn Ionic 1 and built an app using it. I got up to speed much quicker than when starting out with Sencha, but I think knowing Sencha Touch helps with the learning curve :-). Took me about a month, but I’m not at advanced level by any means!

  • http://www.fadamakis.com/ Fotis Adamakis

    Impressive! Hope it matures well.

  • Sagiv Frankel

    This looks promising 🙂 best of luck.

    I’m a little surprised “Ionic Native” is last on the list though.
    This has been the biggest issue I’ve had with Ionic 1 by far. It seemed like every other week I started working some other plugin was broken or incompatible. The story around moving from the browser to native with the plugins (ng-cordova-mocks) was very unclear and also missing a lot of the times…

    • yesimahuman

      We are making it a major focus going forward to support cordova plugins. We are hiring right now to make that happen, since we realize it’s a major liability for Ionic when community plugins don’t work.

      • Sagiv Frankel

        Thanks for the reply! It’s great to see you so involved and open for feedback, keep it up, it’s awesome! (P.S. being hired by Ionic/Drifty sounds awesome to 🙂 ).

  • Artur Denth

    I saw Ionic the first time at version 0.3 and fallen in love with it (objective c was a nightmare). Great job guys!

  • Luís Cunha

    yes, gimme them performance improvements

  • Wolfgang Born

    Amazing job! Congratulation to all Ionics ?
    My first app was build with Ionic1 but since this is just a little app, I will move on to rebuild the app on Ionic2 and Angular2:
    Thank you!

  • Francesco Ostili

    Great job guys! ?
    One question: is it possible to build a complete and stable application with Ionic 2 (and Angular 2 too?)?
    I’m starting a project and I don’t know if I should start learning Ionic 1 and Angular 1 or just skip them and jump to the version 2 of both ?

  • Toni Lähdekorpi

    Still can’t swipe to change tabs though. This is just stupid.

    • yesimahuman

      That’s in the roadmap above. ?

      • Toni Lähdekorpi

        I’ve been considering this as a bug since 1 alpha.
        When testing the UX with users the first thing _all_ test subjects did (in Android) was to try swipe to change the tab.
        Effectively it’s broken.

        • yesimahuman

          Stay tuned, it’s a priority for us on v2

  • Sagiv Frankel

    I really hope Ionic makes it big time!
    The world will be a better place if open web standards provale over vendor specific ones. The native javascript (React native, Nativescript…) are fine solutions, but going web all the way should be the solution for most cases. Go Ionic!!!

  • Carl Paradis

    Will there be anymore ionic 1x updates after this release is not in beta? Some of us that use other 3rd party angular 1x libraries will not be able to switch to angular 2 easily, so continued improvements/updates to the ionic 1x project would be appreciated.

  • LM

    Great job!

    Is there a release notes page somewhere to follow Ionic 2 updates?

  • mt_nasty

    You guys are the best.

  • lricoy

    Great job guys! Starting to test it right now.

  • Rohit Chatterjee

    Looking forward to exploring this! Thank you and congratulations

  • Ludovico Loreti

    Thank you guys!

  • Tommy R. Williams

    Has anyone successfully gotten Ionic 2 + cordova working in ios emulator? Seems that no one can figure out the list of errors that are coming about. Any Ideas? http://stackoverflow.com/questions/34058245/ionic-2-an-error-occurred-trying-to-fall-back-to-cordova-lib-execution-typeer

    • Tommy R. Williams

      FWIW, Seems it would only play well with cordova 4.2 (not 4.7 or whatever I had previously installed)

  • satwaya

    Waiting for this new incoming crazy update!
    Good job guys!

  • Indy Lawi

    Awesome….Support for Google Material Design too.. Wow
    Great job guys! With Ionic 2 and Angular 2 the line between hybrid and native mobile app is further blurred. This is magic!
    Can’t wait to give Ionic 2 a spin.

  • brace110

    Awesome, too bad I just got used to Angular 1, back to grind I guess.

  • PatrickMcDonald

    Your success isn’t humbling. Your misuse of the word is.

    Otherwise, nice job.

  • http://www.anasoru.com/ Onur

    hhhh nice

  • http://chimezieenyinnaya.com Chimezie Enyinnaya

    Great! Heard about ionic just recently and I will like to explore it. Is it advisable to start with v1 or just head straight to v2. Also any idea when v2 will hit stable.

  • John

    Looking forward to the windows support to round things out.

    Might be just me but I couldn’t get the ios app to run because of file permission issues. I deleted the platform and added it via cordova directly and was able to run and build without issue.

  • Augusto Gonzalez

    Where can I download it?

  • Christian James Lourenço

    Amazing!!! Great, great job!!

  • සුපුන් පෙරේරා Supun Perera

    Great news!

  • nerdcombr

    Any loading component like $ionicLoading?

  • ZiLang

    I can’t install. Got the following error message: (sudo npm i [email protected] -g)

    npm ERR! Darwin 15.4.0

    npm ERR! argv “/usr/local/bin/node” “/usr/local/lib/node_modules/ionic/node_modules/.bin/npm” “rebuild” “node-sass” “spawn-sync” “fsevents”

    npm ERR! node v4.2.4

    npm ERR! npm v2.14.21

    npm ERR! path /usr/local/lib/node_modules/ionic/node_modules/.bin/node-sass

    npm ERR! code EACCES

    npm ERR! errno -13

    npm ERR! syscall unlink

    npm ERR! Error: EACCES: permission denied, unlink ‘/usr/local/lib/node_modules/ionic/node_modules/.bin/node-sass’

    npm ERR! at Error (native)

    npm ERR! { [Error: EACCES: permission denied, unlink ‘/usr/local/lib/node_modules/ionic/node_modules/.bin/node-sass’]

    npm ERR! errno: -13,

    npm ERR! code: ‘EACCES’,

    npm ERR! syscall: ‘unlink’,

    npm ERR! path: ‘/usr/local/lib/node_modules/ionic/node_modules/.bin/node-sass’ }

    npm ERR!

    npm ERR! Please try running this command again as root/Administrator.

    npm ERR! Please include the following file with any support request:

    npm ERR! /usr/local/lib/node_modules/ionic/npm-debug.log


    throw err;


    Error: Command failed: npm rebuild node-sass spawn-sync fsevents

    at checkExecSyncError (child_process.js:464:13)

    at execSync (child_process.js:504:13)

    at Object. (/usr/local/lib/node_modules/ionic/lib/tasks/postinstall.js:9:1)

    at Module._compile (module.js:435:26)

    at Object.Module._extensions..js (module.js:442:10)

    at Module.load (module.js:356:32)

    at Function.Module._load (module.js:313:12)

    at Function.Module.runMain (module.js:467:10)

    at startup (node.js:136:18)

    at node.js:963:3

  • medwin


  • http://base2industries.com/ Michel H.

    I am definitely going to observe the shit out of Ionic2! Good job!

  • muzi jack

    i’ve created a blank app and a template with ionic creator. template is @ “www” dir but it can’t be build since its not under app dir and problem is when i copy the template to app dir app doesn’t buid -Please help

  • Divi

    Hi friends,
    any one aware of stable version release of ionic2? …Is it preferable to start the project for banking sector including financial transactions using ionic2 and angular 2 platforms..pls anyone suggest