Webflow Marketplace / 03 of 08
Give app review evidence a clear origin
I worked on App Review Preflight to connect app artifacts, specific findings, and observed runtime evidence before a Marketplace review decision.
Selected professional work by Micah Johnson for Webflow, presented as individual portfolio work. Webflow did not commission this work through CREATE SOMETHING. Individual contributions are described within a wider team and platform context.
Contribution focus: Artifact analysis, immutable revisions, evidence provenance, and reviewer replay
Live Designer on the authorized demo site. Bundle/review-ZIP and hosted-script inputs only; no upload, job, receipt, runtime observation, site edit or publication.
Silent recording · Select captions for visual guidance. Open the MP4 ↗
The problem
Preflight App
An app bundle, a developer’s test report, and behavior observed in a running installation answer different questions. Combining them into one undifferentiated pass makes it difficult for a reviewer to know what was actually checked.
The contribution
The work behind the interface.
App Review Preflight has a developer surface in Designer and a reviewer workspace on the web. The workflow associates analysis with immutable revisions, so the evidence points to a particular artifact rather than a moving target.
The architecture distinguishes supplied source material from runtime observations collected by a server-owned browser. Reviewers can inspect the evidence and request independent replay. Read-only integration in the App Review MCP carries the receipt, bundle identity, readiness, and runtime context into the review workflow.
The key decision
What needed to stay clear.
Preserve who supplied the evidence, which revision it describes, and how it was observed. A Preflight receipt identifies evidence; it does not certify Marketplace approval.
The documented result
What the evidence shows.
The new authenticated Designer recording shows Preflight connected to the authorized Webflow Selection Box demo site. It demonstrates the app-bundle and private review-ZIP inputs, opens the hosted-JavaScript path, and returns without submitting. The implementation sources separately document immutable revisions and reviewer evidence.
The recording is an input-path walkthrough. No files were uploaded, analysis job started, receipt created, runtime observation performed, or reviewer replay demonstrated. The app connection was authorized only for the selected demo site; no design was edited or published.
Portfolio evidence captured October 2026. Historical implementation and recordings do not establish the current state of every production system.