Tales of Using Phoenix LiveView at an Early Stage Startup
summary
Adpipe uses Elixir + Phoenix LiveView as a single stack for front end and back end across a ~25‑person, <2‑year startup, with eight months of LiveView production experience. File uploads go direct S3 uploads with background jobs and PubSub notifying LiveView diffs so video processing appears instant to users. Tests include end‑to‑end integration LiveView tests that cover user interactions, enabling safe refactors. Tradeoffs: large features produce 500‑line PRs, hiring Elixir‑only UI engineers is harder, and mobile reuse requires rework.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:51Startup growth and team
- 3:16Tech stack and LiveView
- 5:28Why LiveView suited us
- 8:16How LiveView accelerated development
- 10:46File uploads and state
- 12:15JavaScript with LiveView hooks
- 13:21Testing LiveView apps
- 15:55Refactoring with LiveView tests
- 17:20Engineering with LiveView
- 19:08LiveView drawbacks
- 21:17Establishing patterns in a new framework
- 23:26Hiring LiveView experts
- 24:53Teaching FP to juniors
- 25:59Mobile app considerations
- 26:42Q&A
related talks
46mThe joy of building your startup with Phoenix LiveView
40mThe Power & Performance of Phoenix LiveView
35mKeynote: Fireside Chat on LiveView, (...)
39mBeyond Liveview: Real Time Features With Liveview
01h 13mKeynote: Phoenix LiveView - Interactive Apps without Javascript
28mLobbying with Elixir: Real-Time LiveView and OTP
15mProtecting Corporate Accounts with LiveView realtime dashboard
35mBringing LiveView to the Client with Popcorn