(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.
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: http://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.
You need one anyway for desktop users. A desktop-first website will usually be more accessible and easier to onboard, especially for infrequent users.
Example: To track a package, a certain store emailed me a button whose destination is this monster of a URL:
(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 includeshttps: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.
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: http://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.
Sooooo… were “labia.fart.cum” parts that were changed, or…??
Sure, go to labia.fart.cum. But you’ll only get the full Fart.cum® experience with the Fart Labia™ app!
You’ll be hearing from the lawyers at queef.org