Hacker News Reader

Comment by danpalmer | Hacker News Reader

Has sharing between the web and RN worked out for you? It seems like it hasn’t for many, or any high profile apps.

Even mobile web and non-web mobile are quite different platforms, even at the UI layer. There are many different expectations, platform norms, and interaction differences that don’t work well in browsers or across platforms. I’d love to seen an example of it working well but I haven’t yet.

View on HN

Honestly I havent tried much sharing with web but I can at least vouch for sharing between iOS and Android which seems to work mostly. In a few years time I think it will become much more easy and bulletproof than it is now. Making two different apps in SwiftUI and Jetpack Compose seems overkill already.

I remember component sharing being a topic on day 1 with react native. I also remember it coming up a lot about 5 years ago when MS launched a component library that theoretically did this (didn’t seem to take off). I’m skeptical of the approach given that so much time has passed, with so much incentive, and it still hasn’t happened.

Building both SwiftUI and Jetpack Compose apps is definitely a ton of work, but I think the right choice at scale. Before “scale” is “achieved”, I’d advocate for doing one platform well (there’s often an obviously more important one) and packaging the web PWA for the other platform.

True at scale it makes perfect sense to do that. Its just not a very lean (2 different codebases for 2 platforms) and maintainable solution (apple and google keep changing how they do things and kick out apps that dont follow suit)

Reply on news.ycombinator.com