Blinkin Legacy Docs Docs
Manuals · manuals/03-create-and-publish-app.md Docs Home

Manual 03: Create And Publish An App

What This Guide Is For

Use this guide to create an interactive App or Companion, add steps, collect data, preview it, and publish it.

Before You Start

You need:

  • permission to create Apps or Boards;
  • a goal for the experience;
  • optional: media files, form fields, and an Agent;
  • optional: integrations or webhooks for submitted data.

Step 1: Create A New App

  1. Go to Apps, Companions, or Boards.
  2. Select Create.
  3. Choose a starting type:
    • blank App;
    • Companion;
    • Board-based workflow;
    • template.
  4. Add a name and short description.

Expected result: a draft opens in the editor.

Step 2: Add Steps

  1. Open the editor canvas or step list.
  2. Add the first Step.
  3. Add content to the Step, such as text, image, video, button, or form.
  4. Add more Steps as needed.
  5. Connect Steps with navigation or routing.

Expected result: the App has a clear path from start to finish.

Step 3: Add Forms Or Inputs

  1. Select the Step where users should enter information.
  2. Add form fields.
  3. Choose field types such as text, email, phone, file, image, video, audio, date, dropdown, checkbox, GPS, or live capture.
  4. Mark required fields.
  5. Save.

Expected result: the runtime can collect structured user input.

Step 4: Add Logic

Use logic when the next Step depends on user input, button choice, form data, or an Agent result.

  1. Add a router or condition.
  2. Define the rule.
  3. Connect the possible next Steps.
  4. Preview the route.

Expected result: users follow the correct path based on their answers or state.

Step 5: Add An Agent

  1. Select a Step that should use AI.
  2. Attach an Agent or AI action.
  3. Choose what the Agent should receive as context.
  4. Choose where the Agent result should appear or which field it should fill.
  5. Save.

Expected result: the App can use an Agent as part of the experience.

For a more advanced setup where a Studio visual flow launches an App or Agentic App as one Step, see 08-studio-visual-flow-agentic-miniapp.md.

Step 6: Preview

  1. Select Preview.
  2. Walk through the App as an end user.
  3. Test required fields, routes, media, and Agent behavior.
  4. Fix any errors.

Expected result: the preview behaves like the intended public version.

Step 7: Configure Sharing

  1. Open Share or Publish settings.
  2. Choose access:
    • public;
    • password protected;
    • workspace only;
    • external users or groups.
  3. Configure branding if needed.
  4. Configure embed mode if the App should live on another website.

Expected result: the App has a clear access rule.

Add A Password To The Published App

Use this when the App should be reachable by link, but only for people who know the password.

  1. Open the App draft or published App settings.
  2. Go to Share, Access, or Publish settings.
  3. Set access mode to Password protected.
  4. Enter the password.
  5. Save the access settings.
  6. Publish the App if the password should apply to the public version.
  7. Open the public link in a private browser window.
  8. Confirm that the App asks for the password before any runtime content loads.
  9. Enter the correct password and confirm the App opens.
  10. Enter a wrong password in a new private session and confirm access is denied.

Expected result: the public link still exists, but visitors must pass the password screen before the App loads.

To change the password, return to Share, Access, or Publish settings, replace the password, save, and test the public link again. To remove the password, change access mode back to Public, Workspace only, or External users or groups, then save.

Step 8: Publish

  1. Review the draft.
  2. Select Publish.
  3. Confirm that a new published version should be created.
  4. Copy the share link or embed code.

Expected result: users see the stable published version, while draft editing can continue separately.

Step 9: Check Results

  1. Open Results or Insights.
  2. Check sessions, submissions, files, completion rate, and user path.
  3. Export data if needed.

Troubleshooting

  • If publishing is blocked, check required fields and quota limits.
  • If the public link asks for a password, check access settings.
  • If form data is missing, confirm the Step has a form and the submit action is configured.
  • If embed does not load, check domain, iframe permissions, and publish status.

Product Decisions Needed

  • Final product name: App, Companion, Blink, or Board.
  • Exact draft/published version labels.
  • Whether publishing requires review for workspace-wide Apps.