Getting Started
Create your account, your organization and your first project, then work through the setup checklist.
Getting from sign up to a working deep link takes about 20 minutes. Most of that is adding your apps and installing the SDK. This page covers the dashboard side.
Create your account
Sign up
Go to app.golander.link/signup. The form is titled Create your account and asks for:
- Name, required ("Tell us your name"), up to 100 characters.
- Email, a valid address ("Enter a valid email address").
- Password, at least 8 characters ("Use at least 8 characters").
Click Create account.
If your account needs email confirmation, you see "Check your inbox to confirm your email, then sign in." Confirm, then sign in at app.golander.link/login.
Name your organization and first project
After signing up you land on onboarding, which greets you with Welcome, <your first name>. Fill in:
- Organization, for example
Acme Inc. This holds your team and billing. - The organization's URL, shown with a
/prefix. It fills itself from the name. - First project, for example
Acme Shop. A project is one app. - The project's URL, shown with a
/<org>/prefix. It also fills itself from the name.
Under the fields, Lander shows where your short links will live:
Your links will live on <project>-<org>.golander.link. Custom domains come later.So the shop project in the acme organization gets shop-acme.golander.link. You can add your own domain later under Domains (see Custom domains).
Click Create workspace.
Land on the Overview
You are taken to app.golander.link/<org>/<project>, the project's Overview, with the setup checklist at the top.
URL rules
Organization and project URLs (slugs) follow the same rule:
- Lowercase letters, numbers and dashes, 2 to 48 characters, starting with a letter or number. Otherwise you see "Lowercase letters, numbers and dashes, 2 to 48 characters".
- Organization URLs are unique across Lander ("This URL is taken, try another").
- Project URLs are unique inside their organization ("A project with this URL already exists").
- These organization URLs are reserved because they would clash with dashboard pages:
login,signup,onboarding,invite,auth,api,settingsand_next("This name is reserved").
Pick slugs you are happy with
The slugs are part of every dashboard URL and of your default link domain, <project>-<org>.golander.link. The dashboard has no screen for renaming them, so choose short, stable names.
The setup checklist
The Overview shows Get Lander working in your app until every step is done ("About 20 minutes end to end. Each step shows who usually does it."). The header shows the same progress as Finish setup with a count like 2/5.
Each step is checked against what actually exists in your project, so it ticks itself off as you go:
| Step | Who | Time | Done when |
|---|---|---|---|
| Add your iOS app | Developer | 3 min | The iOS app has a Team ID and bundle ID |
| Add your Android app | Developer | 3 min | The Android app has a package name and at least one SHA-256 fingerprint |
| Create a publishable key | Developer | 1 min | An active publishable key exists in the current environment |
| Install the Flutter SDK | Developer | 10 min | An app has called Lander.initialize in the current environment |
| Create your first link | Marketer | 1 min | A link exists in the current environment |
The next step to do is highlighted with a Start button. Other open steps have an Open button. Completed steps are struck through.
The key, SDK and link steps are counted per environment. If you finish them in test mode and switch to live, they show as open again until you repeat them with live keys and links. The iOS and Android steps are shared by both environments. See Environments.
Add your apps
Open Platforms (in the Build section of the rail) and fill in the iOS and Android tabs. Lander uses these values to generate and host the apple-app-site-association and assetlinks.json files. Full walkthrough: Platforms.
Create a publishable key
Open Settings, then API keys, and click Create key. Keep the default kind, Publishable, and copy the key from the next screen. It is shown only once. See API keys.
Install the Flutter SDK
The SDK page (Build section) has three short steps with copyable snippets:
- Add the package. Run
flutter pub add lander_flutterto add it from pub.dev. - Initialize before runApp. Call
Lander.initializewith your publishable key. The snippet already has the right prefix (pk_test_orpk_live_) for the environment you are viewing. Secret keys are rejected. - Route incoming links. Listen to
Lander.onDeepLinkand hand each link to your router.
Below the snippets, SDK versions seen lists the platforms and SDK versions that have reported in the current environment, with install counts and when each was last seen. It fills in within seconds of your app's first launch with the SDK. The full guide is in Flutter SDK installation.
Create your first link
Press C anywhere in the dashboard, or click Create link. At minimum, set Opens in your app at to a path your app's router understands, such as /product/123. See Links.
Then open the Debugger, paste the short link and click Check to confirm every piece is in place (see Platforms).
Add more projects and organizations
Open the workspace switcher (the tile below the Lander mark in the rail):
- New project adds a project to the current organization. Only owners and admins see it. The form is titled New project in
<org>and ends with Create project. Each project gets its own<project>-<org>.golander.linkdomain. - New organization creates a separate organization with its own first project, using the same form as onboarding.
Use one project per app. Keep your test and live data in the same project: the Test / Live switch separates them for you.
Signing in and out
Sign in at app.golander.link/login (Welcome back, then Sign in). A wrong email or password shows "Wrong email or password." If you followed a dashboard link while signed out, you go back to that page after signing in.
To sign out, open the account menu (your initials, top right) and choose Sign out.
If someone invited you to their organization, use the link in the invitation email. It works whether or not you already have an account. See Team.