Capturing ARKit scene into WebRTC video stream for React Native | Hacker News Reader

Capturing ARKit scene into WebRTC video stream for React Native

github.com

75 pointsjhen040911 comments

The reason you use React Native is because you are platform independent, if this doesn't integrate with Android in more or less the same way it's a hard sell.

I'm working with this myself (painting over WebRTC frames) and it's definitely not out that different by itself comparing Android to iOS.

The reason you use React Native is because you are platform independent...

That's a reason to use it, but it's not the only reason.

For example, where I live it's much easier to recruit JS developers with React and React Native experience than it is to recruit native mobile developers (it's not a cost thing; there just aren't many native mobile devs looking for work). Consequently it's better to build with React Native even if you're only targeting one platform because the long term support for the app would be basically impossible if you can't recruit someone capable of doing it.

That assumes that building quality mobile apps in js doesn’t require knowledge of native app dev and specialization in mobile app dev (it does). And if those things don’t matter you might as well just hire anyone willing to learn native mobile dev - react native wont make their job any easier beyond the first day (in fact it would make it more complex).

Your definition of quality is different than mine. I think most native apps are unstable, unlearnable, gratuitously animated messes. Even supposedly “quality” apps. I can’t tell you how many voice memos I’ve lost because of Apple’s “lickable” and totally broken (but very pretty) UI.

I would prefer a simple, well designed web app to the vast majority of them.

The native toolkits have too big a surface to reliably product high quality UIs. Yes, it’s possible but they push you away from making the choices that lead to good user experience, in favor of UIs that look impressive on an interaction designer’s or a developer’s portfolio.

This is what native mobile devs tell themselves to preserve their self worth... but unfortunately it's no longer true that you need a dedicated native iOS or android dev to make a useful and performant app.

I’m actually not a mobile dev, just deal with a bunch tech surrounding that space. Also, nothing against react native - used it for building quick things myself too - it’s just not something I’d pick to build say an Uber app, or something. And if you’re not building that level of an app, why bother? Web is enough.

I’d be concerned that you have a bit of a disaster waiting to happen with not native devs. My experience is that a fully JS team needs the support of some devs who know native for RN to work well. Ideally you need devs with native and JS/React chops to fill these supporting roles

> Consequently it's better to build with React Native even if you're only targeting one platform

In the context of the article how is this easier? Integrating with a platform specific API requires knowledge and experience with it, what benefit does sticking another layer infront of it bring? If a developer knows the platform and API then chances are she will prefer to work with the API directly and use the latest version, official tools and docs.

Have you actually done this?

I've done some of both and it doesn't reflect my experience at all! And the lower productivity of RN makes it even worse.

Yes. The company I work for has various native, Xamarin, and React Native apps for iOS and Android (and Windows Phone..). We've used React Native on all of our new projects for about a year now, and it's working very well.

As another commentator said: its a reason.

When we switched to RN our primary reasoning was around shipping features faster for iOS apps. The iOS support in RN is top notch and it worked for our purposes.

Reply on news.ycombinator.com