I have worked on several applications where the product managers wanted to make our web app something that could be installed through the app store, because that's how users expect to get apps.
I know people who don't even type search queries or URLs into a browser, they just tell the phone what they want to find and open whatever shows up in a search result.
I've tried pushing back against the native app argument and won once because customers actually reported liking that we had a website instead of an app, and other times because deploying an app through the stores was more work than anyone had time to take on. Otherwise, we would've been deploying through app stores for sure.
Marketing gets plenty of data from google analytics or whatever platform they're using anyway, so neither they nor product managers actually care about the data from native APIs.
I don't know exactly what you are talking about here, but if I wanted to find a restaurant that is local I definitely just type 'Miguels' into the browser and then it searches google for 'Miguels' automatically and it know's my location so the first result is going to be their website and phone number and I can load the website for the menu or just call if I know what my family wants.
However even then, I'd rather have an app for them where I can enter in the items I want to order. I've noticed apps tend to be more responsive. Maybe it's just the coding paradigm that the applications tend to load all of the content already and the actions I take in the app are just changing what is displayed, but on a website they make every 'action' trigger an API call that requires a response before it moves on to the next page? This makes a big difference when my connection isn't great.
I also find it easier to swap between active apps instead of between tabs of a browser. If I want to check on the status of the order or whatnot, it's easier to swap to the app and have that refresh then it is to click the 'tab' button of the browser and find the correct tab the order was placed in.
So you open safari first. I think that’s a step further than what’s being described.
Many people it’s just “hey siri, book a table at Miguel’s.” And then click whatever app, web result, or native OS feature pops up.
It’s a chaotic crapshoot that I have never been able to stomach personally. For others, that’s just called using their phone.
It's also why so many websites try to offer push notifications or, back when it seemed like Apple wouldn't cripple it, the "add to home screen" or whatever CTA was that would set the website as an icon. Anything that gives the user a fast path back to engaging without having to deal with interacting with the browser itself is what PMs and marketing want.
What I found was that none of these food trucks (and even some relatively nice restaurants) had operational web pages. One had a domain but, for some apparent reason, they posted the menu to <some-random-name>.azurewebsites.net. And that page just... Didn't work. The rest got even worse. Most had listings on Google Maps, but the hours and availability did not reflect reality. We went to a coffee food truck that wasn't there, even though the day before they had commented on a review. Then we had others that had a link to an Instagram page of which some claimed to house their "current" hours and location, yet we tried going to two of them and both weren't open.
It's 2026. If you have your business on Google Maps you should be able to update hours and availability quickly. But beyond that it costs almost nothing to host a simple availability page on a representative domain. And even if you don't want to deal with the responsibility of a domain, there are multitudes of other options. Now, I'm guessing that this isn't the norm for most of these vendors, at least I hope. But we weren't there during the worst of the rain, we hit the second low that went through in our timing. So while it was a significant amount of rain and some of the more treacherous switchback roads were closed - I'm talking about food trucks that were off of very accessible main roads & highways. My SO reached out via IG to about a half dozen vendors and only one responded 2 days later.
Clearly tech and simple services like availability and location that is easy to update is not accessible (or known) for these types of businesses. But it definitely does not require an app (nor should it). Having these simple "status" sites would have made the friction the weather caused significantly less than what we experienced. I don't want an app when I'm trying to find out if a restaurant is open. I, personally, don't find apps any more responsive. In many cases a lot of web sites are littered with far too many components that are not required. I've been doing a lot with Datastar and FastAPI recently and some of the tools I've thrown together (that handle hundreds of MB of data in-browser) load instantly and are blazing fast. So much so that I've been asked how I "did that". It's amazing how fast a web app can be when it's not pulling data from 27 different sources and loading who knows what for JS.
> However even then, I'd rather have an app for them where I can enter in the items I want to order.
Really? You want to download a different app for every restaurant you order from?
The UK's Companies House (required for anyone who is a director or has a shareholding of more than 15% etc.) requires a Onegov ID now. They offer a web version with a scan of a photo ID (passport or driving license). I tried it. I thought one of those would work. Apparently the web version needs to ask security questions (reasonable, as the app used NFC to read your passport) but despite the vast amount of information the government has on me (to issue those IDs, to collect taxes, etc) it cannot do that, so i had to either use the app or go in person to a post office in a different town.
Similarly I got an email from Occado saying that if I used the app I could change orders without checking out again. If I do it on the website i have to checkout again. Why?
The flip side is there are (presumably) real people downloading these apps. Maybe it’s a kid interested in a career in the FBI, or the family of someone who works there. Idk. (I thought it would contain a secure tip line or something, but the app seems to be a social-media front end first.)
I am willing to entertain that there is a legitimate reason for an app to exist without conceding that it should be a pile of trash.
TSA used to have an API [0]. But, of course while the deprecation page still lives on the service does not.
Edit: Also looks like TSAWaitTimes.com [1] is an option, I'm sure their API works. o_O
[0] https://www.dhs.gov/archive/mytsa-api-documentation [1] https://www.tsawaittimes.com/
It's mostly static data. Just publish it under a URL that won't change. Then we could actually cache and archive it.
Most browsers do in fact offer that level of granularity, especially for PWA usecases [0].
And from an indicators perspective, having certain capabilities turned off can make it easier to identify and de-anonymize individuals.
[0] - https://pwascore.com/
There's a considerable difference. And doing whatever one can to mitigate the former shouldn't be discouraged by falsely equivocating the latter.
You will of course need a couple additional threat intel feeds because what is provided via the browser itself isn't enough, but third party data vendors along with threat intel vendors are fairly cost effective.
I've seen a couple actual live demos of deanonymization a couple years ago - it's a capability that has existed in the Offensive Security space for a couple years now. And the company I'm alluding to is already live in Japan and Israel.