# Lovable | Google connectors
Turn connectors from icons into executable tasks: each tool first enters a request, then produces a corresponding application, before all results are gathered into a group.
```motion-demo
{
"id": "sequence",
"title": "Overall choreography",
"src": "demos/sequence.html",
"duration": 46.166667,
"status": "authored",
"description": "Motion and composition example",
"initialTime": 7.2,
"params": [
{
"key": "title",
"label": "Sample main copy",
"type": "text",
"value": "Google × Lovable",
"maxLength": 60
},
{
"key": "accent",
"label": "Accent color",
"type": "color",
"value": "#ed3b99"
}
],
"presets": [
{
"label": "Default content",
"values": {
"title": "Google × Lovable",
"accent": "#ed3b99"
}
},
{
"label": "OpenDesign adaptation",
"values": {
"title": "OpenDesign",
"accent": "#7050da"
}
}
]
}
```
## Establish connections first
Arrange external tool markers around the central brand, with lines or orbits expressing connections only. Then turn one tool into a tag in the input field, bringing the abstract connection into the first real request.
A dark background and soft gradient lighting create a unified stage, while tools retain their own brand colors. Use bold sans-serif for product headings and regular weight for inputs, options and interface data.

## Give each kind of tool a corresponding result
Data requests produce dashboards, product information produces selectors, bookings produce calendars, email tasks produce replies, and location requests produce maps. Do not depict every tool's results as bar charts.
Leave room for an actual interaction after the result appears: select a size, choose a time, confirm a reply or choose a location. A click must produce a selection, confirmation or content update.
## Leave reading space between request and interaction
Advance each example through a tool tag, short request, result and local interaction. Examples may cut quickly between each other, but the states before and after a click must be distinguishable. At the end, shrink different results into a wall of work, emphasizing one entry point for many tasks.
| Time | Section |
|---|---|
| 0.00–4.00s | Surrounding connector icons |
| 4.00–6.00s | Data request |
| 6.00–10.00s | Dashboard |
| 10.00–15.00s | Shoe selection app |
| 15.00–18.00s | Booking request |
| 18.00–22.00s | Calendar selection |
| 22.00–27.00s | Email task |
| 27.00–31.00s | Send reply |
| 31.00–34.00s | Map request |
| 34.00–39.00s | Store selection |
| 39.00–45.00s | Results wall |
| 45.00–46.17s | Brand |
## Change the tools along with the business context
Choose the data sources and tools required by the new business context, then design corresponding results. Adapt prompts, connector tags, data content and interaction options together; preserve the relationships from tools to tasks and from tasks to results.
## Color and typography
Sans-serif interface text with a clear size hierarchy.
#101013 · #ffffff · #ed3b99 · #778df2 · #fb6740
## Elements and production rules
Central brand / External tool icons / Request card / Result interface / Pointer
- Multiple tool icons gather first, then become connector tags in the prompt field one by one
- Show an actionable result after each request, with local clicks producing selection feedback
- At the end, different results shrink into a wall, emphasizing one connection system serving multiple tasks
## Content replacement
- When adapting the theme, retain the four-beat structure of tool → request → result → interaction
- Replace the actual tools and data along with the result types, rather than merely replacing the logo
## Production parameters
[Visuals and objects](style.json) · [Section timing](timeline.json) · [Position data](tracks.json) · [File manifest](manifest.json)
This specification is based on the reference video. The HTML provides editable choreography examples; each file identifies the source, precision and valid interval of its data.
```motion-board
{
"version": 1,
"brand": "Lovable",
"id": "V299",
"palette": [
"#101013",
"#ffffff",
"#ed3b99",
"#778df2",
"#fb6740"
],
"typography": "Sans-serif interface text with a clear size hierarchy",
"sample": "Google × Lovable",
"objects": [
"Central brand",
"External tool icons",
"Request card",
"Result interface",
"Pointer"
],
"frames": [
{
"path": "assets/reference-1.jpg",
"timeSeconds": 0.0,
"frameId": "K0001",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-2.jpg",
"timeSeconds": 6.0,
"frameId": "K0026",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-3.jpg",
"timeSeconds": 15.0,
"frameId": "K0071",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-4.jpg",
"timeSeconds": 27.0,
"frameId": "K0128",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-5.jpg",
"timeSeconds": 34.0,
"frameId": "K0156",
"role": "reference-evidence",
"status": "measured"
},
{
"path": "assets/reference-6.jpg",
"timeSeconds": 45.0,
"frameId": "K0200",
"role": "reference-evidence",
"status": "measured"
}
],
"stages": [
{
"start": 0.0,
"label": "Surrounding connector icons",
"end": 4.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 4.0,
"label": "Data request",
"end": 6.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 6.0,
"label": "Dashboard",
"end": 10.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 10.0,
"label": "Shoe selection app",
"end": 15.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 15.0,
"label": "Booking request",
"end": 18.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 18.0,
"label": "Calendar selection",
"end": 22.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 22.0,
"label": "Email task",
"end": 27.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 27.0,
"label": "Send reply",
"end": 31.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 31.0,
"label": "Map request",
"end": 34.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 34.0,
"label": "Store selection",
"end": 39.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 39.0,
"label": "Results wall",
"end": 45.0,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
},
{
"start": 45.0,
"label": "Brand",
"end": 46.166667,
"status": "inferred",
"basis": "Representative-frame review; approximate boundaries"
}
],
"duration": 46.166667,
"fontFamily": "Arial, sans-serif"
}
```