React Native doesn't presume to know how to build cross-platform apps. But we want to enable people to do that.
That results in two different classes of Native components:
- Cross-platform components that are nearly identical on each platform- Eg. <View>, <Text>, <Image>, <TextInput>, <ListView>. There will not be many more of these
- Platform-specific components- When there is not an identical API and feature-set, we provide bridged components which can take full advantage of the platform. There will be a lot of these, but we currently only have a handful.
The real power comes from React's component-driven declarative programming style. The asynchronous batched bridge is well designed, but it's nothing special.
That results in two different classes of Native components:
- Cross-platform components that are nearly identical on each platform- Eg. <View>, <Text>, <Image>, <TextInput>, <ListView>. There will not be many more of these
- Platform-specific components- When there is not an identical API and feature-set, we provide bridged components which can take full advantage of the platform. There will be a lot of these, but we currently only have a handful.
The real power comes from React's component-driven declarative programming style. The asynchronous batched bridge is well designed, but it's nothing special.