Why adding locations to Google Calendar events is more important than you think


If you’ve ever created an event in Google Calendar, you’ve no doubt noticed—and probably used—the “Add location” box. This is for much more than just informational purposes. Calendar integrates with other Google apps, and that makes location an important detail you shouldn’t leave out.

Know exactly when to leave for events

“Time to leave” notifications

As a directionally-challenged and somewhat forgetful individual, needing to be at a location at a specific time poses two problems. Even when I do remember the event time, I usually underestimate how long it will take to get there. Nothing’s more annoying than being late when you thought you were leaving on time.

That’s why I make a point to add locations to as many calendar events as I possibly can. On Android, Google Maps will automatically send a reminder notification when it’s time to leave for an event in your Google Calendar (or Gmail). If you’re an iPhone user, this is also possible, but it requires manually entering an “Arrive by” or “Depart at” time. I can’t tell you how many times these reminders have saved me from being late.

Go to Settings > Notifications > Getting around > Time to leave.

Stop fumbling around for addresses in your car

We all know that feeling of getting in the car, turning the key, and thinking, “Wait, where am I going?” Even if you happen to have an Android Auto screen, you still have to open Google Maps and manually enter the address or hope it appears in the Recent locations. If you add location details to Google Calendar, you can avoid all of that.

It took me an embarrassingly long time to realize that Google Calendar is available from Android Auto (on Samsung phones, you need to add your Google account to the stock Calendar app). The app is useful because it shows locations from the day’s events, and tapping them immediately starts navigation in Google Maps. Sometimes, Android Auto will even put the location in the suggested locations box. I find this to be super handy.

“When were we at that place?”

The ability to search for event locations

One thing that makes Google Calendar particularly useful is the ability to search. You can find birthdays, dates for upcoming events, dates of past events, and more. Locations added to events also appear in these search results.

This is useful for a couple of reasons. Sometimes, I want to look up exactly when I did something at a specific location. Or I could be planning a yearly event, and I want to remember where it was held last time. In the first example, I can search for the name of the location and find the event details. In the second example, I can search for the event details and find the location. It might be a small thing, but I’ve done it more than I’d like to admit.

2026-07-09_17-28-05


If you use Google, be sure to truly use Google

Many people have legitimate concerns about using Google services, but it’s essentially an all-or-nothing proposition. If you use one Google service, you might as well be using all of them. So, it only makes sense to allow Calendar and Maps to communicate with each other. Integrations like this can genuinely make your life a little less complicated.



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


TL;DR

Meta stripped NameTag facial recognition code from its AI app one day after WIRED exposed it on 50 million phones. Meta says no decision has been made.

Meta removed nearly all traces of an unreleased facial recognition system from its smart glasses companion app on Friday, one day after WIRED reported that the software had been quietly embedded in an app installed on more than 50 million phones. The feature, which Meta internally called NameTag, was designed to convert faces captured by the company’s Ray-Ban smart glasses into unique biometric signatures and compare them against a database stored on the user’s device. WIRED also found that faces the system failed to recognise were cropped, indexed, and stored locally for future processing.

Andy Stone, Meta’s vice president of communications, told WIRED on Monday that the feature is “purely exploratory,” adding that no final decision has been made on what to do with it. That characterisation sits uneasily with the evidence WIRED documented. The version of Meta AI published the day of WIRED’s Thursday report contained several code libraries explicitly named for face recognition, a process for running the NameTag recognition pipeline, and a “Person recognised” alert the app would have shown if someone were identified.

Friday’s release stripped all of it out, along with a folder where the app would have stored the cropped images and biometric signatures of unrecognised faces. Meta did not answer WIRED’s questions about why the code was removed or whether the changes were planned before the story was published. A few fragments remain in the latest version, including an internal debug menu label and a dormant link meant to open a recognised person’s profile, pointing to parts of the system that are no longer there.

The 💜 of EU tech

The latest rumblings from the EU tech scene, a story from our wise ol’ founder Boris, and some questionable AI art. It’s free, every week, in your inbox. Sign up now!

The gap between Meta’s public statements and the code WIRED found is the central tension. Before the Thursday report, Stone dismissed the findings by writing that the company could not answer questions about how the system would work because “the feature does not exist.” Andrew Bosworth, Meta’s chief technology officer, called the reporting “incredibly misleading” and “absolutely dishonest.” Yet the code was functional enough to include three AI models, one to detect faces, another to crop them, and a third to encode them as biometric data, all embedded in the companion app for a product already at the centre of a mounting privacy crisis.

Meta declined to answer ten questions WIRED posed before publishing, including whether it had already created the database of face profiles NameTag uses, how long the app retains photographs and biometric data of unrecognised people, and whether that data would ever be sent back to Meta’s servers. The company also did not respond to questions about whether it was building NameTag for blind or low-vision users, or to criticism from privacy advocates who warned the system could let stalkers and abusers identify strangers in public.

NameTag first surfaced in February, when The New York Times, citing internal Meta documents, reported that the company was developing face recognition for its smart glasses and considering a launch as early as this year. One internal memo reportedly described releasing the feature during a “dynamic political environment” when privacy and civil liberties advocates would be distracted by other concerns. WIRED subsequently found that much of NameTag’s machinery had been built into the Meta AI app as early as January, months before any public acknowledgement, adding another layer to the company’s pattern of shipping first and disclosing later when it comes to its smart glasses.

Kade Crockford, director of the technology for liberty programme at the American Civil Liberties Union of Massachusetts, said the removal does not undo the original decision to ship the code and pointed to it as evidence that consumer privacy needs stronger legal protection than Congress has been willing to provide. The Massachusetts House of Representatives last week unanimously passed a consumer privacy bill that, if enacted as written, would impose strong enforcement provisions including a private right of action allowing aggrieved users to sue. “State lawmakers need to do their job and step up to protect consumer privacy,” Crockford said.

Meta’s sneaky tactics in slipping the face-recognition code into its smart glasses show exactly why data privacy bills need the teeth of strong enforcement,” Crockford added. “Companies like Meta prioritise their bottom line, so lawmakers need to speak in the only language its C-suite understands.” Whether a code removal prompted by investigative reporting constitutes a victory or merely a tactical retreat depends on what Meta does next, and on whether the regulatory pressure building on both sides of the Atlantic produces enforceable consequences before the feature quietly returns under a different name.



Source link