3 ms·
It's if you want to have backwards compatible syntax supported by later devices. This will naturally happen as you add features and modify old ones. It's even m
by SapphireSun 11y ago
It's if you want to have backwards compatible syntax supported by later devices. This will naturally happen as you add features and modify old ones. It's even more important in hardware devices that might might not be able to be updated later.
EDIT: I think someone is probably down-voting me for a technical reason. Would you please explain it?
- mderazon 11y agoIf Apple wants to break BC they just do it. They control the entire ecosystem and has been known to break stuff pretty frequently and force everyone to keep up
- SapphireSun 11y agoI imagine they break stuff frequently, but not as frequently as they could if they wanted - though someone from Apple would know better than me of course.
- sosborn 11y ago> been known to break stuff pretty frequently Apple is really good about giving developers a heads up before deprecating anything.
- pilsetnieks 11y agoAs I understand it, you don't need to worry about backwards compatibility. You submit these pseudo-XML views along with your app when you publish it but what they do from there on out is up to them - they could "recompile" them to newer versions, they could compile them to some binary representation, whatever. But anyway, it's not your problem. Your responsibility is getting the app to the app store, their problem is getting the app from the app store to the devices, in whatever format they see fit. Despite the technological similarities, this isn't publishing to the web where you have to handle everything by yourself.