Talks
Speakers
Events
Topics
Search
Sign in
Search
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
search talks for
⏎
Suggest modification to this talk
Title
Description
RailsConf 2017: React Native & Rails, A Single Codebase for Web & Mobile by Ben Dixon Rails made building CRUD apps efficient and fun. React Native, for the first time, does this for mobile Apps. Learn how to create a single React codebase for Android, iOS and Mobile Web, backed by a common Rails API.
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In the RailsConf 2017 talk "React Native & Rails, A Single Codebase for Web & Mobile," Ben Dixon discusses the effectiveness of utilizing React Native alongside Rails to create a streamlined development process for both web and mobile applications. Dixon shares his experiences transitioning from other technologies, highlighting the advantages of React's versatile framework which allows for code reuse across platforms. Some of the key points discussed include: - **Development Productivity**: Dixon emphasizes how Rails enables rapid development, mentioning that React Native offers similar productivity gains for mobile development. He contrasts this with his prior experiences with other frameworks where he felt bogged down by repetitive tasks. - **Unified Codebase**: By using React for both web and mobile applications, developers can maintain a shared codebase which reduces the overall effort required to develop and manage applications across different platforms. This shift results in a minor increase in effort (about 10%) when adding new platforms rather than tripling the workload. - **React as a View Layer**: Dixon clarifies that React serves primarily as a view layer and does not provide built-in utilities for making API calls or managing persistence, necessitating the use of other libraries to fill these gaps. He discusses the use of patterns like Redux for managing application state to simplify this process. - **Component Structuring**: He addresses how to structure components to keep UI differences between mobile and web applications separate while sharing other parts like state management and API calls. This approach leads to a more organized and maintainable codebase. - **Best Practices**: Dixon shares practical lessons and pitfalls he encountered during this transition, including the importance of properly managing Babel configurations and using generators to streamline code structure. He also provides insight into setting up shared modules within an application, which can ease transitions between web and mobile development. Overall, Dixon concludes that this approach to development not only enhances productivity but also reassures developers that they can expand to native applications without the fear of overwhelming complexity or resource demands. The session finishes with Dixon inviting participants to explore a sample project demonstrating these principles in action, emphasizing a collaborative and incremental approach to building applications using Rails and React.
Suggest modifications
Cancel
