Yes, we regret it. Our app is just a wrapper around a webview, and handles things like in-app payments and SDK integrations like Facebook login, in a team of ~10. Our version of React Native is quite far behind which makes using libraries not already in the project difficult: you have to track back through versions to find a compatible version, which then may not be doing what you want since it's an older version. We…
Ask HN: Companies who adopted React Native over a year ago, do you regret it?
101–110 of 149 posts
Re: Ask HN: Companies who adopted React Native over a year ago, do you regret it?
#102Especially those who have positive experience, could you share your experience with 3rd party libraries particularly in these particular areas: * Layout * Infinite scrolling * REST client * Image handling (loading, displaying, caching) for popular formats * Push notification (Apple's and Google's) * Built-in (not server-side) SQL for storage * Animation (like transitions, fading) * [Added] In-app purchases The reason…
Layout: It's the main reason to go all in with RN. You're much faster building these with RN then using native stuff. Infinite Scrolling: ListViews and RN are a thing. There's a new List Type since a few Versions - if you're following the book regarding DataStrucure everything should work. REST Client: RN provides basic API so nearly everything which works in Browser works in RN too. I use Redux Sagas and fetch. Work…
Re: Ask HN: Companies who adopted React Native over a year ago, do you regret it?
#103We have a 15-person engineering team and converted our mobile app to React Native at the beginning of this year. We do not regret it. Our pace of delivery is much faster with React Native than what we were able to achieve building natively. Our app has over 100 screens, and only needing to implement features once to have them on both platforms is nice. The feedback loop when making code changes is much faster, especi…
It benefits your dev team, but does it benefit your customers? How's the battery usage of your RN app vs a real native app? Does your app require the latest phone hardware to run with decent performance?
> Swift won overall in the CPU category, React-Native won the GPU category (barely), and React-Native won big time in the Memory category.
[1]: https://medium.com/the-react-native-log/comparing-the-perfor...
Re: Ask HN: Companies who adopted React Native over a year ago, do you regret it?
#104Earlier quoted context omitted.
It benefits your dev team, but does it benefit your customers? How's the battery usage of your RN app vs a real native app? Does your app require the latest phone hardware to run with decent performance?
As one of the designers of this app, I was skeptical initially if there would be restrictions on customizing common UI components, the smoothness of animations/interactions, usability, performance, etc. You definitely have to put in a bit of extra work (isn't that always the case with making things nice though), but you can get very nice results (and battery usage) with RN for sure on both Android and iOS. Personally…
[1] https://sites.google.com/view/energy-efficiency-languages/re...
Re: Ask HN: Companies who adopted React Native over a year ago, do you regret it?
#105Earlier quoted context omitted.
How do you manage 100+ screens? I started building a react native app but decided against it because switching activities seemed to be very hacky compared to native development. Seemed like it'd really get out of hand with 10+ screens. Wix's "React Native Navigation" was too opinionated / inflexible.
I found quite the opposite, it's much easier to manage many activities, I am guessing you were using your own 'routing'? Take a look at react-navigation or react-router (it supports react-native too)
I pretty much put the project down after that and started learning Swift (I already do Android).
Now I decided to go all out on iOS dev with the hope of making a career change from web.
Re: Ask HN: Companies who adopted React Native over a year ago, do you regret it?
#106Earlier quoted context omitted.
As one of the designers of this app, I was skeptical initially if there would be restrictions on customizing common UI components, the smoothness of animations/interactions, usability, performance, etc. You definitely have to put in a bit of extra work (isn't that always the case with making things nice though), but you can get very nice results (and battery usage) with RN for sure on both Android and iOS. Personally…
One of the reasons I brought this up was a recent article about energy efficiency of programming languages.[1] JavaScript is ~2x less energy efficient than Java, so it will eat twice the battery. [1] https://sites.google.com/view/energy-efficiency-languages/re...
Re: Ask HN: Companies who adopted React Native over a year ago, do you regret it?
#107Earlier quoted context omitted.
How are you doing code sharing between web views and native? Is this an (open-source??) high-level component library that conditionally compiles to either 's or 's? Or did you actually find a way to render ReactDOM components within React Native inside some sort of controlled web view? The latter IMO would be a holy grail for companies trying to transition large ReactDOM codebases to native apps gradually.
So we've tried a lot of things to maximize code sharing. Our initial goal was to share non-visual code like reducers/action-creators/libs/utils etc… This was pretty interesting but it didn't give us the amount of sharing that we wanted. We were still building multiple versions of many things. The next approach we started on was using https://github.com/necolas/react-native-web . This was very exciting and very fun to…
Re: Ask HN: Companies who adopted React Native over a year ago, do you regret it?
#108A little off topic, but I really, really wish that people would stop trying to make JavaScript be the language of everything. I have zero interest in JavaScript, I don't believe it's a nice language to work in, and the ecosystem is insane. However, given the way things are going, and the way jobs are trending around me, it seems unavoidable.
There should always be a job available for you that doesn't require writing JavasScript. However, as a counterpoint, I have been writing ruby/javascript for a while now and the last couple of years I agree the JavaScript has taken over my career. I have 0 complaints, I love modern javascript, the ecosystem, the engines, debug tools and everything between. You don't have to like it but lots of people do and lots of hi…
Re: Ask HN: Companies who adopted React Native over a year ago, do you regret it?
#109A little off topic, but I really, really wish that people would stop trying to make JavaScript be the language of everything. I have zero interest in JavaScript, I don't believe it's a nice language to work in, and the ecosystem is insane. However, given the way things are going, and the way jobs are trending around me, it seems unavoidable.