Launchpad
Launchpad is the page a visitor sees when your link can't open the app: on a desktop, where there is no app to open, or on a phone that doesn't have it installed. It shows the link's title, description and image, your app's name and icon, App Store and Google Play buttons, and — on desktop — a QR code so the visitor can finish on their phone.
(If you are coming from Branch: this is what Branch calls a Deepview.)
When It Appears
By default, Launchpad appears only where the alternative is nothing: a desktop visitor to a link that has no web destination at any level — the link, its template, or the workspace's web fallback. A link that resolves to a website keeps redirecting there. Nothing changes for a link that already works.
You can widen or narrow that from Social Share Preview → Launchpad in the dashboard:
| Setting | Options | Default |
|---|---|---|
| Desktop | Only when a link has no web destination · Always · Never | Only when a link has no web destination |
| Mobile without the app | Send to the app store · Show the Launchpad page | Send to the app store |
- Always shows the page before every desktop visit, even for links that have a website. The page carries a Continue on the web link to the destination the visitor would otherwise have been sent to — with the link's UTM parameters intact.
- Never restores the plain "This link opens in an app" page for links with no web destination.
- Show the Launchpad page (mobile) replaces the store redirect with the page. It has an Open in app button when the link has a URI scheme, the visitor's own store button, and a link to the web fallback. Links with a Universal Link or App Link are unaffected: the operating system opens the app before the request reaches LinkForty, and that stays exactly as it is.
Per link
A link can override the workspace setting with launchpadMode on the Create Link and Update Link endpoints (and on POST /api/sdk/v1/links): inherit follows the workspace, on shows the page to desktop visitors even when the link has a web destination, off never shows it. On a phone, off opts the link out; on does not force the page onto a workspace set to Send to the app store.
What It Shows
Launchpad uses the same title, description and image as your share card, resolved the same way — the link's own Open Graph fields first, then the template's card, then the workspace's card, then the link's title. The page a person sees and the card a scraper unfurls always agree.
On top of that, from the Launchpad settings:
| Field | Where it appears |
|---|---|
| App name and App icon | The header of the page |
| Accent color | The primary button |
| Page template | Hero puts the text beside the image and works with no image at all; Cover puts the text over the image and falls back to Hero for links that have none |
The preview on the settings page is the real page rendered for one of your links, with your unsaved changes applied. Switch it between desktop and phone to see both.
What It Never Does
- It never navigates on the visitor's behalf. There are no timers and no automatic app-open attempts; Open in app is a button the visitor taps.
- It is never indexed. Every Launchpad page is
noindex, nofollow. - It never sits in front of an installed app. Universal Links and App Links are resolved by the operating system before LinkForty sees the click.
Notes
- Launchpad is available on every plan.
- Changes take effect immediately on save.
- The page is served on your link domain, including a custom domain.