I can see how I insinuated that taco bell is Mexican food, but I don’t actually think taco bell is Mexican food. Far from it. But it’s been memed for like 15+ years that taco bell gives you life-altering shits.
I seriously remember seeing this in high school as early as '07, but I’m sure it was probably going around before then.
I live in the OKC metro and if you’re looking for real Mexican food here, you’re pretty spoiled for choice. I won’t suggest we have the drop on Mexican food, but you can find some really great places here without having to look hard. Taco Bell is great because the food actually tastes pretty good and there are like four within a five minute drive of my house.
Not OP, but for me: Anti-consumer, anti-right-to-repair. You have to have it repaired at an authorized service center, which charges tons; and the computer will literally lock out mechanics from non-authorized service centers (including the owner). They’re even working on subscription models for hardware you already own.
Right, it makes sense to me now. The double “as” was definitely confusing, but “identified” instead of “named” immediately made the sentence clear. Thanks.
I was actually refering to the headline in the picture but yeah this is an interesting piece of information too, I know the post’s title was sarcastic but didn’t know it was such a thoughtful joke haha
Building a great mobile website is much harder than building a great mobile app, so I understand when they just don’t build a great website to begin with, but taking away an existing website, yeah, that sucks.
I have doubts. Great website developers often make a half-assed app by wrapping the website in a crippled browser. The T-Mobile app is not even subtle about this, there was a URL bar in the version I last used.
You’re talking about Cordova. Cordova can actually be pretty good, if it’s made well (for example, the Voyager Lemmy app is a Cordova app), but no, I make apps with native UIs.
(Numbers and some strings were changed but the gist and 604-character length remains.)
The main function of such a long URL is to redirect desktop users to https://order.fart.cum/cz/cs/purchases/4206913372/ to see the tracking info while mobile users get directed to the app store to get an app (or view the link in the app if they have it). These are (probably) Google Firebase links and they’re absolutely terrible. While they make life slightly easier for existing app users (saves one click but only if they go through the email), this implementation makes it way harder for others to reach the content. Either you get the app, log in there and part with fucking 300 MB of storage, or if you have no mainstream App Store, storage or time, you are forced to do a workaround: Desktop Mode (that may or may not work), rewriting the URL (difficult because it’s so long and includes https: several times, may require hex-decoding), or finding a computer. All this just to check one order from a store you’ll forget about next week.
I have demonstrated that instead of just getting sent the desktop-friendly URL (and perhaps seeing a floating “Open in app” button at the destination), most users are put through extra nuisance that took effort to implement. Sure, some customers are frequent enough to use the app while most are happy with a website but once the business invests in the app, they will absolutely make sure everyone is pushed there despite it being less convenient for both parties.
Most apps would do fine without a website. Most everyone has a phone, but a fair number of people don’t have a desktop or laptop. And pretty much everyone who has a desktop or laptop also has a phone.
A number of currently popular apps don’t have a website, let alone a mobile friendly website.
You are not 100% alone. I technically have a smartphone but use it as a mini (5") tablet. My SIM is in a feature phone because greedy T-Mobile (Telekom in Deutschland) will not give me more than 1 MB/day for a decent price.
A webapp sometimes works fine for phone users. There are things that websites can’t do on mobile. For example, on iOS, only the latest OS version has support for push notifications from PWAs, and even then, they can’t make noise or vibrations. They are always delivered silently. PWAs are also always rendered with WebKit on iOS. WebKit doesn’t support a number of features.
Yes, a mobile app doesn’t help desktop users, but there are waaaaaaaay more mobile users than desktop users.
Only if you absolutely need some crucial bit of information the moment it arrives, in which case, email isn’t for you, since messages can take up to 3 days to arrive.
I think this point needs to be stressed more. It is dead simple to write a website that works well on mobile phones. In fact, the first ever website, without CSS, without any JS, without fancy HTML5 features, is mobile friendly: info.cern.ch/hypertext/WWW/TheProject.html
It’s only when you start adding useless bells and whistles like floating shit in from left and right, tons of animations, side-by-side displays, overlays and whatnot that you need to start being competent to make it work on mobile.
You are correct. I once tried to develop a multi-platform web app and getting the touch events right was a pain. But a somewhat basic ESP32 setup website worked on mobile without extra effort.
memes
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.