zlacker

[parent] [thread] 4 comments
1. rimliu+(OP)[view] [source] 2017-07-27 11:46:46 

   > web apps are reaching for feature parity with native
Not even remotely close.
replies(1): >>kartan+82
◧
2. kartan+82[view] [source] 2017-07-27 12:08:29
>>rimliu+(OP)
This is Papa Pear: https://king.com/game/papapear

The HTML5 version is compiled from the same source that the App that goes to the Apple App Store (https://itunes.apple.com/us/app/papa-pear-saga/id572542612?m...).

What's so different? It is literally the same code base (minus some platform specific code).

replies(1): >>rimliu+y4
◧◩
3. rimliu+y4[view] [source] [discussion] 2017-07-27 12:30:46
>>kartan+82
I am talking about possibilities provided by iOS SDK and what is provided by web stack. It is amazing that React Native does not even have something UINavigationControll-ish. UIKit alone gives stuff which is lightyears ahead of the web. Even some more basic stuff: how easy it is to add accessibility to PWAs? Localization?
replies(1): >>royal_+C6
◧◩◪
4. royal_+C6[view] [source] [discussion] 2017-07-27 12:49:23
>>rimliu+y4
Most Frontend-Frameworks do have Localization-features so that's kind of easy to do. But other features like Bluetooth are nowhere to be seen (Blink Browser can do this - but it's far far away from a standard)
replies(1): >>vetina+ys
◧◩◪◨
5. vetina+ys[view] [source] [discussion] 2017-07-27 15:21:37
>>royal_+C6
Web Bluetooth: https://webbluetoothcg.github.io/web-bluetooth/ (not yet standard, but supported by Chrome, for example).

A11y is also being taken seriously.

[go to top]