ReactJS dev support

[Sebastian.s1994]

Hey guys,

Our company is starting a project soon and I want to go with ReactNative rather than Cordova/Angular.

What is the React support out there in terms of South African devs?

Thanks

 

[_kabal_]

why do you want to go with ReactNative specifically?

Do you know React?

Do you know Angular2? have you considered NativeScript?

 

[SmartKit]

Hey guys,

Our company is starting a project soon and I want to go with ReactNative rather than Cordova/Angular.

What is the React support out there in terms of South African devs?

Thanks

I must say, I've just developed my first app with React Native and I'm sold. Coupled with Parse Server (or Firebase, though I have no experience) and you have an end-to-end solution.

Though if you already know Angular, why not Nativescript, as per _kabal_?

EDIT: as regards support, if you go with React Native, what is it you're looking for?

 

[Sebastian.s1994]

why do you want to go with ReactNative specifically?

Do you know React?

Do you know Angular2? have you considered NativeScript?

I would like to go ReactNative as I've worked with React & Redux in the browser a lot. I only worked with Angular1 a bit, no real world apps. Native dev would be to expensive.

 

[Sebastian.s1994]

I must say, I've just developed my first app with React Native and I'm sold. Coupled with Parse Server (or Firebase, though I have no experience) and you have an end-to-end solution.

Though if you already know Angular, why not Nativescript, as per _kabal_?

EDIT: as regards support, if you go with React Native, what is it you're looking for?

At the moment I will be the only one working on the app but if I am going ReactNative I just want to make sure there are devs that can easily be recruited. But am I wrong to say that if someone is a good Angular (Javascript) dev they should not struggle switching to React?

 

[SmartKit]

At the moment I will be the only one working on the app but if I am going ReactNative I just want to make sure there are devs that can easily be recruited. But am I wrong to say that if someone is a good Angular (Javascript) dev they should not struggle switching to React?

Look, it's... different - especially on the JSX side. But at then end of the day it's also 99% JavaScript with some HTML elements embedded in the code.

Effectively you're gonna need to give any developer a period to come to terms with the new framework (and possibly with ES2016+ for good measure - but they should be learning that anyway!) before they churn out code. However, if they are decent JavaScript developers the battle is already mostly won.

 

[SmartKit]

I would like to go ReactNative as I've worked with React & Redux in the browser a lot. I only worked with Angular1 a bit, no real world apps. Native dev would be to expensive.

Agreed, native dev ultimately means at least twice the cost.

Remember React Native also isn't write-once-run-anywhere either (well, except on the simpler stuff)! However, you will be looking at 80%+ of the same base code.

 

[sutekj]

How much native coding do you need to know. Is it essential to have a Mac if you want to release an iOS version as well?

Also, got guides or starter kits you can recommend?

 

[sutekj]

How much native coding do you need to know. Is it essential to have a Mac if you want to release an iOS version as well?

Also, got guides or starter kits you can recommend?

 

[SmartKit]

How much native coding do you need to know. Is it essential to have a Mac if you want to release an iOS version as well?

Also, got guides or starter kits you can recommend?

