Build a Product Shoot App in Runway

• Open the Polaroid OneStep source page and select Original file.
• Save the 2,560 × 1,920 image as polaroid-onestep-source.jpg in a new Analog Weekend folder.
• Save the credit below as photo-credit.txt in that folder.
• Open the photo and locate the red button, rainbow stripe, lens, film slot, and lettering.

Photo credit to keep with the outputs:

Source photograph: "Polaroid One-Step" by Mike (squeakymarmot), via Wikimedia Commons.
Source: https://commons.wikimedia.org/wiki/File:Polaroid_OneStep.jpg
License: Creative Commons Attribution 2.0 Generic.
License link: https://creativecommons.org/licenses/by/2.0/
The generated versions change the setting and lighting with AI.
This is an independent practice project with no Polaroid affiliation or endorsement.

The source image shown here is “Polaroid One-Step” by Mike (squeakymarmot), used under CC BY 2.0. The generated concepts change its setting and lighting with AI. Keep that credit and license link with displayed images, and identify the AI edits. An image-search result alone does not grant reuse rights.

The source has a warm color cast. Use the cream body and its visible details as your reference rather than expecting a pure-white camera.

• You saved a small preview: Return to the file page and select Original file. Avoid a search-result thumbnail.
• The page saves instead of the photo: Open the original JPEG first, then use your browser's Save image action.

• Sign in to Runway and confirm your workspace's plan, App Studio access, and current credit balance.
• Open App Studio from the left sidebar. On first use, wait for setup and select Get started.
• Paste the build prompt into Describe the app you want to build…, then select the arrow.
• Choose a palette and Continue if the builder asks; leave the logo empty.
• Wait for Preview and check for the six controls named in the prompt.

App build prompt:

Build a private product photography app named Analog Weekend.

Use Runway's Nano Banana Pro image model for one image-editing call per click. Pass the user's original product photo as the image reference every time. Use portrait 3:4 and 2K output. If this model or these settings are unavailable, report the limitation before substituting anything.

Create these controls with these exact labels:
- Product photo: one required image upload.
- Keep these details: a required text field describing the product features to preserve.
- Scene: a dropdown with Coral Studio, Palm Shadow, and Midnight Blue.
- Extra direction: an optional text field, empty by default.
- Generate photo: generate one image only after a click.
- Download image: download the actual generated file, keeping its original format.

Use these scene instructions:
Coral Studio: A seamless coral-pink backdrop and a low, pale-aqua round pedestal. Soft studio light from the upper left. A clear contact shadow supports the product.
Palm Shadow: A warm cream tabletop against a pale-aqua wall. Afternoon light enters from the upper left. A palm-leaf shadow falls across the background, leaving the product unobscured.
Midnight Blue: A deep cobalt backdrop and dark-blue glossy surface. A soft circle of light sits behind the product. A white front light keeps the product's color and lettering readable. A restrained reflection sits beneath it.

For every scene, keep the product's original viewpoint, proportions, materials, markings, and wear. Keep the entire product visible at a similar size, centered in the lower two-thirds. Leave the upper quarter clear for copy added later. Create a believable product photograph. Include only the product and the selected set. Add no headline, people, extra products, or invented accessories.

Combine the selected scene, Keep these details, and Extra direction into the generation request. Keep the user's original upload as the reference, including on retries. Do not replace it with an earlier generated image.

Display the source thumbnail beside the result. Show the selected model, 3:4 ratio, 2K setting, scene, and attempt number. Show real usage information when available; label unavailable costs rather than inventing them.

Disable generation until a photo and preservation notes are present. Changing a field or uploading a file must not start a generation. Do not generate sample images while building. Disable repeat clicks during a run. Display a failed request as an error with a manual retry; do not retry automatically or substitute stock images.

Keep earlier results visible during the current session, each with its own download control. Warn that a reload may clear the session history. Do not claim permanent storage unless you implement and verify it.

Use built-in Runway services only. Add no external API, keys, payments, advertising connection, or public gallery. Keep the app unpublished for now. Tell me when the preview is ready and identify anything you could not build.

The builder creates the fields and buttons named in your prompt and connects the form to its generation step.

Runway's build guide explains the chat-and-preview workflow. A custom app fits repeated work; a one-off reshoot may need less setup.

• The sidebar shows Apps: Select Try App Studio in that panel. For a disabled workspace, ask its owner about access.
• The preview lacks a required control: Paste the correction below into the builder conversation. Inspect the new preview before generating.

