Hacker News new | ask | show | jobs
by moomoo11 12 days ago
why was your team against react native? (for mobile app right that goes along with the wearable right?)

you can ship the actual UI stuff in seconds.

you can write your own plugins for anything native and just call it. we have a app that uses many native SDK calls which we write plugins for and call.

not to mention that once the native work is done you can deploy ui level changes and new features, bug fixes to users over OTA.

i’m just an outsider so i know my lane. but

whatever you do, do not allow bike shedding and ultra opinionated tech nerds to derail company vision timelines.

1 comments

I've used react native a bunch. When you've got custom elements it isn't always the cross-platform write once you think it is. I've always had custom components across iOS and Android.

The big complaint is that the amount of work to get the level of polish needed in premium apps just isn't there. Or you need to do a bunch more work and it isn't significantly different than the amount of work of getting a native iOS and native android dev.