5 ms·
At the time, they really wanted to pivot from a computer company to a device company after the success they found with iPod. Remember at first they didn't even
by toddmorey 4y ago
At the time, they really wanted to pivot from a computer company to a device company after the success they found with iPod. Remember at first they didn't even want to allow 3rd-party apps: that's how device-oriented they were thinking.
The computer landscape in 2007 punted the problem of viruses and inability back on the user. I think Apple's goals when they finally did an app store were to (1) ensure iOs-specific native software (vs crappy ports), (2) prevent viruses and malware, and (3) keep the phone as stable as possible.
I think you could argue that there were other ways to approach those goals, but I think it's harder to argue that preventing side-loading was entirely pointless.
- wlesieutre 4y ago> they didn't even want to allow 3rd-party apps They had a "sweet solution" for 3rd-party apps! *drumroll* webpages!
- emodendroket 4y agoArguably could have saved the world a lot of man hours if that vision had prevailed.
- illiarian 4y agoExcept all the man-hours that would be spent on trying basic things like animations in lists work.
- emodendroket 4y agoWell you’d just use some library that solves that problem instead of every app having to do it twice.
- illiarian 4y agoThere are no libraries that solve that in a generic easy-usable way. Because animations shift layout
- DaiPlusPlus 4y agoCSS has lots of non-layout-shifting animation techniques - obviously there’s stuff like only changing colours, images, backgrounds, and effects like box-shadow, but things like animating the transform: property are also “layout safe” and very high performance because they’re applied after layout: https://web.dev/animations-guide/ https://web.dev/animations-guide/
- raydev 4y agoThere would be no web-based option in 2007, especially on a mobile device, that could guarantee 60fps out of the box like Apple's APIs did.
- sbuk 4y agoExcept developers wanted an API and native apps - careful what you wish for! All the argument over progressive web apps could have been avoided, along with Apple being on board.