Control correction:

Adjust Analog Weekend to match this required control list:
Product photo, Keep these details, Scene, Extra direction, Generate photo, and Download image.

Keep Scene limited to Coral Studio, Palm Shadow, and Midnight Blue. Show the source beside each real output, with its scene and attempt number.

Use the original upload as the reference for every attempt. Generate only on an explicit button click, one image per click. Do not make sample generations, add models, add external services, or publish the app while fixing these controls.

• Open the builder's three-dot More actions menu, then App settings → Models. Some layouts show a gear icon instead.
• Confirm the image step uses Nano Banana Pro; return to Preview.
• Upload polaroid-onestep-source.jpg through Product photo.
• Paste the notes below into Keep these details; leave Extra direction empty.
• Confirm the thumbnail. Ask the builder to confirm that the generation request uses 3:4, 2K, and one output; the result panel shows these settings after you start a run.

Product-preservation notes:

Use the uploaded Polaroid Land Camera OneStep photo as the product reference.

Preserve the cream plastic body, large round black lens, red shutter button on the viewer's left, rainbow stripe, black film-exit base, and raised black rear viewfinder.

Keep the OneStep name and POLAROID LAND CAMERA lettering in their original positions. Preserve the visible wear and the shape of the buttons, openings, and edges.

Keep the same three-quarter viewpoint. Show one complete camera at a believable scale. Change the surrounding set and its lighting while keeping the camera recognizable and its details intact.

Runway's Nano Banana instructions document image references, 3:4 output, and 2K resolution. This app uses that model for the photos; App Studio builds the tool around it.

Specifying the ratio matters because a reference image can otherwise influence the output shape. The original photo is landscape; this shoot uses portrait frames.

• Nano Banana Pro is unavailable: Check your workspace's model access. Stop this route if it cannot use the required model.
• The thumbnail is missing: Re-upload the JPEG and wait for it to load. Do not generate from the text alone.
• A model change alters the app: Wait for its rebuild, then recheck all six controls and the output settings.

• Select Coral Studio in Scene.
• Check the usage information and approve only one Generate photo request.
• Compare the result with the source at full size.
• Check the camera's six features and both markings against the notes below.
• Download an approved result, retaining its original format and the base name onestep-coral-studio.

Check the cream shell, round lens, red shutter button, rainbow stripe, film-exit base, and raised viewfinder. Read OneStep and POLAROID LAND CAMERA closely. The pedestal should support the camera, and the upper quarter should stay clear.

Look at the whole product before judging the set. A striking backdrop cannot make an altered lens or invented button accurate.

In our October 27 test, the download was a 1,792 × 2,400 PNG from a 3:4, 2K request. The two markings remained readable, but the model changed surface wear and small control details. We kept it as a creative concept, not an exact reproduction.

• A camera detail changes: Replace the bracketed placeholder below with the visible mismatch. Paste into Extra direction and generate one new attempt.
• The result is a square or landscape image: Ask the builder to apply 3:4 in the generation settings. Recheck before another run.

Product correction. Replace [DESCRIBE THE VISIBLE DIFFERENCE] with one specific problem:

Keep the original product photo as the image reference. Correct this mismatch in the camera: [DESCRIBE THE VISIBLE DIFFERENCE].

Match that detail to the original photo. Preserve the cream body, lens, red button, rainbow stripe, viewfinder, film slot, markings, and wear.

Keep the selected scene, portrait framing, and clear space above the camera. Keep the complete camera visible. Return one image.

Output-setting correction:

Correct only the image-output settings in Analog Weekend.

Keep Nano Banana Pro, the uploaded original photo, the selected scene, and the product-preservation notes. Set the generation request itself to portrait 3:4 and 2K, with one image per click. Do not stretch or crop a different-shaped output to disguise a wrong setting.

Show the applied settings and leave the app ready for my next click. Do not generate, retry, or publish while making this correction.

If repeated attempts alter the product, keep the image as a rough concept. Use a manual composite with the original product photograph when exact preservation is required.

• Clear Extra direction and select Palm Shadow.
• Generate one photo with the original upload, then inspect the camera and background shadow.
• Download an approved image with the base name onestep-palm-shadow.
• Select Midnight Blue, generate once, and check that the front lettering remains readable.
• Download an approved image as onestep-midnight-blue, then compare all three at the same viewing size.

