New Year's Eve Ride-Home Tag: Tap by the Door to Call a Ride
Put an NFC tag by the party door that holds a ride-app link. Guests tap, the app opens with pickup filled in, and nobody types an address at 1 a.m.
Put the ride on the wall: one tap instead of typing an address
An NFC tag ride home on New Year's Eve is simple: write a ride-app link to a tag, stick it by the door, and let guests tap it with their own phone. The app opens with the request ready, so nobody has to type an address at 1 a.m. while the party is still loud.
The tag doesn't call a car by itself. It holds a link, and the link opens the ride app on the guest's phone, with their account and their payment method. This guide covers what the link looks like, how to write it, where to put the tag, and the limits you should plan around.
What the tag holds: a ride-app link, not an app
A tag like an NTAG213 stores a short NDEF message. For this project that message is a single URL record, nothing more. When a phone reads it, the operating system hands the link to whichever app handles it.
On Android, the tag dispatch system parses the URI out of the NDEF record and wraps it in an intent. Android's NFC documentation recommends the RTD_URI record type for URIs because it is more efficient than an absolute URI record, and any app set up to handle that link can respond. If more than one app can handle it, Android shows an activity chooser. Newer Android versions are changing how web links from tags behave: Android 16 fires a view intent for http and https links, and the Android 17 documentation describes an "open link" notification that needs a tap first. Expect one extra tap on some phones.
On iPhone, background tag reading works with NDEF tags that carry a URL record. Apple's developer material describes the feature as read-only and NDEF based, and developer forum answers add that only the first URL record in the message is processed. That is the reason to keep the tag to one record: put anything else, like a note or a second link, on a separate tag.
Why a link works well for guests
Everything personal stays on the guest's phone: their account, their saved card, their location. The tag stores nothing about them, and reading it needs no account on your side. That fits the way NFCore works too: no tracking, no account, nothing uploaded.
Ride link formats and pickup from the current location
Uber publishes its deep link formats for developers. There are two forms.
- A universal link:
https://m.uber.com/looking - A standard link:
uber://riderequest
Uber's docs recommend universal links when you link from something that is not a native app, and a tag counts. The documented parameters include pickup and dropoff locations, a product_id for the ride type, and a client_id that identifies the requesting application. The examples in the docs all include a client ID, but the docs do not say whether it is required, so test your link rather than assuming.
Pickup from the guest's location
The most useful detail for a party tag: you can set pickup to the rider's current location. Uber's docs say that setting pickup to my_location means you do not need to provide latitude and longitude. For a tag by your door, that is usually what you want. Every guest taps, the app starts from wherever their phone says they are, and the same tag works for all of them.
A fixed pickup address is also possible, using latitude, longitude, a nickname and a formatted address. A fixed spot makes sense if your building is hard to find on a map, say a rear entrance on a side street. Note that the docs say product_id needs a pickup location and does not work with the user's current location, so if you want to preselect a ride type, set a fixed pickup.
The destination
A destination only shows in the app if you give it a nickname or a formatted address. For a ride home you do not know where each guest lives, so leave the destination out and let people enter their own. Uber also notes that on Android, with standard links, destination details may not appear until the rider taps "Set Pickup Location".
Other ride apps
Lyft documents its own universal link, with pickup and destination coordinates and a partner ID. Taxi companies and regional ride apps have their own formats. Whatever you pick, read that app's developer page, write the link, and test it on both an iPhone and an Android phone before the party. If your town has a local taxi app, a tag for it is a good second tag next to the first.
Writing the tag in NFCore
Writing it takes about a minute.
- Build and test the link in a browser or message first, so you know what it does.
- Open NFCore and start a new write. Choose a URL record and paste the link.
- Hold the phone to the tag until the app confirms the write.
- Read the tag back in NFCore and check that the stored link matches what you pasted, with exactly one record.
- Tap it with a second phone, ideally one of the other platform, to see what a guest would see.
A short link fits easily on an NTAG213, so there's no need for a bigger tag. If you want several tags, for the kitchen door and the garage, there is a guide on writing several tags with the same link. iPhone can write NDEF tags from the app, and Apple's tag-writing support is what makes tags written on an iPhone readable by background tag reading on another iPhone.
You can get NFCore for iPhone on the App Store or for Android on Google Play.
Setting it up by the door
Put the tag where people are already reaching for their coats, at about phone height, near the door they will actually leave through. A small card helps: "Tap your phone here for a ride home". Plain words beat clever ones at that hour.
Test with a real phone. Uber's docs say universal links do not work in the iOS simulator and that pasting them into Safari's address bar does not work either, so the tag test on a real device is the only one that counts. Do it days early. Not at 9 p.m. on the 31st.
If you are already planning the evening around tags, the same door area suits a party playlist tag near the speaker and a midnight countdown tag for the countdown.
Limits to plan around
- No price or time estimate. Uber's docs state that deep links cannot fetch price or time estimates. The app shows the fare after the tap, so surge pricing late on New Year's Eve is a surprise the tag cannot warn about.
- Guests need the app and an account. If the app is missing, Uber's universal link sends iOS and Android users to the app store, but they still have to sign up and add payment. So the tag helps people who already ride.
- Screen and platform differences. iPhones read background tags with the screen on. Android phones may show a chooser or an "open link" prompt depending on version.
- One action per link. Uber's docs say a link carries one action. You cannot also apply a promo in the same tap.
- A tag is a convenience, not a safety system. It does not check whether the driver is on the way, and it does not replace a plan. Agree on a designated driver or a backup ride, and make sure guests who are unwell get help in person, not through a tag.
Bottom line
A ride-home tag is a small, cheap thing to set up: one URL record, written once, tested on two phones. Set pickup to the rider's current location, leave the destination blank, put the tag at phone height by the door, and mention it as people arrive. Write and test it a few days before December 31, and keep a backup ride plan anyway.
Frequently Asked Questions
Does the tag work if a guest doesn't have Uber installed?
Uber's docs say its universal link sends iOS and Android users to the app store when the app is missing. The guest still needs an account and a payment method, so the tag is really for people who already use the app.
Can the tag show the price of the ride?
No. Uber's deep link docs say links cannot fetch price or time estimates. The app shows the fare after the tap.
Do I need an NFC tag per guest?
No. One tag by the door serves everyone. Each guest's phone opens the link in their own app, and with pickup set to the current location it starts from where they are.
Will iPhones read it with the screen locked?
iPhone background tag reading works on NDEF tags that carry a URL record, and only the first URL record is processed. Keep the link as the only record on the tag, and have guests wake the screen first.