This page is a permanent link to the reply below and its nested replies. See all post replies 禄
Northwest 路 M
I personally picked it and led a team to develop a major application, 4 years ago.
Great idea in principle, but would not do it today, as long as Apple is not party to the development effort, and they will never be.
Control over hardware functionality, especially VR, geosynch, gyrosynch, network and camera lags, making achieving true code portability impossible, as I learned the hard way.
I can longer use that code base today, and would recommend a mix of native/react to achieve a higher level of interoperability.
Great idea in principle, but would not do it today, as long as Apple is not party to the development effort, and they will never be.
Control over hardware functionality, especially VR, geosynch, gyrosynch, network and camera lags, making achieving true code portability impossible, as I learned the hard way.
I can longer use that code base today, and would recommend a mix of native/react to achieve a higher level of interoperability.
Elessar 路 26-30, M
@Northwest That'll depend what you're trying to achieve, but from the perspective of my use case I haven't seen such limitations. But bear in mind, my apps mostly do QR-scanning, REST and local data processing/storage so I don't interact with hardware too much.
Working with XCode is painful as hell for me so I'll stay away from pure native as much as I can, and I've never tried React Native yet
Working with XCode is painful as hell for me so I'll stay away from pure native as much as I can, and I've never tried React Native yet