Live data from Hacker News

Announcing Ionic 2 Final

blog.ionic.io

21–30 of 82 posts

Re: Announcing Ionic 2 Final

#21
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?

Re: Announcing Ionic 2 Final

#22
post #2

I'm always afraid of investing a lot of time into this type of frameworks and then having the rug pulled from under me. Most of the time I spent learning angular ended up being a waste of time and I'm still scarred from then. Also that logo looks familiar?

Curious why you think it was a waste of time. You can still make perfectly functional products using Angular 1, and most jobs (at least in the bay area) won't look down on you if you're not fluent in their framework of choice - they'll expect you to learn it on the job.

Re: Announcing Ionic 2 Final

#23
post #21

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?

I don't think that's a stupid question at all. Ionic uses Cordova [1], which basically launches a browser that runs your web page as an "app". That said, Cordova does give you access to native APIs, so you still have access to Bluetooth/camera/whatever. Phone processors and browsers are getting increasingly powerful, so it's totally possible to achieve native or near-native performance in a web view-based app - assuming you properly optimize your JS and HTML. I believe Ionic provides consistent styling, so it's definitely possible to make your app look and feel like a native one.

The real win using something like Ionic is that you can build your app using web tech that works equally well on the phone or in the browser, and that your developers already know. The trade-off is that it becomes more difficult (but certainly possible) to make your app look and feel native.

React Native gives you many of those benefits, but since it compiles to actual native code you can't reuse your code for a browser app.

[1] https://cordova.apache.com

Re: Announcing Ionic 2 Final

#24
Not long ago I was an Ionic believer, but not anymore... the lack of support for their cloud services [0] has turned many people off and signals that they don't mind leaving their users "locked".

Devs are migrating en masse to react native. I have friends in several startups leaving their jobs because they've been tasked with maintaining legacy Ionic 1.x/Angular projects, while the codebases are migrated to react native...

For hacking quick MVPs is not bad, it was even cool 2 years ago, but for serious projects starting from zero, react native is a smarter choice.

[0] https://github.com/driftyco/ionic-cloud/issues

Re: Announcing Ionic 2 Final

#26

Earlier quoted context omitted.

You're not wrong. I've worked with Ionic v1 a fair amount. The framework is good for mockups and prototypes but nothing more. What ends up happening, as you app grows to include notifications, deep linking, etc, is you need to rely on more and more hacky thirdparty solutions. These days I either code natively or use Xamarin.

You are wrong. I have few mobile apps, made with Ionic and Ionic 2, some have been used on warehouse as part of huge WMS (to scan items and manage whole business process of warehouse worker), some were apps for business as part of CRM (with geolocation, maps and handwritten signatures). And every time product owners were very satisfied with the result and with speed of development. Ionic 1 had too hacky API and not g…

I don't believe I ever mentioned ionic v2... I don't doubt v2 brought many improvements. However you just can't beat the power of not operating in a Webview.

Re: Announcing Ionic 2 Final

#27
post #24

Not long ago I was an Ionic believer, but not anymore... the lack of support for their cloud services [0] has turned many people off and signals that they don't mind leaving their users "locked". Devs are migrating en masse to react native. I have friends in several startups leaving their jobs because they've been tasked with maintaining legacy Ionic 1.x/Angular projects, while the codebases are migrated to react nat…

why use the cloud though? just build on premise and use existing MDM, or App Store

Re: Announcing Ionic 2 Final

#28
post #24

Not long ago I was an Ionic believer, but not anymore... the lack of support for their cloud services [0] has turned many people off and signals that they don't mind leaving their users "locked". Devs are migrating en masse to react native. I have friends in several startups leaving their jobs because they've been tasked with maintaining legacy Ionic 1.x/Angular projects, while the codebases are migrated to react nat…

why use the cloud though? just build on premise and use existing MDM, or App Store

Right, AFAIK the framework itself functions independently of the services, so you can drop in whatever solution you want for push notifs / analytics / MDM.

Re: Announcing Ionic 2 Final

#29
post #24

Not long ago I was an Ionic believer, but not anymore... the lack of support for their cloud services [0] has turned many people off and signals that they don't mind leaving their users "locked". Devs are migrating en masse to react native. I have friends in several startups leaving their jobs because they've been tasked with maintaining legacy Ionic 1.x/Angular projects, while the codebases are migrated to react nat…

> I have friends in several startups leaving their jobs because they've been tasked with maintaining legacy…

It's better to not have such people working for you in the first place.

Maintaining existing software to focus on real business is just the kind of founders I'd want to work with. It's a part of being a part of a startup, and those who jump the ship too often do not leave any legacy behind.

Re: Announcing Ionic 2 Final

#30
post #17
post #2

I'm always afraid of investing a lot of time into this type of frameworks and then having the rug pulled from under me. Most of the time I spent learning angular ended up being a waste of time and I'm still scarred from then. Also that logo looks familiar?

> Also that logo looks familiar? Dr Manhattan? http://imgur.com/a/EQNya

jesus. that's it. watched the movie 2 weeks ago, his face must still be in my RAM
Post reply on HN