Website to app & app features
Make Your Website Links Open Your App, Not the Browser
Verified Android App Links and iOS Universal Links — up to 10 routes, tested on a real phone before handover.
Delivered in 3-4 working days
Fixed price · one-time · no hidden charges
or
Ask on WhatsApp before you buyA real person replies — usually within minutes during the day (IST).
How it works
- Pay ₹5,999Secure Razorpay checkout. Share the app and the domain before payment.
- Routes agreedA short WhatsApp exchange fixes the link-to-screen map and collects code, domain and signing access.
- Built, verified, handed overFiles hosted, entitlements set, verification confirmed and both platforms tested on real devices in 3-4 working days.
The short answer
ZoopCoder sets up verified Android App Links and iOS Universal Links for an existing app at a fixed ₹5,999, tested and handed over in 3-4 working days. Up to 10 link routes are mapped, so a tap on https://yourdomain.com/product/123 in WhatsApp or Chrome opens that exact screen inside the app instead of the mobile website. What silently breaks this for most teams is not the app code: Android only verifies an App Link if it can fetch /.well-known/assetlinks.json over HTTPS with no redirect, and iOS only accepts a Universal Link if /.well-known/apple-app-site-association is served as application/json with no .json extension — one stray redirect or wrong content type and every link keeps opening the browser, with no error shown anywhere.
What you get
- Android App Links: intent filters with autoVerify, plus the SHA-256 signing fingerprint of every build variant
- assetlinks.json generated and hosted at /.well-known/ on your domain, served over HTTPS without a redirect
- iOS Universal Links: Associated Domains entitlement, applinks entry and the provisioning profile updated
- apple-app-site-association generated and served as application/json with no file extension
- Up to 10 link routes mapped to in-app screens using path patterns, for example /product/*, /order/* and /offer/*
- Fallback behaviour: a link tapped on a phone without the app installed lands on the matching web page, not the home page
- Verification confirmed with adb, Android's App Links verification state and a fresh fetch of Apple's CDN-cached AASA file
- Tested on a real Android phone and a real iPhone, opened from WhatsApp, Chrome, Safari and Gmail
- A handover note listing every route and its screen, so new routes can be added later without re-reading the app
| Price | ₹5,999 (fixed) |
|---|---|
| Deliverable | Verified App Links (Android) + Universal Links (iOS) |
| Timeline | 3-4 working days |
| Routes included | Up to 10 |
| Platforms | Android and iOS; Flutter and React Native supported |
| Files hosted | assetlinks.json and apple-app-site-association |
| Tested from | WhatsApp, Chrome, Safari and Gmail on real devices |
| Support | 15 days after handover |
What we need from you
- The app source code, or a repository invite (Android, iOS, Flutter or React Native)
- Access to your domain's hosting or DNS, so the two verification files can be placed and served correctly
- Your keystore SHA-256 fingerprints, or Play App Signing access so we can read them
- Apple Developer account access for the Associated Domains entitlement, if the app is on iOS
- The list of links you want opened in the app, and which screen each one should land on
Not included
- Building the in-app screens the links point at — they have to exist already
- Publishing the updated build to Google Play or the App Store (app update release is ₹999)
- Firebase Dynamic Links migration, or a third-party deep-link SDK such as Branch or AppsFlyer and its subscription
- More than 10 routes — quoted per additional batch of 10
- Notification tap routing, which is part of Push Notifications Setup (₹2,499)
About this service
A deep link is what turns a shared URL into an app session. Without it, every link you put in a WhatsApp broadcast, an SMS campaign, an email or an invoice sends the customer to your mobile website — the app they already installed sits unopened, and the journey restarts from a logged-out browser. With App Links and Universal Links set up, the same URL opens the app on the exact screen, and still works normally on desktop and on phones without the app. The app code is the easy half. The half that fails is the two verification files on your domain: Android fetches assetlinks.json and refuses to verify if it is behind a redirect, if the SHA-256 fingerprint belongs to a debug key rather than the Play-signed key, or if a WAF blocks Google's fetcher. iOS caches apple-app-site-association through Apple's CDN, so a file fixed today can keep failing for a day unless it is served correctly the first time. We set both up, confirm verification instead of assuming it, and test from the apps people actually share links in. This is worth buying if you already have an app and links you send out. It is not worth buying if you have no app yet, or if your only goal is a notification that opens a screen — that is already part of push setup and costs less.
Questions before you buy
What is the difference between a deep link, an App Link and a Universal Link?
A plain deep link uses a custom scheme like myapp:// and shows a browser prompt or fails silently if the app is missing. An Android App Link and an iOS Universal Link use your normal https URL, are verified against your domain, and open the app with no prompt — falling back to the website when the app is not installed. This service sets up the verified https kind on both platforms.
Will the links still work for people who do not have the app?
Yes. That is the point of using your real https URLs. Someone without the app opens the same page in their browser as before, so you can put one link in a campaign for everyone.
My app links already open the browser instead of the app. Can you fix that?
Yes, that is the same job. It is almost always the verification file, the signing fingerprint or a redirect on the .well-known path. We diagnose which one, fix it, and show you the verification state afterwards rather than asking you to trust it.
Do you need my source code?
Yes. Intent filters, the Associated Domains entitlement and the route handling are code changes, so we need the project or a repository invite. We cannot do this from a built APK.
Does this work with Flutter and React Native?
Yes. Both have supported routing packages and both still need the same two verification files and the same native configuration, which is where the work actually is.
What happens if I add new URL patterns later?
Most new patterns are covered if they sit under a wildcard route we already set up. A genuinely new path shape needs a small code change and a rebuild; the handover note lists every route so your own developer can do it without us.
Often ordered with this
© 2026 ZoopCoder