---
uid: application-development.modelling.about-designers
description: "Designers in Intent Architect provide visual modelling of domain entities, services, eventing, and UI structure, driven by installed module configuration."
---
# About Designers

Designers in Intent Architect allow you describe your [application's](https://docs.intentarchitect.com/docs-md/application-development/applications-and-solutions/about-applications/about-applications.md) design as visual models and hierarchical concepts. For example, Designers could be used to describe: the entities in a domain, the services that make up the applications API, events that are published and subscribed, etc.

Designers are added to an [Application](https://docs.intentarchitect.com/docs-md/application-development/applications-and-solutions/about-applications/about-applications.md) when a [Module](https://docs.intentarchitect.com/docs-md/application-development/applications-and-solutions/about-modules/about-modules.md) that has designer configuration is installed. You can therefore choose which Designers you would like to use in your Application.

![Domain Designer](images/designers-domain.png)
_An example of a sample application showing a Domain Designer with a modelled domain._

Designers serve as a **blueprint** of your system. They can be used to describe any aspect of your Application. The following are some examples of what they are used to capture:

- **Codebase Structure** - Visual Studio Projects in .NET, Folder Structures in other languages, etc.
- **Entities** - Entities and their relationships to one another, Domain Driven Design (DDD) concepts (Aggregate Roots, Entities and Value Objects), etc.
- **Database Schemas** - Tables, Documents, Foreign keys, Indices, etc.
- **Services** - RESTful web services, SOAP services, security settings, transactional settings, etc.
- **Client Proxies** - Web client proxies, Synchronous Query Proxies, etc.
- **Eventing** - Messages, Topics, Queues, Subscriptions, etc. Often used to support a Microservices architectures.
- **Workflows** - Workflow Diagrams, Process Diagrams, etc.
- **Front-End Structure** - Components, Routing, Modules, View Models, Views, etc.

Intent Architect Designer behaviour and element visuals are configuration driven and [module authors are able to make Designers](https://docs.intentarchitect.com/docs-md/module-building/designer-extensions/about-designer-extensions/about-designer-extensions.md) perfectly suited to just about any scenario.