Keynote: Fireside Chat on LiveView, (...)
summary
LiveView claims to let teams build fault-tolerant, server-driven single‑page flows using Phoenix, OTP and pubsub and OTP for real‑time updates; it promotes the CRC pattern (construct‑reduce‑convert) and skinny LiveView handlers backed by contexts and reusable reducers. Examples include a checkout form running in production with thousands of daily users. Surface component features migrate into LiveView, JavaScript hooks handle edge cases, and disconnected mobile/offline scenarios require custom JS or different architectures.
AI-written summary · about
chapters (11)
- 0:00Start
- 3:12What Makes Live View So Effective Why Is It So Special
- 8:08Crc Pattern
- 10:25The Constructor
- 14:45Boundary Layer
- 18:04Is Live View Its Own Thing or Is It Part of a Greater Ecosystem
- 24:10Which Companies Are Using Phoenix Live View in Production
- 30:08Is It Possible To Use Phoenix Live View To Build a Really Nice App for Ios or Android That Can Compete with Native Apps
- 30:20Using Live View for Your Mobile Web Development
- 31:24When Building Complex Systems We See Patterns Such as Microservices or Micro Front Ends How Does this Translate into Live View How Do We Manage the Growing Complexity of the Live View App
- 33:34Downsides of Microservices
related talks
01h 13mKeynote: Phoenix LiveView - Interactive Apps without Javascript
46mThe joy of building your startup with Phoenix LiveView
40mThe Power & Performance of Phoenix LiveView
39mBeyond Liveview: Real Time Features With Liveview
24mLiveView and Web Components
44mWhat's new in LiveView
30mTales of Using Phoenix LiveView at an Early Stage Startup
28mLobbying with Elixir: Real-Time LiveView and OTP