The document compares ComponentKit and React Native for building native iOS apps. It discusses that ComponentKit uses a declarative approach like React.js but only supports iOS, while React Native uses JavaScript to build apps for iOS, Android and the web using a native UI bridge. The document considers pros and cons of both, ultimately concluding that React Native's ability to build cross-platform using JavaScript may make it preferable for many developers due to its broader reach despite some tradeoffs in performance for complex native tasks.
5. React.js
Simple
“Simply express how your app should look at any given
point in time, and React will automatically manage
all UI updates when your underlying data changes.”
Paul Taykalo, ComponentKit and React Native, Stanfy, 2015 5
6. React.js
Declarative
“When the data changes, React conceptually hits the
"refresh" button, and knows to only update the
changed parts.”
Paul Taykalo, ComponentKit and React Native, Stanfy, 2015 6
20. Write once, run everywhere
Java, Sun Microsystems
Learn once, use everywhere
React, Facebook
Paul Taykalo, ComponentKit and React Native, Stanfy, 2015 20
21. React.js
var HelloMessage = React.createClass({
render: function() {
return <div>Hello {this.props.name}</div>;
}
});
React.render(
<HelloMessage name="John" />,
document.getElementById('container')
);
Paul Taykalo, ComponentKit and React Native, Stanfy, 2015 21
39. ComponentKit downsides
» Native (I cannot write for Android)
» I need to compile it each time I change something
» I cannot share the code
Paul Taykalo, ComponentKit and React Native, Stanfy, 2015 39