How to promote an app when its useful screens are behind a login
Use your public page to explain the product, and use a separate demo environment to capture private workflows. A website-to-video service cannot show what it cannot access. Do not make a production account public just to create a launch asset.
This is a common distinction for dashboards, internal tools and SaaS applications. The landing page communicates the promise; the authenticated application supplies evidence of how the task works.
Choose what the video needs to prove
A short announcement can introduce the audience, problem and benefit using the public page. A workflow demo needs to show a real sequence: input, action and result. Write that sequence before deciding which screens to capture.
If a feature is not ready, label a concept as a concept. A polished reconstruction should not imply that visitors can use a workflow that does not exist.
Prepare a safe demo environment
Use fictional names, files and transactions that are realistic enough to explain the task. Remove personal emails, tokens, customer details and unrelated browser content. Check the resulting footage, not just the environment before recording.
Shopify's file guidance puts the public-upload distinction plainly: “Never upload any documents that contain confidential, personal, or sensitive information”. Its instruction applies to Shopify's public file area, but the same distinction is useful when deciding what belongs on a public marketing page. Shopify product-media guidance.
Do not share a password in a video-production note. For a private workflow, create approved recordings or a purpose-built public demonstration instead.
Record one complete task
Capture the smallest sequence that proves the point. OBS is one recording route. Show the input clearly, perform the action and leave the result visible long enough to inspect.
Keep errors and edge cases in supporting documentation unless they are the point of the demonstration. Do not edit out necessary steps in a way that changes the claimed capability.
Pair the demo with a public overview
| Asset | What it should do |
|---|---|
| Public landing page | Explain who the app serves and what it does |
| Short promo | Introduce one reason to investigate |
| Recorded task | Demonstrate the relevant workflow |
| Supporting instructions | Answer setup and operational questions |
For the public-facing overview, Teasr lets you start with the landing page and review a short branded promo without assembling the video yourself. It does not log into your product or record the private task. Keep those roles explicit in the brief.
Before posting, inspect the full export for exposed data, inaccurate UI and unsupported claims. For the production choice, see screen recording vs animation. For a concise SaaS brief, see making a SaaS promo.