Templates
Every App Builder project starts from a template: a production-ready application that already works. A template is not an empty page. It ships with a map, a set of widgets, wired-up controls, and clean code, so you begin from something running and shape it from there.
Organized by category
Section titled “Organized by category”Templates are grouped by what you are trying to build, so you can pick the closest starting point:
- Web apps for interactive, multi-panel GIS applications.
- Web maps and Static maps for map-first experiences.
- Dashboards for metrics and charts over your data.
- Story maps and Reports for narrative and documents.
- Websites and One page for lighter, content-led sites.
The catalogue grows over time. Some categories are still on the way and appear marked accordingly in the gallery.
Free of any single map library
Section titled “Free of any single map library”ALIGN templates are not tied to one mapping stack. A template supports several map libraries, and you choose which one it runs on. MapLibre GL, the open map runtime, is the default. From your project settings you can swap to another supported library at any time, without starting over.
This keeps your app portable: your data, your widgets and your code do not depend on a single vendor’s map engine.
What a template gives you
Section titled “What a template gives you”When you create a project from a template, you get:
- a working map centered and styled sensibly,
- pre-built widgets you can configure without code,
- map controls already placed,
- and a real project structure you and the AI can extend.
From here, open the Interface overview to see where everything lives, or head straight to Working with the AI Assistant.