5 ms·

Its pretty stable and very easy to use if you are good with AngularJS .. little bit of confusion around cordova plugins integration but easy to figure out .. Re

by uberneo 12y ago

Its pretty stable and very easy to use if you are good with AngularJS .. little bit of confusion around cordova plugins integration but easy to figure out .. Recently I have developed and app built on Ionic and it works perfectly -- https://play.google.com/store/apps/details?id=com.lowendapp.corkfilmfestival https://play.google.com/store/apps/details?id=com.lowendapp.... .. also its been mentioned on ionic website

xtrumanx 12y ago
It's great to hear that. I got real excited when I first saw it launch on my browser. It felt like Bootstrap for mobile app development. Looks like I figured out what went wrong before and got it running on my emulator and my phone now. Gonna try building something on it.
Bahamut 12y ago
That is not quite true - there are huge breaking changes that are happening quite rapidly with Ionic, especially if you're stuck on head of master due to 1.3 support & other performance issues that force you onto head of master. There's also a steep curve with navigating some of the pitfalls surrounding Ionic if one isn't careful - so much so that multiple excellent developers I've spoken to have decided to fork Ionic & consume the fork along with patches, since they don't seem to consider merging PRs much from the community. I'd say that unless you have some very talented developers and you aren't having to worry about cross-browser issues & commit to exclusively mobile apps, avoid Ionic. There are many pitfalls when you deviate from opinionated conventions, and they can be quite painful to figure out. I spent an hour earlier today trying to figure out an issue where registering a new user was broken due to the new Ionic view caching mechanism - this is quite painful. I would highly recommend waiting for Ionic to hit 1.0 formally before even considering using it to anyone who is still deciding - you'd be better off probably going with Angular Material instead currently. I don't normally advocate staying away from a pre 1.0 release, but with Ionic, I think the warning is well earned - this is also coming from someone on a team where Ionic fit our use case almost perfectly, but were bitten hard when we had to do desktop support along with mobile & various other issues from our design not matching up with how Ionic built things.

by uberneo 12y ago

xtrumanx 12y ago

It's great to hear that. I got real excited when I first saw it launch on my browser. It felt like Bootstrap for mobile app development. Looks like I figured out what went wrong before and got it running on my emulator and my phone now. Gonna try building something on it.

Bahamut 12y ago

That is not quite true - there are huge breaking changes that are happening quite rapidly with Ionic, especially if you're stuck on head of master due to 1.3 support & other performance issues that force you onto head of master. There's also a steep curve with navigating some of the pitfalls surrounding Ionic if one isn't careful - so much so that multiple excellent developers I've spoken to have decided to fork Ionic & consume the fork along with patches, since they don't seem to consider merging PRs much from the community. I'd say that unless you have some very talented developers and you aren't having to worry about cross-browser issues & commit to exclusively mobile apps, avoid Ionic. There are many pitfalls when you deviate from opinionated conventions, and they can be quite painful to figure out. I spent an hour earlier today trying to figure out an issue where registering a new user was broken due to the new Ionic view caching mechanism - this is quite painful. I would highly recommend waiting for Ionic to hit 1.0 formally before even considering using it to anyone who is still deciding - you'd be better off probably going with Angular Material instead currently. I don't normally advocate staying away from a pre 1.0 release, but with Ionic, I think the warning is well earned - this is also coming from someone on a team where Ionic fit our use case almost perfectly, but were bitten hard when we had to do desktop support along with mobile & various other issues from our design not matching up with how Ionic built things.