Start with owned web screens and at least two real cards you may share. Record an actual viewer test before accepting the result. BIG CHANGE read the documentation on 26 October 2026 but ran no account test.
The big change
- What changed: Google documents a route from Stitch designs into a shareable app.
- Why it matters: An owner can check a useful filter before sharing.
- What to watch: Stop when a required result is missing.
1. Set the acceptance cases
Confirm rights to every screen, asset and card. Verify Stitch and AI Studio Build access and an approved viewer. Check regions and account access: AI Studio requires users to be 18 or older, and age verification or administrator help may apply. Check displayed cost and allowance.
Fill this record from your project. Choose one query that matches a real card and another that matches none. Save the approved screen and narrow layout for comparison. If the screen has no cards, define and review a different task first.
Stitch project URL/name:
<owned project>
Web screen IDs/names and
reviewed revision: <actual>
Content and asset rights:
<owner/license decision>
Build/recipients: <actual>
Purpose and intended viewer:
<actual>
Cards: <at least two real
permitted items>
Each title and search terms:
<actual for each item>
Positive query -> items:
<query and expected names>
No-match query -> message:
<query and approved copy>
Cleared query -> all cards:
<actual item list>
Visual baseline: <copy, assets,
layout, narrow state>
Stop conditions: <missing route
or screen; rights; behavior;
visual drift; access; cost>2. Export the screens
Select the reviewed web design in Stitch. A February 2026 forum reply describes Export in the toolbar. Choose AI Studio only if that destination appears. Google's March announcement names the export; its May update describes a sharing route. Neither fixes today's menu or filenames. Record the option and resulting project. Stop if the destination or selected screen is absent.
A March forum reply said prototype export was unavailable then. Use the selected screens as your baseline; the dated reply is no current guarantee. Inspect the imported screen in Preview and files in Code. A forum thread reports visual drift and suggests more precise prompts. Record any difference and hold one the owner rejects.
3. Request and check the filter
Send this filled prompt in Build chat.
In this imported app, retain
the reviewed screen <actual
screen ID/name> and approved
visible content. Add a labelled
text input to filter the cards
<actual items> by approved
search terms. Use only local
client-side state. Add no API,
model call, database, sign-in,
analytics, secret or device
permission. Empty query: show
all approved cards. Positive
query <actual>: show only
<expected items>. No-match
query <actual>: show the
approved message <actual>.
Keep keyboard input, clear and
reset, and the approved narrow
layout.
List changed files and show
relevant code. If the screen or
data is missing, stop and ask.Enter the positive query and compare names and count with your record. Try the no-match query and check its message; clear the input and check every card returns. Inspect state, search terms and reset logic in Code. Check keyboard use, narrow layout and the Stitch baseline. Record any failure, make a scoped correction and rerun all three cases.
4. Inspect and share with the intended viewer
Review changed files, dependencies, routes, calls, permissions, secrets and visible data. Remove private, unlicensed or unapproved material and retest. The filter needs no model call. Google says apps start private; recipients can see and fork code, while editors can change it. Shared API use counts to the owner; paid models may cost money. Review any separate AI feature and store its key in server-side secrets.
Use Share → Integrations → Shared URL (Google's manual). Give access to the approved recipient. Open the link as that viewer, using their authorized sign-in if needed, and repeat the three cases. For restricted access, check that an uninvited identity cannot open the app or inspect its code. Record the viewer's actual result.
For a 403, check recipient and account eligibility. Google also lists extension and build errors. Change an extension only with viewer consent. Inspect a code fix and rerun all cases. Keep restricted access while diagnosing. Read usage and costs after the viewer check; hold unexpected charges or permissions.
Stitch project/screen/revision
and baseline: <actual>
Export option/destination and
UTC: <actual>
Imported ID/screens/files:
<actual>
Code changes: <actual>
Positive query / expected /
observed: <actual>
No-match query / expected /
observed: <actual>
Clear / expected / observed:
<actual>
Keyboard and narrow layout:
<actual>
Differences from Stitch:
<actual>
Data, code, cost approval
and date: <actual>
Shared URL, viewer and access:
<actual>
Viewer sign-in, access and
three-case retest: <actual>
Uninvited denial if restricted:
<actual>
Post-test usage/cost:
<actual or unresolved>
Decision: <accepted / design
hold / behavior hold /
access or cost hold /
inconclusive>
Next action and owner: <actual>This result is a checked shared app for the intended viewer. Cloud Run hosting, persistence and production access require separate requirements and review. For related tasks, see our Stitch DESIGN.md-to-Claude components guide and AI Studio-to-Cloud Run guide.
