Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
This will mean that all apps will eventually be on the App Store so they can be sold on all devices at once. This also means Apple gets a cut of all apps sold on all stores.
 
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!!
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.
 
If the goal is to be single/neat one-app only across all, then this could be good..

I can't imagine it will be good for developers who would need to keep track of which code is for what..

staying as separately apps now makes things more sense where u clearly know which platform your designing for.

Starting to mix up the code in one app, and u start to have problem. Particularity Mac and iOS.

Universal is good for the consumer though

I hope not.


lol.. Just what we need... Apple forcing customers to get the latest gear just do run these universal apps on a specific ARM chip.

(It would be an excuse to upgrade)
 
Last edited:
In order to do that, MacOS that is frozen in 1990 in terms of development, has to evolve. I develop for iOS, tvOS and MacOS and without doubt the later is the most difficult because UI APIs are very poor and crappy compared to iOS'.

Also, this is not viable in terms of quality and in terms of Apple Review rules for MacOS.

Apple has barely forbidden any courses on MacOS. This is why the courses you see on the app store are old. So, if you create a cross-platform course for all devices the course will not be approved for MacOS and for that reason, will be rejected for iOS and tvOS also.

Also, this is a less common denominator.

This is very risky for developers.
 
  • Like
Reactions: springsup
This sounds like a Trojan Horse move on the part of Apple since iPhone can now match processing power of computers.

Arm based portables and desktops here we come.
 
As an iOS Developer, just now finishing up v1.0 of my First-Ever Mac app, "I'll believe it, when I see it".

The ONLY way this makes sense to me is if all future Macs, & probably starting with the Next-Gen Mac Mini, include the ARM co-processor that was hinted-at / leaked 9+ months ago.

For it to become a success, Apple needs to offer a viable / attractive solution to Developers FIRST, which will very-likely require the purchase of a new Mac ... so, if it's NOT the Next-Gen Mac Mini, it will very-likely take years to get off the ground, even if Apple's Software Engineering Dept did their job well.

To Tim / Phil, the coincidence is stunning !
 
With this kind of talk, I just wonder if (or more likely when) Apple will bring a fully functional Xcode to iOS? They started with Swift Playgrounds. Now, it's just a matter being able to create a full app in Xcode, and get the appropriate audio & visual elements from other apps.
 
I just hope it’s not something that’s a messy as the 10.6 transition with Rosetta. I remember working at AppleCare as senior advisor and having to take escalations over that.
 
This would make more sense if Macs had touchscreens since iOS apps are made for touch input.

It might be more useful to go the other way and let iOS run Mac apps.
 
So 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.
If Microsoft can make native x86 run on arm, i think Apple can too
 
Interesting news. I'm curious how this will work for developers and how this will work with the Mac App Store. Hopefully, iOS apps can reuse most code and logic with minimal changes and use Mac-specific storyboards as needed and that the Mac App Store will seamlessly show iOS apps that support macOS. Technically, Macs can already run iOS apps as developers use the iOS Simulator to test apps on their machines already. This is on Intel-based Macs--no ARM required, but my guess is that with the direction Apple is going with the introduction of an ARM coprocessor for the Touch Bar that Apple may still require a newer Mac, ostensibly for perfect compatibility with the iPhone app counterpart (and certainly not to drive new Mac sales ;)).
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.