Native and browser SPA versions using re-frame, ClojureScript and ReactNative

on YouTube ↗46m

" summary

Rewriting a browser spelling-practice app into ClojureScript lets the team ship a single codebase that shares about 90% of logic between web and native using reagent + ReactNative via Expo. Architecture uses effects and coeffects so event handlers stay pure, returning effect descriptions that make unit tests trivial, while reactive subscriptions compute view data once and reduce renders. Platform differences reduce to a few effect handlers (storage, native APIs) and view event wiring; most business logic is identical.

AI-written summary · about

" chapters (7)

1. 0:00Introduction and context
2. 3:47Effects and co-effects in re-frame
3. 18:13Subscriptions and reactivity
4. 23:20Design constraints and benefits
5. 26:56ClojureScript advantages
6. 31:35Code sharing between platforms
7. 36:02Q&A and final thoughts

" related talks

• 29mMobile Apps with ClojureScriptJearvon Dharrie · Clojure/conj 2015
• 27mOn iOS with React Native and ClojurescriptJelle Akkerman · Øredev 2016
• 28mCross-Platform ReactAnna Doubkova · ReactNext 2019
• 34mClojureScript in Your PocketDom Kiva-Meyer, Lily M. Goh · Clojure/west 2017
• 29mDesign decisions in React-based ClojureScript applicationsFalko Riemenschneider · :clojureD 2017
• 25mGoing NativeAnna Doubkova · ReactiveConf 2018
• 41mReact Native - A native love storyEnes Kaya · code.talks 2017
• 53mHow React-Native shapes the way we think about native appsIlya Ivanov · Mobile Fest 2018