I don't think all projects should be done with it as native development still has its place for certain kind of apps, but for a typical thin-client app wrapping a web service, it's really great.
One month with React Native
21–30 of 55 posts
Re: One month with React Native
#22Re: One month with React Native
#23What I wish to exist is something like Kotlin with react-native like library, with single good cross-platform library of components and good solid tooling.
Facebook developers are awesome, but they are paid for Facebook apps, not for making good library, IMO, good library is just a by-product which they kindly shared and it feels everywhere.
Overall I think React Native is the best cross-platform solution out there. It doesn't carry overhead of bundled HTML webview, its view is advanced enough for complex GUI, it provides smooth animations and React is something very interesting actually. Also you can push updates without app-store approvals, if I got that right (I'm not sure about Apple). For apps built in haste with multiple bug-fixes every hours it's important.
Re: One month with React Native
#24It has the best React support ever since React existed, and every IDE feature imaginable. And also, its basically the same IDE as Android Studio, so a very small step for a App programmer.
Re: One month with React Native
#25I'm going through a similar experience. I have some experience with Objective C and iOS, almost nothing with Android and I have good experience with (non-mobile) Java. Basically I have a week to build Android app which should be quickly ported to iOS. So far my experience is mixed. React Native feels like very powerful tech. But standard library is very minimal, tooling looks very fragile (it works, but I'm very afra…
AirBnB just started working on one too that seems promising, but it's not ready for primetime yet.
Re: One month with React Native
#26> Next, plan your Redux store ahead. I feel like I made the mistake of overusing it. Almost every property of my app is managed by Redux and this results in large reducers and many many actions to control all that. It’s very important to figure if some prop will be needed outside a certain component or not and, if not, keep that inside that component. How can you possibly know _in advance_ if a prop will be needed ou…
http://redux.js.org/docs/recipes/reducers/BasicReducerStruct....
Here are a few gotchas to avoid:
1. Define your state shape in terms of your domain data and app state, not your UI component tree.
2. Your reducers do not need to have a 1 to 1 mapping to actions. If you need to fire multiple actions to change the data you need then rethink your reducers.
Re: One month with React Native
#27I'm going through a similar experience. I have some experience with Objective C and iOS, almost nothing with Android and I have good experience with (non-mobile) Java. Basically I have a week to build Android app which should be quickly ported to iOS. So far my experience is mixed. React Native feels like very powerful tech. But standard library is very minimal, tooling looks very fragile (it works, but I'm very afra…
Disclaimer: I work on React Native, react-navigation, etc @ Expo (expo.io)
Re: One month with React Native
#28Earlier quoted context omitted.
What database were you using and what bottlenecks did you run into? Curious as I have yet to work with dbs in React Native.
We are using SQLite. The performance bottleneck is not the database itself but conversion between the Java and JavaScript environments.
Re: One month with React Native
#29Re: One month with React Native
#30React Native vs Xamarin?