REPL driven mobile development with Clojure(script)
summary
Claims that a REPL-driven workflow plus react-native + clojurescript lets a two-person team ship faster than a ten-person native team, with concrete evidence: incremental edits applied live, state reset and DB seeded (generated 30 plants), UI add‑to‑cart and animated bounce implemented and tested without rebuilds, Google Closure compiler used for JS output, and on-device debugging from the REPL. The process centers on immediate feedback, manipulable program state, and hot updates that demonstrably reduce development time and increase delivered functionality.
AI-written summary · about
chapters (9)
- 0:00Start
- 11:25CLOJURE LAND
- 28:16WHAT IS A REPL?
- 29:53WHY USE A REPL?
- 32:48WHY USE A CLOJURE REPL?
- 34:42EXPRESSIVE, SIMPLE
- 35:27WHY CLOJURESCRIPT?
- 40:08UNDIVIDED TEAM
- 41:21UNILINGUAL TEAM
related talks
29mMobile Apps with ClojureScript
46mNative and browser SPA versions using re-frame, ClojureScript and ReactNative
38mUsing React Native + ClojureScript to launch iOS/Android apps to 1M users
40mUsing Clojurescript to launch iOS/Android apps to 1M users
37mUsing Clojurescript to launch iOS/Android apps to 1M users
34mClojureScript in Your Pocket
27mOn iOS with React Native and Clojurescript
30mReact Native
