Data Binding Architectures for Rapid UI Creation in Unity
summary
Claims a reusable Unity framework that actually works: a typed message bus replaces string topics, a view‑model layer with editor bindings lets artists drag UI into scenes without code, and a mocking mode for isolated screens boots only the needed logic so designers iterate instantly. Reflection is handled once at startup via startup‑only reflection caching to avoid GC spikes. The team runs automated device tests against thousands of Android models (Google Play lists ~13,000 devices).
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:50Traditional UI challenges
- 5:00UI process goals
- 6:45MVC and MVVM patterns
- 9:58Proposed architecture overview
- 11:21Simple data binding example
- 12:03Dynamic UI with prefabs
- 13:26Performance in data binding
- 14:32Artist workflow improvements
- 15:35Mocking framework for testing
- 16:40Mocking in editor demo
- 17:44Unit testing benefits
- 19:08QA challenges and automation
- 20:54Device testing solutions
- 22:41Message bus details
- 24:07Existing Unity frameworks
- 25:32Architecture benefits summary
- 27:01Question and answer session
related talks
25mDeclarative 3D: Achieving integration SwiftUI and 3D
52mUnity: make development fun again!
47mA Functional Developer in the World of Games
04mIntervista a Andy Touch
41mAutonomous vehicle development with Unity
38mCreate Stunning Visuals: A New Workflow for Artists
01h 08mDesigning UIs with Qt Quick 1/6 - Design Workflow Part 1
17mCreating Immersive 3D Solutions with Microsoft Mesh