51–60 of 82 posts
No body mentioned but Ionic Creator[1] still supports Ionic 1. I think it is great tool to start an app from scratch but it doesn't look cool when your own tool doesn't support your own latest product. [1]: https://creator.ionic.io/
We used Ionic 1.x for a few projects. We found that for relatively basic, brochure-ware apps, it worked just fine. However, for some of the more complex apps, we really fought the lack of support/options in the Cordova plugin space. This, of course, is not the fault of the Ionic team, but it does create a frustrating development experience that played a large part in us abandoning it as an option. This was also our f…
We used Ionic 1.x for a few projects. We found that for relatively basic, brochure-ware apps, it worked just fine. However, for some of the more complex apps, we really fought the lack of support/options in the Cordova plugin space. This, of course, is not the fault of the Ionic team, but it does create a frustrating development experience that played a large part in us abandoning it as an option. This was also our f…
Earlier quoted context omitted.
I was really very well impressed by the small size of ionic apps. It's in the order of ~3MB which is great. But the startup times are somewhat big. I'm talking, for the simplest of applications a startup time of ~5.5 seconds in ionic 2 (the beta) vs ~2 seconds in React Native in Android. For me, that detail has a significant impact in usability. Any plans to work on those startup times?
Disclosure: I also work at Ionic So start up time is something that we are very focused on at the moment. Especially on the PWA side of things, TTI (time to interactive) is exceedingly important to ensure a good user experience. We are working on a few things at the moment but most likely the first one to hit is gonna be code splitting. So with code splitting, instead of shipping just one big bundle you will be shipp…
Ionic 2 has given me two platforms and a great development experience. The few times I've had problems they have an amazing responsive team on Slack that's helped me out right away.
Earlier quoted context omitted.
Disclosure: I also work at Ionic So start up time is something that we are very focused on at the moment. Especially on the PWA side of things, TTI (time to interactive) is exceedingly important to ensure a good user experience. We are working on a few things at the moment but most likely the first one to hit is gonna be code splitting. So with code splitting, instead of shipping just one big bundle you will be shipp…
Well, these are good news. Any timeline to expect the results from this to be suitable to apply in production?
I've been using react-native for the last year and can't say I have much positive to say about it. Honestly, just about every day we hit a sharp pain point in component layouts, broken build scripts due to RN bugs, and runtime crashes. While Ionic 2 is young, I welcome another option to the JS native space. I'm also hoping Flutter.io will get to a stable release.
Check out nativescript. It has 2 versions, one of which is angular2 based. It's pretty neat
Stupid question, but Ionic is not native, or was not at least. But react-native is actually using only native APIs through Javascript. So if you want to have a native look and feel, why not go with react-native?
Ionic is ideal for smaller projects (one to about a dozen developers) or varying skill levels, many of whom already know web development to some level and don't want to have to learn yet another way to do things.
With Ionic, you can use the same code for your website and your android and ios apps, or at least re-use a lot of it easily. This is a big deal to people who want to keep costs low.
If you need serious performance on your mobile app, use react. If you want lower costs, use ionic.
What's the equivalent for desktop site development?