From Zero to App with Bridgetown: The Rapid Prototyping Framework
summary
Claims that Bridgetown (beta 2) lets teams go from static mockups to a functioning prototype: a Roda-powered server-side rendering stack with file-based dynamic routes and Roda-powered server-side rendering that wires into external APIs. The team prototypes an identity-verification flow, connects to login.gov sandbox, mocks internal APIs, and validates a doctor-onboarding path; hundreds of organizations and thousands of patients are already in production elsewhere, and the prototype works as a testbed though not a drop-in replacement for the existing Rails system.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:07Healthcare data challenge at CMS
- 4:58Prototyping doctor verification
- 9:34What is Bridgetown
- 13:26Bridgetown architecture
- 16:20Roda in Bridgetown
- 19:49Server-rendered routes
- 21:35File-based dynamic routes
- 24:02Callable objects in Bridgetown 2.0
- 25:48Bridgetown project structure
- 27:33Prototyping DPC project
- 29:18Serious apps with Bridgetown
- 31:50Value of prototyping
- 33:36Ruby’s power with Bridgetown
- 34:16Closing
related talks
45mRuby Prototyping for Impact
32mImplementing Rails 3.1...
44mBuilding Distributed Applications
08mRuby startup demo – Alex Kalderimis
39mRoda: The Routing Tree Web Framework
30mRoda: Simplicity, Reliability, Extensibility, Performance
16mOne Ruby App to Rule Them All
01h 09mRails 3 ...and the real secret to high productivity