Apple is going to build on its plan on merging iOS and macOS apps this year. The company first announced its plans, codenamed Marzipan internally, at last year’s WWDC developer conference. It even shipped a couple of native iOS apps as part of macOS Mojave to give users a taste of what’s to come.
And at WWDC this year, the company is taking things further.
According to Bloomberg, Apple plans to release a new SDK for developers that will allow them to convert iPad apps to run on the Mac. The new kit will mean that iPad app developers like Netflix will be able to convert their existing iPad app to run on a Mac. The only limitation, however, is that developers will continue to have to release separate versions of their apps on the iOS and Mac App Stores for the time being.
Apple plans to expand the SDK to support iOS apps in 2020, though the company is currently struggling with problems surrounding the fact that iPhone apps are much harder to scale for the bigger screen of the Mac. And if the company really is planning to release a 16-inch MacBook Pro this year, that’s definitely going to be a problem.
Apple’s ultimate goal, however, is to combine all the different platforms and turn it into a single, universal App Store — much like Microsoft’s Universal Windows Platform in Windows 10. Cupertino plans to achieve this by 2021, allowing developers to make apps for iPhone, iPad, and Mac with a single code base, and submit them through a single, combined App Store.
provision l-3
<blockquote><em><a href="#406042">In reply to codymesh:</a></em></blockquote><p>Considering Apple announced this last June and there was no freakout I'm guessing you are probably going to be waiting awhile. </p>
provision l-3
<blockquote><em><a href="#406245">In reply to codymesh:</a></em></blockquote><p>I actually read both and while both and 9to5mac's most recent article was positive about the idea and Gruber was skeptical of the relevance of doing it. We might use the word freakout differently but I wouldn't characterize either as a freakout. </p>
dontbe evil
<blockquote><em><a href="#406043">In reply to nbplopes:</a></em></blockquote><p>yeah apple fans can't wait to play with animoji and AR toys</p>
dontbe evil
<p>but but nobody wants apps on a pc … oh no that's about windows, this is about apple: this is so cool, apple is the best!!!</p>
skane2600
<blockquote><em><a href="#406071">In reply to spacein_vader:</a></em></blockquote><p>You were downvoted most likely because many people make a distinction between "apps" and "programs". </p>
dontbe evil
<blockquote><em><a href="#406263">In reply to locust infested orchard inc:</a></em></blockquote><p>just read comments about windows 10 UWP apps, and most of people clearly make a distintcion with the word "apps", I was mocking them</p>
skane2600
<blockquote><em><a href="#406263">In reply to locust infested orchard inc:</a></em></blockquote><p>I would imagine anyone like that would find Apple's "What's a computer?" campaign to be perfectly logical. </p>
dontbe evil
<blockquote><em><a href="#406075">In reply to locust infested orchard inc:</a></em></blockquote><p>butthurt applefans didn't like your comment, have an upvote from me</p>
skane2600
<blockquote><em><a href="#406294">In reply to irfaanwahid:</a></em></blockquote><p>It was a chicken and the egg problem. MS didn't do all they could have to promote the Windows Phone and thus there was no viable business opportunity for UWP apps and their Windows 8/8.1 predecessors. Not to mention that MS essentially turned up its nose to its legacy developers in favor of chasing a mobile future that was never going to arrive.</p>
skane2600
<blockquote><em><a href="#406075">In reply to locust infested orchard inc:</a></em></blockquote><p>The fate of the Windows Phone had already been determined before Windows 10 came along. One can only speculate how much faster MS could have delivered a touch-oriented OS for smartphones if they hadn't got distracted by coupling it with a desktop version of Windows. </p><p><br></p><p>I'm not an Apple fan but you have to admit there's a big difference between integrating mobile apps with your desktop when the mobile platform has proven itself viable in the market for years vs combing an unproven mobile platform with your desktop OS.</p>
skane2600
<blockquote><em><a href="#406311">In reply to curtisspendlove:</a></em></blockquote><p>Interesting speculation but I'm a skeptic with regard to the final scenario you described. Unless one creates programs with a more limited "multi-platform friendly" feature set, they are not going to be the same on all devices.</p><p><br></p><p>I don't see this as an Apple problem, I see it as an universal problem. In the general case, form-factor issues can't be abstracted away. </p>
skane2600
<blockquote><em><a href="#406329">In reply to curtisspendlove:</a></em></blockquote><p>Of course common libraries have been SOP for many decades, so there's nothing new there. If all it is is multiple binaries combined into a single file, it doesn't seem to provide much improvement in programmer productivity over a more traditional approach. I guess uploading a single file to a store rather than n files would save a few minutes.</p>
provision l-3
<p>Mehedi, you are almost a year late on this. Apple announced last WWDC that they were going to roll this out to iOS developers this year. </p>
dontbe evil
<blockquote><em><a href="#406244">In reply to MikeGalos:</a></em></blockquote><p>and don't forget "it's your fault" (you're holding it wrong) and "it's not a bug, it's a feature"</p>
provision l-3
<blockquote><em><a href="#406244">In reply to MikeGalos:</a></em></blockquote><p>Credit where credit is due, this is far better criticism than that time you made up an Apple product demo and then accused Apple of faking the demo that you made up. This is at least based in reality. </p>
skane2600
<p>As described, it doesn't actually allow iOS apps to run on MacOS, it provides a more convenient method for porting an iOS app to MacOS than what currently exists. </p>