If you stick solely to the community projects you will not need to know any native code - otherwise Objective-C and Java if you wish to build your own components (though there is little you can't already do with React Native).

React Native has a fairly decent tutorial of it's own: https://facebook.github.io/react-native/docs/getting-started.html

The best kit I've used is Ignite: https://github.com/infinitered/ignite - you will need to brush up on your Redux http://redux.js.org/docs/basics/UsageWithReact.html

Alternatives are SnowFlake https://github.com/bartonhammond/snowflake and Pepperoni https://github.com/futurice/pepperoni-app-kit

Additionally, as good start for a BAAS (backend as a service) would be Parse Server http://parse.com/ + https://github.com/ParsePlatform/ParseReact (though you don't need to use mixins) or Firebase https://firebase.google.com/ if you don't mind leaving control in the cloud.

Good luck!

 

[sutekj]

That looks great. Thanks. Saved it.

 

[[)roi(]]

If you stick solely to the community projects you will not need to know any native code - otherwise Objective-C and Java if you wish to build your own components (though there is little you can't already do with React Native).

React Native has a fairly decent tutorial of it's own: https://facebook.github.io/react-native/docs/getting-started.html

The best kit I've used is Ignite: https://github.com/infinitered/ignite - you will need to brush up on your Redux http://redux.js.org/docs/basics/UsageWithReact.html

Alternatives are SnowFlake https://github.com/bartonhammond/snowflake and Pepperoni https://github.com/futurice/pepperoni-app-kit

Additionally, as good start for a BAAS (backend as a service) would be Parse Server http://parse.com/ + https://github.com/ParsePlatform/ParseReact (though you don't need to use mixins) or Firebase https://firebase.google.com/ if you don't mind leaving control in the cloud.

Good luck!

I'm always surprised when I see such enthusiasm about Facebook's new thing -- appears some developers either have short memories or are uninformed about the dangers of choosing Facebook's latest thing.

At least for your own sanity do some research about how developers were burnt with for example: Three20 and Parse.

In general Facebook appear a little uncommitted about their directions; one example: they're leading the port of the Swift Language for native Android development, including the Foundation stdlibs; which make me wonder about which horse are they betting on for the long run.

 

[SmartKit]

I'm always surprised when I see such enthusiasm about Facebook's new thing -- appears some developers either have short memories or are uninformed about the dangers of choosing Facebook's latest thing.

At least for your own sanity do some research about how developers were burnt with for example: Three20 and Parse.

In general Facebook appear a little uncommitted about their directions; one example: they're leading the port of the Swift Language for native Android development, including the Foundation stdlibs; which make me wonder about which horse are they betting on for the long run.

Thanks bud, making good use of the open-source community-supported and driven Parse Server initiative - as mentioned above.

Additionally Facebook, Facebook Ads Manager, Facebook Groups and Instagram all use React Native - so Facebook isn't just a dealer, they're a user too!

 

[[)roi(]]

Thanks bud, making good use of the open-source community-supported and driven Parse Server initiative - as mentioned above.

Additionally Facebook, Facebook Ads Manager, Facebook Groups and Instagram all use React Native - so Facebook isn't just a dealer, they're a user too!

They were both a Three20 creator & user, similarly Parse (purchased creator re internal use); yet it didn't stop them from terminating it when they changed direction. Open source means nothing if it's not secured by a good community or corporate.

/Edit I'm probably just more dependency adverse than most; don't include something unless it's future is secured or if I'm quite confident it's easy to fork and maintain separately.

 

[SmartKit]

They were both a Three20 creator & user, similarly Parse (purchased creator re internal use); yet it didn't stop them from terminating it when they changed direction. Open source means nothing if it's not secured by a good community or corporate.

/Edit I'm probably just more dependency adverse than most; don't include something unless it's future is secured or if I'm quite confident it's easy to fork and maintain separately.

Three20 was DOA on that we agree. Parse on the other hand has created a huge opportunity - it is more alive today that ever.

I hear what you're saying about being risk averse. I've been burnt on a few (mostly mobile) technologies.

In the instances of Parse Server and React Native it's been given to the community and there is no reliance on a corporation. Silver lining, no?

My five cents is that React Native works bloody well. This is the first time I've been comfortable with cross platform development - and I can programme in both Java and Swift (I draw the line at Objective-C).

 

[[)roi(]]

Three20 was DOA on that we agree. Parse on the other hand has created a huge opportunity - it is more alive today that ever.

I hear what you're saying about being risk averse. I've been burnt on a few (mostly mobile) technologies.

In the instances of Parse Server and React Native it's been given to the community and there is no reliance on a corporation. Silver lining, no?

My five cents is that React Native works bloody well. This is the first time I've been comfortable with cross platform development - and I can programme in both Java and Swift (I draw the line at Objective-C).

You miss the point with parse; it was a service; the service doesn't exist. FB outsourcing the product was at least some saving grace, but for most if their customers that simply increased their costs and liability.

The bigger issue is that FB have demonstrated they're willing to turf solutions at a moment's notice. So whilst you may love React Native, internally FB aren't betting the farm on it.

 

[SmartKit]

You miss the point with parse; it was a service; the service doesn't exist. FB outsourcing the product was at least some saving grace, but for most if their customers that simply increased their costs and liability.

The bigger issue is that FB have demonstrated they're willing to turf solutions at a moment's notice. So whilst you may love React Native, internally FB aren't betting the farm on it.

I respectably disagree, in this instance. React Native isn't a service and is community driven - it can continue without Facebook. One of the customers that stands to lose out should Facebook change direction is Facebook, so they definitely have hedged some bets.

Yes, Facebook has dropped the ball on some occasions - and may do so with React Native - but it's structured such that it won't be of huge consequence.

 

[[)roi(]]

I respectably disagree, in this instance. React Native isn't a service and is community driven - it can continue without Facebook. One of the customers that stands to lose out should Facebook change direction is Facebook, so they definitely have hedged some bets.

Yes, Facebook has dropped the ball on some occasions - and may do so with React Native - but it's structured such that it won't be of huge consequence.

Community driven, doubtful. The commits alone don't support that notion, that's like saying Swift would survive without Apple -- it's open source, and has a lot of community involvement, but what we should acknowledge is the vast difference of commits between community and Apple. With React Native, its not different, you need only look at the major contributors to similarly confirm its primarily FB resource. Plus FB lost their largest contributor earlier this year (Nick Lockwood); someone who has openly doesn't use React Native, prefers Objective-C & Swift.