# Set up your app

Find your app, keep its configuration and follow the four setup steps.

Version 0.1.0 · Early pilot · unreleased SDK · Reviewed 4 November 2026

## Add a new app or resume an existing one

Open App setup from your workspace. Add app starts a new setup; reopening an existing app resumes its Connect step without creating another app or changing its public configuration. Only an owner or admin can create or edit an app. Setup progress and incomplete requests are scoped to the signed-in operator and selected workspace.

## Find the correct App Store listing

Search with an app name, numeric Apple App Store ID or apps.apple.com link. Choose the storefront and inspect the title, developer and icon before selecting. An exact URL or ID fills the phone preview as soon as Apple’s matching result arrives. Scroll through the real listing, switch iPhone/iPad screenshots, enlarge an image, and expand the description or release notes. Ratings, price, compatibility and information use Apple’s returned values; unavailable fields stay omitted. The preview displays the App Store listing and does not run the installed app. An exact ID is the clearest way to distinguish similarly named apps. The listing supplies display metadata; it proves neither app ownership nor customer identity. If search is unavailable or the app is unpublished, choose My app isn’t on the App Store yet and enter its name manually.

## Choose a monitored support email

A valid support email is required for the app. Use an inbox your team actually monitors; hej can offer it when chat cannot accept a new message. An App Store search does not discover or verify that inbox. Existing-app edits retain the same public configuration and conversations.

## Connect with your own hej instructions

Connect contains Copy setup prompt, Preview prompt and Set up manually. Choose Swift, Expo or Flutter for the intended host. The instructions use the selected app’s actual origin, public configuration and explicit environment. The prompt asks your coding agent to inspect that host, agree the Help entry and optional non-sensitive context, then use the shipped hej APIs for the chosen platform. Review the instructions before sharing them. Each manual path includes its actual source archive and integration example. Swift is the fuller iOS SDK; Expo and Flutter are guest foreground text pilots with their own limits.

- [Install the native iOS SDK](/docs/installation)
- [Check supported Swift APIs](/docs/sdk-reference)
- [Set up Expo foreground chat](/docs/expo)
- [Set up Flutter foreground chat](/docs/flutter)

## Read actual connection checks

Run your own app, open Help and send a synthetic development question. The panel distinguishes configuration fetched, support session registered, customer message accepted, human reply committed, reply fetched and reply displayed. Observations belong to the selected app/environment and can include another build; send a fresh test from your installation. Copying a prompt or viewing the illustrated phone never passes a check. Connect later leaves unobserved checks waiting.

## Integrations, plan and a way back

Integrations are optional. A configured key is separate from an observed push, provider event or Telegram reply. The Plan step shows workspace billing separately from free development setup. Save and exit retains the current step and unsent app draft; an uncertain app save retains its complete original request for retry. Back and reopening App setup let you continue later.

- [Understand connection readiness](/docs/integrations)
- [Read the workspace plan and limits](/docs/limits)