I am interesting in writing an url to NTAG215 cards, so far I have download some apps for Ios tagwriter and NFC tools however once I try to read the card I have to open the app and read it, and my intention is to approach the phone and it will be able to pop up the window that let me open the link.
I have read and search quite a bit online about this but I am confused if this is something that needs to be develop using a sdk or its something the I have sort it out playing with the phone configuration.
any information will be much appreciated.
JL
So iOS does support some background processing of URL's in the correct form.
See https://developer.apple.com/documentation/corenfc/adding_support_for_background_tag_reading
If you look at the NDEF spec https://github.com/haldean/ndef/blob/master/docs/NFCForum-TS-RTD_URI_1.0.pdf and look to only support URI Identifier Code 3 & 4 and possibly not 1 & 2
And from Apple's doc's
Note
Background tag reading doesn’t support custom URL schemes. Use universal links instead.
Definitely not URI Identifier Code 0 (custom URL)
And NXP Tagwriter App seems to default to "custom URL", so try writing the URL using the https:// or http:// from the drop down menu.
Related
I'm not familiar with QR codes, but for an app I'm developing for both Android as well as IOs, I need a QR code that takes the user to the Google play or App store. I'm told that this QR code is already generated by somebody else working on the project, but the app is not yet in the stores, so the destination page does not yet exist. Right now this QR code links to nothing. Is it possible to assign this destination page later on, or do I need to generate a new QR code for this link?
Also, is it possible to have a QR code link either to the play store or app store depending on which device it's scanned with, without taking the user to an extra web page beforehand?
Depending on the tool you are using to generate this QRCode, you might be able to modify it later on and add the final Google Play URL.
If you want to have a single page that redirects depending on the device, you might be interested by onelink
You can setup the landing page with multiple store IDs, then put this link as the callback of your QRCode, and you will be redirected to the right page depending on the device OS / platform.
I hope it will help you, I am using this for my projects and it is working really nice.
By the way, welcome to Stack!
We are developing PWA for our app because it's capable of 99% of our needs , however we do need NFC reading capabilities (not writing) and we would hate to abandon PWA and go Native just for this 1 thing
Our purpose for NFC is for reading the serial only. In fact we dont need fancy NFC functions. We just have a text field where the NFC code should be typed in, kinda like how barcode readers work (keyboard emulation)
Is this possible with PWA today?
The Web NFC API has a draft status at W3C. However, it seems to be the case that Chrome for Android has support for NFC, but only in experimental modus.
This means that currently, if you would release your application today, NFC will not generally be supported. However, the fact that Google has it available in experimental modus, seems to indicate it will be more widely available soon.
You can check the status here
For in-house solutions (or solutions where you have full control over the device) you can do it without NFC api in browsers (at least until it is available).
You will need to install Tasker app (paid, about 3 USD), which can create NFC read trigger, which then can open url like yourapp.com/{nfc_uid}. If YourApp is installed as PWA, you can select to open the url in the app instead of browser. This way it will look like the PWA is reading the NFC tag.
To make it work:
1. Install Tasker
2. Add new -> Event -> Network -> NFC Tag. Leave field blank and confirm (or just press back button)
3. Add new Task to this trigger: System -> Send intent
Action: android.intent.action.VIEW
Data: http://yourapp.com/%nfc_id
Extra: com.android.browser.application_id:yourapp
Target: Activity
4. Save
The reason we are not doing it using Task "Open url" is because we do not want to open new tab each time it is triggered.
If you have everything right and you scan NFC tag, your app should load with the NFC UID in url.
I think that you have any solution, if you don't have solution yet, so I recommender check this web site.
https://www.chromestatus.com/feature/6261030015467520#
https://googlechrome.github.io/samples/web-nfc/
to enable NFC experimental on Chrome type chrome://flags on G Chrome Android explorer
Does anybody know if it will be possible to link apps to URLs in Windows 10?
Like if you click a YouTube link I can choose to open it in an YouTube App rather than linking to the YouTube homepage.
Yes, its possible, yu might want to check this out:
Handle URI activation
i have this url:
If i open it up in the iphone or in the ipad, the uiwebview displays the step-by-step to reach the final place.
I want to display the MAP by default.
Is there any way to do that? I mean, with some kind of adaptation of the url?
I have the same question,
according to Apple URL Scheme Reference - Map Links
it seems that we don't have an option to do that.
besides, there's an article building a WEB APPs, I'll post the link in case it might be helpful
Location in iPhone Web Apps
I need to launch my WP7 application from the phone's browser and pass some arguments. For example, the following url would be a link on an html page. Clicking the link would start my application. iPhone and Android both have these capabilites by the name of 'url schemes'.
appName://my.arguments.here
How can I accomplish this on WP7?
Thanks!
Unfortunately there is currently no support for "url schemes" or custom URL handlers that will allow you to handle these requests from within your application.
It is possible to integrate with the search application, which can provide deep linking into your application. It also appears that YouTube has some kind of way of doing it, as the mobile version of their site will jump to the app for playback of videos.
You should use the protocol activation feature of Windows Store apps - see http://msdn.microsoft.com/en-us/library/windows/apps/hh452686.aspx