4 ms·
One of the main issues I had when I tried to do an app in react native was not really the UI,performance or data. The main problem was that you where in an unc
by bpfrh 2y ago
One of the main issues I had when I tried to do an app in react native was not really the UI,performance or data.
The main problem was that you where in an uncanny vally type of situation where some browser features where supported and some nodejs(?) features but never the right ones.
So you now had to write 3 different apps(web,ios,android,electron(?)) with all the problems of react/js while not having the wealth of libraries and batteries included benefit of a browser
E.g. crypto.subtle was not available, so forget anything with encryption running in react native and on the web without separate libraries.
So my question is how do you solve the problem that react native loses many of the benefits of using a webview type framework?
- nwienert 2y agoIt’s a trade off - better performance and native UI but a bit more of a learning curve and need to curate some API surfaces. We have something close to ready based on Expos “use dom” feature they just announced. It should be available soon. I think that’s a smart strategy so you can do webviews if your want. But to be honest I haven’t felt much pain in that regard. You can almost always find a library pretty easily for what you need, and the trade off in getting a great native feeling app is worth it, especially if we can keep improving DX, which I plan to do.