Building Your Own Tools

on YouTube ↗30m

" summary

Artsy moves from heavy Swift/native work on four apps (two Swift, one Objective‑C, main app Eigen) toward React Native + Relay because native compile cycles hit tens of seconds and reuse is poor; an experiment shows rewrites need far less code, faster feature shipping, and JavaScript tooling (TypeScript, testing) improves productivity. React Native brings 593 dependencies, cross‑platform UI via flexbox, Relay collapses component data requests, injection gives sub-second changes but Swift lacks runtime support, so hybrid native fallback remains possible and adoption succeeds.

AI-written summary · about

" chapters (15)

1. 0:00Start
2. 0:10ART SY
3. 1:03DANGER
4. 5:31ARTSY SWIFT COMPONENTS
5. 5:49JSON-POWERED COMPONENTS
6. 6:31REACT IN SWIFT
7. 6:58POD VIEW CONTROLLERS
8. 7:32REACT NATIVE
9. 12:31BETTER CORE ABSTRACTIONS THAN UKIT FOR API DRIVEN APPS
10. 13:16HARD TO WRITE BLOCKING CODE
11. 13:38SIMPLER LAYOUTING SYSTEM
12. 13:58TESTING
13. 14:12OPEN COMMUNICATION
14. 15:11OPEN SOURCE BY DEFAULT
15. 16:43A BIG DEPENDENCY

" related talks

• 25mReasons to give React Native a(nother) tryBrent Vatne · JSHeroes 2018
• 07mFrom Native to React NativeGreg Ryzhov · React Day Berlin 2019
• 31mRewriting a Large Hybrid App with React NativeJavier Cuevas · Chain React 2017
• 05mLightning talk from Eric SauterEric Sauter · React.js Conf 2016
• 24mBuilding Stellar User Experiences with React NativeAlex Kotliarskyi · Chain React 2017
• 34mChanging React Native... from within!Adam Foxman · React Native EU 2022
• 30m5 years of DEVeloper EXperience in React NativeFabrizio Rizzonelli · reactjsday 2022
• 20mBuilding a Mobile App with Expo, EAS and React NativeBrent Vatne · React Summit Remote Edition 2021