Sometimes it’s Apple and Google that are forcing developers. The system is perfectly capable of running the app (you’re not using any new API) but store policies force you to add the restriction anyway.

▲

jmkni a day ago | parent [-]

Yeah we are in this situation right now with an App, we literally can't update it unless we target a more modern version of the SDK, which introduces breaking changes

	▲	touristtam 2 hours ago \| parent \| next [-]
		Does it mean that you potentially have multiple version of the same software released if you are choosing to support devices that have been dropped from the latest SDK?
	▲	ryandrake a day ago \| parent \| prev [-]
		This problem could be mitigated by Apple making older versions of software available. Then you could continue to release updates, and users on older devices could continue to use earlier versions of your app on their devices. Apple actually partially solves this: as a user, if I have EVER downloaded Older Version X of an app, and then go to download it again, they let me. However, if I have never downloaded the old version and go to download it, they just say “this app is not compatible with your device.” and don't give me the chance to get the older, compatible version. I don’t know why they make this distinction. Worse are the third party apps where the old version still actually runs, but the developer deliberately blocks you with a full-screen “go away” dialog (I’m looking at you, FlightAware).