Thank you! :)

I didn't explain myself correctly, I wanted to ask about their tools/preprocessors, and not about frameworks/UI libraries. I edit my post. Thank you for answering though! :)

Flow-typed props are superior in almost every way to the built PropTypes.The only drawback that you might have is that FlowType is still not well known, so people reading your code might be confused by some FlowType notations.

Sorry for being late!For sagas for example you can easily use something like this (from this post).For Redux thunk you can easily apply the same approach, just call a Alert.alert( 'Error', error) when you catch an exception and you want to display the Alert.

Hi! The easiest option would be storing the error in Redux and showing the alert in componentDidUpdate when you detect that it has changed: componentDidUpdate (prevProps) { if (!prevProps.error && this.props.error) { // show the alert } } Another option is invoking directly the alert directly from redux-thunk (I'm assuming you're using it for handling the fetching). An even cleaner solution though (in my opinion) is achieved using something like redux-saga for triggering the side effect (the alert) when an error action is dispatched. P.S.: Let me know if you need any example of the suggestions above :)

Yep, Oceanic Next + One Dark

Thank you for you post. Do background services works on the Android native side?

Yep, I know, but what about making the service comunicate with React-Native?Do you have any experience/example on this?And thanks for the fast answer man!

Hey! Nice introduction tutorial! Do you have any suggestion on the implementation/bridging of an Android service in React-Native?I'm asking because I'm considering all the available options for making react-native-beacons-android works even when the app is killed.Thanks ;)

Koa, Hapi, Express and Sails are all valid options... but I'm still trying to figure out which one suits better an API REST service. Any opinion?