Low-Code Personalization With Flutter
summary
A Flutter app for couples uses on-device personalization by treating editor-provided JSON from a headless CMS as facts and plain-text expressions as business logic, evaluated with the Dart expressions package to yield true/false flags (achievements) rather than full Drools complexity. Facts live as map<string,dynamic>, persist across sessions with hydrated cubit, and custom Dart functions are exposed to expressions; prototype works but needs editor previews, input validation, documentation and webhook-triggered tests to avoid silent behavior changes.
AI-written summary · about
chapters (12)
- 0:00Introduction and context
- 1:49Personalization challenges
- 2:31Solution approach with rule engine
- 4:16Existing libraries and limitations
- 6:04Building a custom rule engine
- 7:31Simplifying the rule engine
- 8:55Content creator integration
- 9:59Handling facts and state
- 11:07Implementing feedback
- 12:32Common pitfalls and tips
- 13:55Documentation and testing
- 14:38Q&A and closing
related talks
13mRevolutionizing Smart Device Interfaces with Flutter: Any Screen, Any...
30mCat-like Development: Flutter for Efficiency
29mSimplify app development by building widgets in isolation
40mCreate simple, beautiful UI with Flutter
37mLessons learned from crafting an in-house framework
32m"Flutter: How we're building a UI framework for tomorrow at Google"
50mFlutter: The Wizards of Widgets
15mBuilding a desktop design language with Flutter