How is it different from NativeBase.io?

[react-native-elements]

How is it different from NativeBase.io?

[rockus123]

I think javascript and react and angular and all these thousands of framework are the wrong way to go. To complicated in everything.

[knowbody]

hey @sanketsahusoft!

Also, do you have any idea about how can we move NativeBase to react-native-community? What are the pros and cons of moving it to the react-native-community organization?

Our goal is to keep FOSS, maintained and well documented modules for React Native within the organisation. If you want your project to join us, just ping me or other folks on the team (@grabbou, @satya164, @Kureev, @brentvatne) and we will make it happen.
We want react-native-community to be a "go to" place for high quality, well maintained modules for React Native.

• The cons - I can't think of any... We don't owe your code, we don't ask for for your npm access, you are still in full control of your repository.
• The pros - I think at some point it will attract more contributors to these projects. At the moment I see the pros for others, because they can be sure that when they use any of these modules they are well supported.

[eduardoinnorway]

Any progress here or just talks?

[ALawliet]

My project is currently a blend of NativeBase (most things), Elements (love the icons/buttons, ButtonGroup), and https://github.com/xinthink/react-native-material-kit (range sliders!!, checkbox), so it'd be amazing if you guys did a merge! 👍

[davebro]

@rockus123 Huh?? Why are you even here lol? People probably said the same thing during the Industrial Revolution...and uh...now I have a MacBook Pro. So.....

[sanketsahu]

@Jonovono

• NativeBase follows the design guidelines of Android and iOS and aims at unifying their API using conditional styling.
• NativeBase suggests on adding more JSX and less props which makes it flexible.
• NativeBase defines the styling in one place which can be ejected and overridden by the user.

[sanketsahu]

Hi @dabit3, thanks for the inputs! NativeBase is 100% Open source, it doesn't charge for its components.

Also, do you have any idea about how can we move NativeBase to react-native-community? What are the pros and cons of moving it to the react-native-community organization?

[sanketsahu]

@knowbody Thanks a lot for the inputs. I really appreciate that you and the community are open to embrace open source projects with value.

I will have an internal discussion with the team and ping you once we have some updates.

Thanks again!

[herlarbs]

Is there any hope of a potential merge someway along the nearest future or have both parties decide to go on separate ways. I love Nativebase but I'm keen on its direction and path for the next foreseeable future

[Jonovono]

@sanketsahusoft Hey, can you talk a bit about the differing philosophies in these two projects? :)

[dabit3]

Hey, it's not really following any specific styling guidelines because they are all configurable with styling! Not sure I want to move it away from this repo, we are trying to keep it 100% free and open source. Isn't native base charging for some of the components?

[dabit3]

@sanketsahusoft Oh that's awesome, I really like NativeBase, you guys have a lot of great components. Re: moving to RN Community, I would reach out to either @knowbody and check with him on what that process is.

[satya164]

Sounds awesome!

[pierredewilde]

Any update about a potential merge of NativeBase into React Native Elements ?

[sanketsahu]

@pierredewilde No plans about the merge as of now. Both the repos are built on different patterns and a bit of different philosophies actually.

[Ayc0]

Is there any progress ?