ııı motion.mdVideo style specification
Lovable / V299

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.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 46.17 seconds
Motion and composition example Open separately ↗
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Lovable | Google connectors · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#101013}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="sequence"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>
Visual elementsCentral brandExternal tool iconsRequest cardResult interfacePointer
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Establish connections first

0.00s · Composition reference

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.

02

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.

03

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.

04

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.

SEQUENCE

Sections and rhythm

Click a section to seek to it in the choreography example above.

Composition reference at 0.00 seconds
0.00s
Composition reference at 6.00 seconds
6.00s
Composition reference at 15.00 seconds
15.00s
Composition reference at 27.00 seconds
27.00s
Composition reference at 34.00 seconds
34.00s
Composition reference at 45.00 seconds
45.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • 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 constraints

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