Flutter Templates

Open-source catalog of production-focused Flutter widgets and full app templates, built to help developers start polished mobile interfaces faster. Readable by coding agents through llms.txt, a registry, and a CLI with an MCP server.

Flutter Templates is an open-source library of Flutter UI patterns, widgets, and full app templates. The goal is to give developers a practical starting point for mobile interfaces that feel polished and are ready to customize.

The project includes reusable UI building blocks across common app needs like navigation, forms, layouts, chat interfaces, dialogs, empty and error states, e-commerce screens, social features, search, and animation.

Why I built it

Building a Flutter app often starts with recreating familiar screens and interaction patterns before the real product work begins. I wanted a place where developers could browse clean, production-focused examples and use them as a foundation instead of starting every UI from a blank screen.

What I built

  • A public website for browsing Flutter widgets and templates by category
  • Reusable examples for common mobile UI patterns
  • Full app templates and smaller snippets that can be adapted independently
  • A clean visual system for presenting previews, categories, and source code
  • An open-source codebase designed to be easy to inspect and extend
  • A machine-readable registry: one index of every screen, plus a JSON and a Markdown entry for each
  • An llms.txt that lists the catalog for agents
  • A CLI, fluttertemplates_dev on pub.dev, that searches the library and copies screens into a project as plain source files
  • An MCP server inside the CLI, so coding agents can search, read and add screens themselves

Built for agents too

More and more Flutter code is written by coding agents, and an agent cannot browse a gallery of previews. So every screen is also published as data. The registry at /r/index.json lists the whole catalog, and each screen has its own JSON and Markdown entry with the source, its packages and its license.

The CLI reads that registry. fluttertemplates add copies a screen into a Flutter project, installs any missing packages, and puts everything back if a step fails. Running fluttertemplates mcp starts an MCP server with four tools: search_widgets, get_widget, list_categories and add_widget. An agent can find a login screen and add it to the project without leaving the editor.

Terminal window
dart pub global activate fluttertemplates_dev
fluttertemplates search login form
fluttertemplates add auth/signup_terms

Engineering focus

The site is built with Astro, and the content is Flutter and Dart examples. The interesting part was treating this as both a design catalog and a developer tool. Examples need to look good, but they also need to be readable, copyable, and structured enough that another developer can learn from them.

What I learned

This project helped me think more deliberately about developer experience. A useful template library is not just a pile of attractive screens. It needs clear organization, predictable code structure, good previews, and enough polish that developers trust the examples before opening the source.