Google Gemini | Connected apps expand creative workflows

Google began rolling out new connected apps for Gemini on September 23, including Adobe, Picsart, Squarespace, and Webflow in its creativity category. The announcement covers visual asset creation and website work. For designers, the useful question is how a conversation can help move a clearly defined creative task into the application that supports it.


Creative applications connected to Google Gemini

{getToc} $title={Table of Contents}

Gemini adds more creative connections


Connections can be started through Gemini settings, an @ mention, or a direct request in the conversation. The rollout adds an entry point to the listed services; it should not be treated as a complete specification of every tool available through each one. Confirm the connected application's actual options before promising a particular production result.


Start by identifying the output rather than choosing an application name first. A campaign image, a revised visual, and a website section require different decisions. Stating the intended result, audience, and delivery context can help the creator decide which connection is relevant and what material needs to be prepared before work begins.



Choose the application around the task


A conversational brief should include the constraints that would matter in an ordinary design handoff. These might be the approved copy, the required dimensions, the subject that must remain recognizable, and the visual direction. Leaving them implicit can lead to an attractive draft that still needs substantial revision before it meets the real assignment.


When more than one service is involved, keep the purpose of each step explicit. Exploring an image and preparing it for a page are related activities, but they have different review criteria. Agreeing on the asset first can make the next stage easier to evaluate, because collaborators know which visual decisions are already settled.


Keep the brief consistent across services


Maintain a short record of the approved brief as the work progresses. This can help a team spot whether a later request has changed the intended message or visual emphasis. It also gives reviewers a reference when an output looks polished but no longer expresses the idea that prompted the project.


An early test should include the output in its intended context. Place a proposed image beside the actual headline or review a website element with the surrounding content. This is where design decisions become easier to assess: contrast, hierarchy, subject placement, and copy length can all affect whether the result communicates well.


Check availability before planning a full workflow


Because availability is rolling out, check that the desired connection appears in the account before building a production plan around it. Review sign-in requirements and the service's relevant access conditions during setup. A connection being announced does not establish that every account already has the same experience or the same allowance.


Use a small task to establish the division between conversational requests and hands-on refinement. Record which adjustments can be made clearly through the connection and which need the application's own editing controls. That observation can guide a practical workflow without assuming that an entire creative project should stay inside one conversation.


Daisuki's Take: What This Means for Designers


We see the expansion as another way to connect an initial brief with tools used for making the result. The strongest use is likely to be a well-scoped task whose output and review standard are already clear.


We would keep creative ownership visible as work passes between services. Someone still needs to approve the copy, choose the visual direction, and check the final asset in context, even when the starting request feels simple.


Try one connection with one concrete deliverable. If it reduces the effort between brief and usable output, build on that result. The connection earns its place when it helps the project move forward with fewer misunderstandings and a clear route to final refinement.



Sources and Recommended Links