They are going to do this similarly to how they handled apple pay cash. Then you can add features in different scenarios without needing to necessarily bloating your app.At one level that does sound cool, but from another it's really a bad idea!
A Phone or Tablet GUI is not the same as a Laptop or Desktop. Even now just in iOS we have the constant Ying & Yang between the iPhone and iPad code changes to be more intune with their unique GUI needs.
I think the goal should be the apps core primitives should be common and then the overlay of the given platform should be applied. That way the programmer can be selective on what he wants to turn out... an iOS, MacOS or other and if they think it makes sense to offer it across multiple OS's then compile it for them from the same base.
I think Apple is seeing the larger storage options in iOS devices now coming out as being what allows them to do this. But is that the best use of all this storage?? I think not!
I don't want bloat on my iPhone or iPad with MacOS stuff and even my MacBook Retina is still tight for storage so I surely don't want extra stuff on it either.
Skinny code is still in vogue!! Long live skinny code!!
I hope not.
You don’t know how Apple universal app works.My main worry about universal apps is bloat.
. . . . .
I'll save final judgement until I see the results, but my initial instinct is that this will not bode well for Mac apps.
If Microsoft can make native x86 run on arm, i think Apple can tooSo are they changing all the macOS system library APIs to match those of iOS? That would be nice because it's hard to find help when you're making a native Mac application!
[doublepost=1513793716][/doublepost]
It is an issue because most third-party Windows software is x86-only (much of it still 32-bit even). And the only reason to use Windows is third-party software.
My main worry about universal apps is bloat.
My main worry about universal apps is bloat.