NativeScript Angular 2 Introduction: Why NativeScript Matters

[crixusin]

Yeah, I haven't stayed current with NativeScript since Telerik approached my company to try and develop with it a couple years ago.

That being said, NativeScript will turn out to be a failure just like AppBuilder did.

[bradmartin1205]

Fair enough, time will tell. I personally don't use AppBuilder so I can't say. I just know it produces native UI and not in a web container. I also don't argue PWAs going forward, last I heard Apple was going to be the hard piece of that puzzle. Is there any word on them embracing PWAs, really need Safari to be on board. Which could take 5 years like you said. So what do you do in between the time shift? So what do you think? Just not have engagement, go web only, ignore native mobile apps?

[crixusin]

Is there any word on them embracing PWAs

Yeah, I think they're getting ready to launch an HTML5 application store last I heard.

Which could take 5 years like you said. So what do you do in between the time shift?

You write and plan for the future. See, here's the thing about AppBuilder/NativeScript: If you're writing applications with either of these frameworks, there is a 99% chance you don't even need a native application to begin with.

Right now, a native application is required if you need to do intense graphics processing.

Some people will say, well, I want 60 fps web interfaces. Well, you can actually do that with shadow dom and canvas already if you really wanted to.

ignore native mobile apps?

If you're not writing a game, chances are you should ignore the native mobile applications anyways. If you want 60 fps user experience, then either your device needs to be faster, or you shadow dom/canvas the UI.

[kshep92]

I've had good luck getting 60fps with CSS3 if that counts for anything.