Name the exact Runway surface
A merchant likes the Product Shot Video Builder App on Runway’s website and wants a contractor to run the identical workflow from an iPhone app or a nightly API job. These are different access contracts. Runway documents Apps as use-case-specific workflows, lists Product Shot Video Builder among them, and states that Apps are unavailable in the native iOS application and inaccessible through its API. A visible App link is not an API endpoint. First record the exact App, desired input, output and automation requirement.
Route the mobile request correctly
If the merchant simply needs to use an App from a phone, the official guidance points to a mobile browser rather than the native iOS app. Confirm the actual App page, account access, accepted inputs and visible credit quote there. Do not promise that every App behaves identically or that a mobile browser provides all desktop conveniences. If the contractor is blocked in the native app, switching the same account to a supported browser route is a sensible next check, not evidence that the App was discontinued.
Route automation as a different product decision
If the merchant needs unattended overnight generation, the Runway Apps UI is not a supported API surface. Define the intended steps—product image selection, motion direction, generation, review and export—and investigate the provider’s separately documented developer API models or workflows for those steps. Do not invent a Product Shot Video Builder API call, assume that App Studio publishes an API endpoint, or promise equivalent results. Agent and Tool Mode support broader interactive work, but the official Apps article does not convert them into an App API.
Fictional launch with two teams
A hypothetical homeware merchant has an approved lamp photograph and wants a five-second teaser. The social editor needs one browser-based App session, while the catalog engineering team wants hundreds of clips scheduled through an internal service. The first requirement may be evaluated through the website App. The second requires its own documented API feasibility review, cost estimate and human approval stage. The retired product-video entry guide concerns another provider, while product URL versus first-frame inputs helps identify the source role without establishing Runway API support. A failed attempt should be classified before escalating. If the App is absent only in the native iOS client, inspect the documented browser route. If the App opens but the source is rejected, inspect that App’s upload instructions. If a developer receives no App API endpoint, that is a documented product boundary, not an authentication error to solve with repeated tokens.
Keep the output review and access proof separate
Record the surface used (website, mobile browser, native app or developer API), App identity, visible inputs, current account permissions and provider credit quote. Then inspect any actual output for lamp geometry, logo and claimed operation. If a team requires API parity with the App, hold that architecture until a supported API contract is established. CartVisual does not execute Runway Apps, expose their endpoints, or guarantee the same generation through another route.