android - Proximity Marketing API -
currently i'm using aws-s3 create url's documents & shorten url's suit eddystone format.
i'm using kontakt beacons & use ui edit beacons shortened
url's. works fine, displayed link (as seen using physical
web app) long & there no link description.
i'm hoping above & more using proximity marketing api,
trouble i'm api newbie & looking guidance. i've created project & browser key & have beacon, not sure to
next (sorry).
i'm guessing i'll have input beacon details
somewhere required url & link description.
is there idiots guide doing or can advise?
the way physical web app , chrome's physical web support work is:
- the app discovers eddystone-urls nearby.
- the app sends url physical web service.
- the physical web service fetches web page url (following redirects, e.g., introduced link shorteners).
- the physical web service extracts title, description, icon, , linked data web page.
- the physical web service returns extracted data app.
- the app uses metadata show url sees fit.
in other words, way control how physical web url displayed in physical web app or chrome ios/android manipulate page's meta tags. if you're linking directly non-html files, naturally can't that.
the best workaround can think of link html page javascript redirect (so it's not followed service) actual document. can manipulate content of html page it's shown physical-web–enabled apps you'd shown. , when user taps on link, it'll open page, redirect user document, initiating download.
Comments
Post a Comment