3 ms·

I totally understand the upside of writing one app for both platforms, but at the end of the day they are still two different platforms. It seems unlikely you’r

I totally understand the upside of writing one app for both platforms, but at the end of the day they are still two different platforms. It seems unlikely you’re going to make a high quality app unless you give each version the individualized attention they really need. Maybe these dual platform frameworks are fine for something like a company internal app where it’s okay if you don’t get everything “just right”. But otherwise I’d rather just go pure native, even if it means alienating half my user base or spending 2x resources. It’s worth it in most cases IMO. Granted I’ve only spent a couple weeks with React Native about a year ago, so maybe I just need to give it another go.

hactually 8y ago
I'd really recommend taking a dive into flutter. It's leaps and bounds better than working with React Native IMO. Treating Dart and Flutter as one 'SDK/Language for Apps' made it a lot easier to avoid the uncanny valley effect I had with react native vs normal react.
woah 8y ago
It doesn't make sense to alienate half your user base if your product is anything other than a standalone app with no real-world hardware or services. In this case you're not competing on app slickness like you would be with a calendar app or something.