5 ms·
For me, with the only PhoneGap app I've worked on, there were required extensive bridge code to Native APIs, anyway. So adding in the webview components just me
by drvdevd 10y ago
For me, with the only PhoneGap app I've worked on, there were required extensive bridge code to Native APIs, anyway. So adding in the webview components just meant having a mess of different languages/frameworks in the codebase where I don't think it would've required very much native code anyway.
Is there a good meta-compiler solution targeting native APIs across mobile platforms that people are using lately?
- MBCook 10y ago> Is there a good meta-compiler solution targeting native APIs across mobile platforms that people are using lately? I guess I just don't see why everyone is so dead set on trying to find a way to not make native applications. No matter how long this goes on, no matter how much more advanced these library seem to get, native apps always feel and work better. I understand you don't want to do a complete rewrite for each platform, but I'm not sure that trade-off is worth it for the quality of apps you tend to get out of these middleware solutions. (Games are something of an exception)
- drvdevd 10y agoWell, personally I'm not dead set on non-native code, just thinking of ways to make something "cross platform" this is close enough to native code to make other team members comfortable. Personally, I'm the type to just write native code first as I believe it skips lots of the quirky situations as mentioned in the post. So I completely agree.
- bayesian_horse 10y agoIt's a very attractive trade-off when you're "profit" plan doesn't involve massive adoption by discerning gamers/users.
- MBCook 10y agoI just don't think many people realize just how many people are actually sensitive to issues of non-native apps, they just couldn't name or put their finger on what the problem was. Frankly I'm about to give up on Google because of their AMP pages and how terrible they work on an iPhone. It's to the point where I can't use half the search results. All because they decided to make it act non-native and implement their own special behavior in I-frames on their website.