Everybody loves making small changes easier: many apps have moved copy changes -even color schemes or page layouts- to be dynamic and data-driven. But what if we set up the entire app -navigation and all- based on server-provided information? Let's explore the concepts behind schema-driven applications: how they work, why they're awesome, and how to do them right.

Let's explore the world of server-driven layouts as a concepts-driven experience. We'll show how things work, rather than integrating with existing production-ready libraries or services.

For each of the following, we'll first cover why you'd want to do it, then an overview of minimal code to get it to work:

1. Moving small bits of app information such as text snippets to the server allows for easier experimentation and marketing changes
2. Allowing generating entire routes/screens/pages based on JSON descriptions of building blocks
3. Creating application templates that can be hooked up to generic data sources as straightforward as JSON files or as intense as business-grade CRMs
4. Performance concerns around intelligent caching & over-eager loading
5. Combining these techniques with realtime WebSocket-powered over-the-air updates, for truly dynamic applications

Attendees should take away an appreciation for the vast amount of time they can save by making their applications highly dynamic and data-driven. If at least a few developers are saved from having to manually do the same work repeatedly, this talk will have done its job!