Comment by tormeh

Lets just zoom into a single use case. The ability of the user to buy a 3rd Party watch that integrates with their phone:

* Apple doesn't allow 3rd Party watches to send text messages. The Apple Watch is allowed to do so.

* Apple doesn't allow 3rd Party to take actions on notifications. The Apple Watch is allowed to do so.

* If you want to use the internet on your watch, you must: 1) install a 3rd party app, 2) keep that app open. Closing the app closes the connection to the internet. The Apple Watch does not have this restriction.

* 3rd Party watches cannot detect if you are using your phone. This means that they will notify users of notifications even if the user is looking at the notification. The Apple Watch does not have this restriction.

* Apple does not have ‘interprocess communication’(IPC) like Android.

* Apple restricts making 3rd Party App Stores. This makes it difficult to make a community of people making watch faces.

All points come from Pebble's blog [1]. This is just a single type of integration that Apple intentionally makes difficult, there are many others (e.g. 3rd Party Photos App, ...)

[1] https://ericmigi.com/blog/apple-restricts-pebble-from-being-...

On iPhones you can't install software except through the app store

let me list some things I can do on android which I cannot do on iOS:

* Install real mobile firefox, including installing firefox addons I've built for myself. Firefox on iOS is a safari skin

* Install web browser security updates without also updating my entire OS. On Android, firefox is an app. on iOS, safari is a part of the OS that cannot be updated independently

* Install an open source app my friend built without paying $100/year or having to reload it every 7 days

* Build and install an app without owning a macbook or other macOS device, just using linux

* Filter notifications to my garmin smartwatch by-app

* Change the messenger app that handles SMS

* Have a notification center that syncs between linux and my phone (i.e. KDE Connect doesn't work https://invent.kde.org/network/kdeconnect-ios#known-behavior... )

* Have reliably working file-syncing (i.e. syncthing for iOS) because background tasks are something you can do well in android, and barely at all in iOS

* Have access to the source code to debug and fix problems

* Have the ability to flash my own custom kernel / rom (not all android devices, but many)

.... Really, not being able to write and install my own app without paying apple $100, and without owning a macbook is the big dealbreaker, followed by iOS restricting APIs needed to do all sorts of things like proper notification handling, proper NFC, etc etc.

It amazes me that so many people on the "hacker news" forum are okay with their primary computing device being wildly hostile to the hacker spirit, to the desire to tinker around for fun and learn and hack on things.

Like sharing your WLAN. It works great between iPhones, if you know how it works and the preconditions are fulfilled (it's undiscoverable). You can't share with Android devices by showing them a QR code – which I would consider the "usual" way and which is easy to do on Android devices.

Edit:

Here is the procedure I was talking about and all prerequisites for it to work:

https://support.apple.com/en-us/102635

Bluetooth LDAC would be cool.