Palm Shadow should place the leaf shadow behind the camera. Midnight Blue should keep the cream body readable against cobalt, with a small reflection beneath it.

Every request starts from the original photo. This avoids carrying a distorted detail from one generated scene into the next. Keep the camera's apparent size and viewpoint similar across all three.

Our first attempt at each scene produced a downloadable 1,792 × 2,400 PNG. The camera is smaller in Palm Shadow than in the other two, and the model reinterprets wear, reflections, and the small right-hand dial. Those differences belong in the review notes; matching prompt settings does not lock product pixels or scale.

• The blue lighting changes the product color: Paste the correction below into Extra direction and try one new image.
• A new result replaces an earlier one: Download the current image before leaving the page. Return to the builder and request separate result cards.
• A retry uses a generated reference: Restore the original upload and have the builder correct the reference passed to the model.

Blue-light correction:

Keep the selected Midnight Blue set and the original product photo as the reference.

Use neutral white front light on the camera. Preserve its cream body, black components, red button, rainbow stripe, markings, and wear. Keep the cobalt background and a restrained reflection below the camera.

Preserve the original viewpoint, portrait framing, complete product, and clear space above it.

• Download every approved result before leaving the preview.
• Select Publish in the builder.
• Check Who can open this app. If it is not Only you, change the audience and save it.
• Confirm Only you, then select Publish privately. Do not choose a workspace or public audience for this exercise.
• Reopen its link and check the controls without starting another generation.

Runway's sharing guide describes audience controls. Our test app's panel already showed Only you, but a new app or workspace may differ. Read the current audience before confirming. Later builder changes require another publish before they appear in the saved app.

The link is a way to reuse the tool. Keep the downloaded images separately, since your app's session history may not persist.

• The panel names your whole workspace: Change the audience to Only you before publishing.
• The saved link shows an older layout: Return to the builder, check the revised preview, and publish the change again.
• Publishing is unavailable while the builder is paused: Resume the saved session and wait for its preview before publishing. Download results first; pausing or reopening can clear preview history.
• The product upload is empty after reopening: Upload the saved original again. The app's controls can persist even when session inputs do not.

• Put the three approved downloads and photo-credit.txt in one Analog Weekend Review folder.
• Rename the files with the base names below, keeping their existing extensions.
• Open each file and confirm its dimensions are portrait 3:4, allowing for minor model rounding.
• Read both camera markings and inspect the buttons, stripe, edges, and contact shadow at full size.
• Record the app link, model, attempts, and any defects beside the images before handing them off.

Image base names:

onestep-coral-studio
onestep-palm-shadow
onestep-midnight-blue

Review record. Replace each bracketed field with your observed result:

Project: Analog Weekend
Purpose: Independent product-concept review
App URL: [YOUR PRIVATE APP LINK]
Model: [MODEL SHOWN IN APP SETTINGS]
Checked on: [DATE]

Coral Studio
File: [EXACT FILENAME]
Dimensions: [WIDTH x HEIGHT]
Attempts: [COUNT]
Decision: [ACCEPT / REVISE / REJECT]
Remaining defects: [NONE OBSERVED OR DESCRIBE THEM]

Palm Shadow
File: [EXACT FILENAME]
Dimensions: [WIDTH x HEIGHT]
Attempts: [COUNT]
Decision: [ACCEPT / REVISE / REJECT]
Remaining defects: [NONE OBSERVED OR DESCRIBE THEM]

Midnight Blue
File: [EXACT FILENAME]
Dimensions: [WIDTH x HEIGHT]
Attempts: [COUNT]
Decision: [ACCEPT / REVISE / REJECT]
Remaining defects: [NONE OBSERVED OR DESCRIBE THEM]

Source credit: Included in photo-credit.txt.
The images are AI-edited concepts. Review product accuracy before external use.

These three settings offer creative directions for a campaign. They do not establish which image will sell more. Keep the original photograph, every approved export, and the reusable app together in your project record.

For a client review deck, place the source beside the three concepts and include the attribution on the same page or an accessible image-credit page. Label the changed settings as AI edits.

• The download is a thumbnail or screenshot: Use the result's Download image control and check the saved file again.
• The file extension disagrees with its format: Keep the original extension. Renaming a JPEG to PNG does not convert it.
• One image fails the product check: Exclude it from the approved set. Repair that preset and replace only its export.