Changelog

Links on your custom domain can now open your iOS or Android app on the right screen. No SDK needed. On Pro.

• Add your app's IDs to the domain, and tinbo serves the apple-app-site-association and assetlinks.json files for you.
• People without the app go to the App Store or Google Play. Set the store pages once per domain, and override them per link when you need to.
• After an install, your app can ask which link brought the person in and open that screen (deferred deep linking).

Set it up with the deep links guide, or read how it works and what's hard about it, with a map for teams moving off Firebase Dynamic Links.

• Notes: give a link a private note to find it by in your list. Visitors never see it.
• Every optional section of the link form has its own switch, so you can see at a glance what a link uses.

Every new or changed destination is now checked against Google Web Risk, with a closer look at a new workspace's first links. More in the acceptable use policy.

The step-by-step guide for your DNS provider now shows the provider's pages as links, and the record names and values in a different font, so it's clear what to type where.

Up to 100 links in one go, from Links → ⋯ → Create links in bulk.

• One link per line: url, slug, note. Only the URL is required.
• Rows pasted straight from a spreadsheet or a CSV file work too, header row and all.
• Pick the domain, folder and tags once for the whole batch, then copy the results or download them as CSV.
• Same in the API and MCP: POST /v1/links/bulk and create_links. A batch of 100 counts as one request against your rate limit.

Short notes on what ships, on the day it ships: a few lines each, plus a link to the guide or the post when there is one. What's still to come lives on the roadmap. To follow along, add the RSS feed to your reader.