[null,null,["最后更新时间 (UTC):2025-07-27。"],[],[],null,["# Provide multiple entry points into an instant experience\n\n**Warning:** Google Play Instant will no longer be available. Starting December 2025,\nInstant Apps cannot be published through Google Play, and all\n[Google Play services Instant APIs](https://developers.google.com/android/reference/com/google/android/gms/instantapps/package-summary)\nwill no longer work. Users will no longer be served Instant Apps by Play using any\nmechanism.\n\nWe're making this change based on developer feedback and our continuous investments\nto improve the ecosystem since the introduction of Google Play Instant.\n\nTo continue optimizing for user growth, we encourage developers to refer users to\ntheir regular app or game, using [deeplinks](https://support.google.com/googleplay/android-developer/answer/12463044)\nto redirect them to specific journeys or features when relevant.\n\nEach instant experience has at least one *entry point* , which is a single\nactivity within your app or game. If you want your app or game to have multiple\nentry points, each starting activity needs to be *addressable*; that is, it\nneeds to correspond to a unique URL.\n| **Note:** You cannot associate fragments with URLs. Additionally, you cannot launch these fragments independently of an activity.\n\nIf the URLs for the entry points in an instant app or game share a domain, each\nentry point needs to correspond to a different path within that domain. For\nexample, say you're creating a navigation app that should have three separate\nentry points: find current location, search for nearby restaurants, and share\nlocation. Each of these features corresponds to resources within a web domain,\n\"example.com\". To provide a unique URL for each entry point, specify different\npaths within the domain, as shown in the following table.\n| **Caution:** To help the system launch the correct activity for each entry point, make sure that your paths don't share a common prefix. For example, if you provided entry points containing the URLs \"http://example.com/check\" and \"http://example.com/checkout\", the system's behavior might be undefined.\n\n| Feature | URL |\n|--------------------|--------------------------------|\n| Location finder | http://example.com/finder |\n| Nearby restaurants | http://example.com/restaurants |\n| Share location | http://example.com/share |\n\nDeclare URL path prefixes\n-------------------------\n\nIt's possible for the URL of one entry point to share a prefix with the URLs of\nother entry points into the same app or game. In this case, specify the\nfull path for one entry point and the path prefix for the other entry points, as\nshown in the following code snippet:\n\nAndroidManifest.xml \n\n```xml\n\u003cmanifest\u003e\n \u003cactivity android:name=\".CatalogActivity\" \u003e\n \u003cintent-filter\u003e\n \u003c!-- List of items in the catalog. --\u003e\n \u003cdata android:path=\"/items\" /\u003e\n \u003c/intent-filter\u003e\n \u003c/activity\u003e\n \u003cactivity android:name=\".ItemActivity\" \u003e\n \u003cintent-filter\u003e\n \u003c!-- Information about a specific item in the catalog. --\u003e\n \u003cdata android:pathPrefix=\"/items/\" /\u003e\n \u003c/intent-filter\u003e\n\u003c/manifest\u003e\n```\n| **Note:** To match a `pathPrefix` filter, URLs must contain the path prefix in addition to at least one character following the prefix. Therefore, by following the logic in the preceding code snippet, the URL \"/items/\" would bring users to `CatalogActivity`."]]