Of course, when you have multiple full newsrooms, you care about location capabilities. I get a customized California feed (California Today) when I go to it.
Of course, when you have multiple full newsrooms, you care about location capabilities. I get a customized California feed (California Today) when I go to it.
"California Today" needing a location capability - I'm not sure if you're entirely serious. Why would it need to access your current location - people read local news for where they live, not where they happen to be. And whether you're in California or not is not something that changes frequently. Nor is California Today a travel guide - it has no relevance for people who happen to be in California. Do you actually know if it's based on your real time location? I doubt it. And even if it was, it doesn't have to be.
Also looking at this - https://www.nytimes.com/column/california-today - it consists of an article every other day or so? This is why they need the location data? And it doesn't look like it's a customized feed at all - seems like everyone gets the exact same feed. What data do they need to put this together? And it looks like they have a signup sheet - https://www.nytimes.com/newsletters/signup/CA - are you sure they don't automatically sign you up based on your permanent address? I mean, consider the level of location access (frequency and granularity) needed to show New York news vs California news and compare that against, say, turn-by-turn navigation.
Also I just downloaded the app and it has "Australia" as a top-level section by default (I'm in the US). Are you sure user location is used meaningfully for anything in the app?