kotlin-platform-app-links-and-deep-links

Guide Android App Link and deep-link design in Kotlin Multiplatform projects.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/cedric-champeix/SpoonFeeder --skill kotlin-platform-app-links-and-deep-links
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kotlin-platform-app-links-and-deep-links
Source: https://github.com/cedric-champeix/SpoonFeeder/tree/main/.claude/skills/kotlin-platform-app-links-and-deep-links
Command: npx skills add https://github.com/cedric-champeix/SpoonFeeder --skill kotlin-platform-app-links-and-deep-links

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides structured guidance for designing and validating Android deep links, web links, and App Links in Kotlin Multiplatform projects, reducing misconfigurations and navigation errors.

Core Features & Use Cases

  • Clear distinction between deep links, web links, and App Links
  • Review manifest intent-filter correctness and scope
  • Plan host verification and assetlinks.json integration
  • Separate Android-specific registration from shared routing for clean architecture
  • Use cases include designing entry points, verifying ownership, and ensuring correct back-stack behavior

Quick Start

Review the Android deep-linking guidelines and apply the recommended manifest, host verification, and assetlinks patterns to your Kotlin Multiplatform project.

Frequently Asked Questions about kotlin-platform-app-links-and-deep-links

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the difference between deep links, web links, and App Links in Android?

Deep links use custom URI schemes, web links use HTTP intents without host verification, and App Links are verified HTTP URLs that open your app exclusively. This distinction ensures correct intent-filter structure and link-type choices in KMP projects.

How do I configure Android App Links and host verification for a Kotlin Multiplatform project?

Configure Android App Links by structuring manifest intent-filters correctly, setting up host verification, and deploying the assetlinks.json file. This ensures proper host ownership validation and seamless routing entry points in KMP workflows.

Does this approach separate Android-specific manifest registration from shared KMP routing?

Yes, it separates Android-specific manifest registration from shared routing to maintain clean architecture. This boundary ensures platform-specific entry points are distinct from the shared KMP navigation logic, reducing misconfigurations.

Why are my Android App Links not working after adding intent-filters in my KMP app?

Android App Links fail when intent-filter scope is incorrect, host verification is incomplete, or assetlinks.json is misconfigured. Validating manifest structure and ensuring proper assetlinks.json deployment resolves these navigation errors.

Can I use standard Android deep linking patterns for KMP entry points and back-stack behavior?

Yes, standard Android deep linking patterns apply to KMP entry points. Designing correct intent-filter structures and managing link-type choices ensures proper back-stack behavior and navigation routing within the shared architecture.

When do I need to deploy an assetlinks.json file for Android App Links?

You need to deploy an assetlinks.json file when implementing verified Android App Links. This configuration proves domain ownership, allowing HTTP web links to automatically open your app without disambiguation dialogs.