From No‑Code to Build‑Ready: Exact Exports & Checklists for Webflow, Figma, Adalo & Bubble

What to export: a developer needs the working Figma file (shared with Editor or View access), a flattened component page, all exported assets (SVG for icons, 1x/2x PNG for raster images), a JSON export of tokens (colors/typography) if you use tokens, and a short design‑system README describing component props and breakpoints. Use Figma’s Dev Mode / Inspect to let devs copy CSS variables and measurements, but still export canonical assets rather than relying on screenshots.

Naming and variants: adopt deterministic file names so scripts and devs can locate assets. Use folder and layer prefixes: icon/ for SVGs, img/ for raster backgrounds, logo/ for logos. For multi‑resolution assets use suffixes: logo@1x.png, logo@2x.png, icon.svg. Export SVGs with 'Outline strokes' off when developers need editable vectors and include an 'export-metadata.json' listing frame name, platform (web/ios/android), and intended use.

Webflow exports a ZIP of HTML/CSS/JS and assets — but don’t hand that ZIP alone. Developers need a developer zone map: a small Markdown file that maps Webflow pages/classes to intended backend routes or React components (e.g., /products → ProductList.jsx). Export the code ZIP, and separately export images (unminified SVGs and source PNGs), any custom scripts, and a list of site interactions with short summaries (what triggers them, expected behavior).

Naming and structure: keep Webflow class-to-component mapping in a machine‑readable mapping.json (example below) and include instructions about which CSS is intentionally global vs generated. If you used the CMS, export CMS CSVs for collections and include sample CMS items. If you used Webflow forms, export a list of form IDs and the intended back‑end endpoints the contractor should implement.

Bubble does not export a production‑ready codebase; you can export data and certain app definitions. For a handoff, export your full database CSVs, a JSON or spreadsheet that documents data types/field constraints and relationships, and a named list of API endpoints (Bubble API workflows) with sample requests/responses.

Additionally, capture workflows and page flows as annotated screenshots or a short exported document. Because Bubble workflows are platform‑specific, include a 'rebuild spec' — for each workflow, list the trigger, expected validations, side effects (emails, DB writes), and precise acceptance tests the contractor should run.

Adalo does not provide full source code export. For a developer to port an Adalo app, export CSVs of collections, export all images/files used in the app, and create a manifest that lists screens, components used on each screen, and navigation flows. Capture any custom formulas, computed fields, or third‑party integrations used so developers can reimplement logic server‑side if needed.

Also export a small 'runtime map' describing which screens expect native behaviors (push notifications, deep links), what authentication providers are configured, and the exact API keys or third‑party services (migrated to a secrets file) used in the app. Without this, contractors will waste cycles re-discovering integration behavior.

Across tools, contractors want the same core artifacts: canonical design source, exported assets with deterministic names, data exports (CSV/JSON), API contract examples (requests & responses), and short acceptance tests for each major flow. Put these artifacts in a single /handoff folder in your repo or cloud drive with a top‑level README that links to each file.

Below is a copyable one‑page checklist you can paste into the README of your handoff bundle. Treat this as the 'must have' list — anything missing will trigger clarification tickets and slow the build. If you use AppWispr to manage contractors, this same checklist works as a project preflight before you start the sprint.