Every team has a job it does the same way every week, usually held together by a saved prompt and one person who remembers the settings. Runway’s App Studio, announced October 26, is meant to turn that kind of job into a small tool with its own interface. You describe what you want, and Runway builds and hosts it. No code from you, no API keys to manage.
What changed
You type what the app should do, and a single sentence is enough to start. An agent plans and builds it while you watch a live preview, and partway through it asks you to pick a color palette and optionally add a logo. After that you keep asking for changes, or select an element or draw on the preview to show what you mean.
A few things make this more than a chat box with a nicer skin:
- Existing work converts. Runway says you can turn an Agent session or Workflow into an app in one click. The prompt, model chain, and settings get locked, and teammates only see the inputs they need.
- It connects to your brand setup. Apps can use Brand Kits, Workflows, Assets, and References, and Runway says updating one of those means new outputs reflect the change.
- Models are swappable. Each generation step lists its model in the app’s settings, and you can choose a different one.
- The code isn’t hidden. There’s a Code tab to read the app’s files, and you can download the source as a zip once it’s published.
- There’s a Store of ready-made apps. Runway’s launch set includes tools for swapping a product into footage, retouching only a marked area of an image, and setting camera moves in 3D space. You can remix these into your own versions.
Runway’s early-access examples give a better sense of the range than the feature list does. They include animating design renderings along a drawn camera path, localizing end titles, and matching background plates.
Why it matters for designers
The useful shift here is who gets to hold the craft. A senior designer can work out the prompt, model, and reference that actually give on-brand results, lock those in, and hand the team a form with three fields. That’s a real answer to the problem of everyone getting slightly different output from the same brand.
It also makes small internal tools realistic for teams without a developer. A tool for resizing a campaign or generating one approved kind of product shot used to be hard to justify building. Now it costs some credits and a few rounds of description, so it’s worth asking which of your repeat jobs are predictable enough to package.
What to watch out for
Check your credits before you plan around this. The help guide says you need a minimum balance of about 700 credits to start a build session, and Runway’s pricing page lists Standard at 625 credits a month. On those numbers a Standard subscriber’s monthly credits alone don’t reach the minimum, so you may need more credits or a higher plan. Pro lists 2,250 a month. Standard also doesn’t list a Brand Kit on the pricing page, while Pro lists one and Max lists up to three, which matters if brand consistency is why you’re here.
Runway’s own pages disagree about public links. The launch post says paid plans can publish a public link, with visitors signing in and spending their own credits. The sharing guide’s FAQ says there’s no public link option and that everyone needs an account that can sign in to your workspace, even though a step in that same guide lists “Anyone with a link” as an audience. If you were hoping to hand an app to a client, confirm it works on your account before you promise that.
Sharing with your team may depend on your plan. App Studio is on every paid plan, but the launch post says it’s Team and Enterprise customers who can share apps with specific teammates, a project, or the whole workspace. If that’s the reason you’re building one, check what your plan allows first.
Runway’s terms count App Studio apps as your applications, and they say applications made available to end users must prominently display “Powered by Runway” and link to runway.com. Keep that in mind if you’re building something a client or the public will see.
You can’t take an app down yet. The help guide says there’s no way to delete or unpublish one. You can set the audience to “Only you,” which takes effect immediately, but the app still exists. Workspaces also have an app limit, and unpublished apps and examples from the Store count toward it.
Read the terms before you run client work through it. Runway’s terms say inputs and outputs may be used to train its models. They say apps may be incomplete or insecure and come without warranties, and using an app another user built is at your own risk, including that what you submit may be shared with its creator. Published apps can also reach the internet unless that’s turned off for the workspace, so it’s worth knowing what a remixed app connects to before you put anything sensitive in it. The sidebar has the details.