Hacker News Reader

Comment by djanogo | Hacker News Reader

There are two ways to write mobile app...

1. Write native app's for both the platforms, pay once and cry once. 2. Write web mobile apps, realize how sub par the experience is, rewrite in native. Pay twice, loose competitive advantage, and cry twice.

This is what, 3rd or 4th iteration of web app's are going to take over mobile cycle?. My first instinct about any blog that promotes this turd is, either their business depends on selling this solution or the person is huge web guy and never really worked on complex native apps.

View on HN

I wrote a PWA and got it published in 3 app stores[0]. I found this to be a pretty good mix: I can access native mobile features while using modern web features and rolling out instant updates without app store approval.

[0]: http://debuggerdotbreak.judahgabriel.com/2018/04/13/i-built-...

They are clearly trying to sell their business "If you have further questions regarding the PWA development, reach out to the K&C team as right now we’re actively working in this field".

After writing enough front end work, I'm not exactly afraid of writing native apps for multiple platforms.

I dont want to, which is why I chose react native JS for this round of development. But the big deal IMO is getting the back end of the app developed and working.

Beautifying is annoying and time consuming, but I dont need to learn anything new.

Implementing a backend that is secure required learning a framework and massive testing.

IMO pretty is easy, but I havent made anything for IOS, so who knows.

As with web apps and applications in general there's a wide gamut of different app categories. There's also frameworks such as Ionic that provide native or near-native capabilities and experience through native bindings.

> realize how sub par the [mobile web app] experience is

why is this a given?

A proven experience since Symbian introduced the Web Runtime in 2011, with a few dead OSes pushing for a Web only experience?

There is such a thing as "good enough". The cheap plastic solution tends to win when that happens. We weren't there in 2011, maybe we're not there in 2018, but the writing's on the wall.

When that happens, the browser would have turned into a general purpose VM running apps via WebAssembly with WebGL/WebGPU for rendering, thus becoming native as well.

The writing is on the wall with the ongoing efforts on .NET, Java, Go, Unity, Unreal and who knows, someone might even port Flash to it.

I don't consider an universal bytecode as native.

So according to you IBM and Unisys mainframes, the Xerox PARC computers, watchOS apps don't run native code.

Do the CPUs of their respective systems directly understand the instructions? In my opinion, if they don't, that's not native code. Of course, for strategic reasons such as portability the manufacturer might not provide any kind of access. At which point that's the closest to "native" you're going to get...

Depends, on the mainframes and watchOS, bytecode (or bitcode) is used as portable binary format and JIT compiled at installation time into native code.

On Xerox PARC systems, the CPUs were micro-coded.

> turd

> conflict of interest

> ~simpleton

Says the guy that deliberately says: "both the platforms". Talk about ingrained propaganda

Reply on news.ycombinator.com