zlacker

>>janand+(OP)
Haha, excellent timing:

I opened HN just now because:

1. I got tired of waiting 2h for my app to get notarized because

2. I can't sell it on the AppStore in the EU... because

3. the AppStore Connect page gets stuck at their DSA compliance form (it's been 10 days).

And, to add insult to injury, the whole thing could be a PWA, without any compromises in the UX whatsoever.

I misread the title, but I still posted this comment as an example of confirmation bias* in the orange book for posteriority. Time to step away from the computer!

* (sunk cost fallacy)

>>rpastu+79
> the whole thing could be a PWA

Apple neutered the web as best they could to force you to use their rails.

I'm still angry they killed flash. There has never been a better platform for non-technical folks, kids especially, to make animation, games, and mini apps, and deploy them as single binary blobs.

A single swf file could be kept and run anywhere. For the younger generation: imagine right clicking to download a YouTube video or a video game you'd see on itch.io. And you could send those to friends.

You could even embed online multiplayer and chatrooms into the apps. It all just worked. What we have now is a soup of complexity that can't even match the feature set.

>>echelo+q9
You say the security and battery issues "were solvable", so why didn't Macromedia or Adobe solve them? Adobe bought Macromedia in 2005, the era of Palms, Blackberries, Nokia/Symbian, Windows Phone, Microsoft Tablet PC; mobile devices were not a new surprise by 2005. Adobe did get Flash onto Palm mobile devices and TVs and early Android smartphones, and the experience was poor[1][2] - not just from those two issues; Flash sites weren't designed for mobile or touch or small screens. Customers had a choice of Flash-mobile devices, and preferred iPhones.

> "Ryan Lawler of TechCrunch wrote in 2012 "Jobs was right", adding Android users had poor experiences with watching Flash content and interactive Flash experiences were "often wonky or didn't perform well, even on high-powered phones".[9] Mike Isaac of Wired wrote in 2011 that "In [our] testing of multiple Flash-compatible devices, choppiness and browser crashes were common", and a former Adobe employee stated "Flash is a resource hog [...] It's a battery drain, and it's unreliable on mobile web browsers".[10] Kyle Wagner of Gizmodo wrote in 2011 that "Adobe was never really able to smooth over performance, battery, and security issues".[11]" - https://en.wikipedia.org/wiki/Thoughts_on_Flash

[1] https://www.palminfocenter.com/news/9692/palm-joins-adobe-fl...

[2] https://old.reddit.com/r/Palm/comments/ere0c/how_does_flash_...