ClojureScript in Your Pocket
summary
A buggy iOS app and an abandoned Android app become a single codebase using React Native + ClojureScript and Expo, with GraphQL replacing fragile REST syncing. The team rebuilds what took almost two years in Swift and Java down to a three month delivery for feature complete Android and iOS, but spends days wiring ClojureScript tooling, wraps GraphQL‑Java for the server, and hits Expo limits (video, file system) so native bridges become necessary. GraphQL eliminated over‑fetching and simplified client state.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 0:24Project Context
- 1:11Choosing Technologies
- 2:08Project Overview
- 3:24What is React Native
- 4:19React Native vs JavaScript
- 4:59React Native vs React
- 5:26Why React Native
- 6:34React Native
- 7:06Expo
- 11:24Community
- 12:16ReactNative
- 13:51Interactions
- 15:24Styling
- 16:23React Native vs CSS
- 20:16Limitations
- 20:32React Native is incomplete
- 22:49React Native iOS simulator
- 23:47GraphQL
- 25:37Lesson Learned
- 28:42Complexity
- 30:54Ecosystem
- 31:54Conclusion
related talks
29mMobile Apps with ClojureScript
38mUsing React Native + ClojureScript to launch iOS/Android apps to 1M users
37mUsing Clojurescript to launch iOS/Android apps to 1M users
27mOn iOS with React Native and Clojurescript
46mNative and browser SPA versions using re-frame, ClojureScript and ReactNative
40mUsing Clojurescript to launch iOS/Android apps to 1M users
17mDispatches from React Native
29mLessons from Using Bleeding Edge Tech in a Startup
