So Balmer was right?
Best to market (in theory) for Apple, not first to market. Think Zune vs. iPod.
So Balmer was right?
Seems to me that this Major undertaking will mean that OS 10.14 (Lassen?) will come out even more bug ridden that High Sierra.
Unless they go on a hiring binge, they don't have the Mac programming staff to tackle this cleanly.
I'd sooner see a 10.14 which is a !0.13 done right.
That is absolutely possible.
But - what problem is being solved by allowing iOS apps being run on Mac OS? Developers still need to modify the GUI for a usable Mac OS experience.
iOS apps on a desktop application would no little more than dashboard type apps.
Apple putting in an additional ARM chip into its computers sounds like another excuse to hike prices.
Well there you go. Looks like Apple is doing something I was not expecting.
That would be so sweet.
Udemy App to download my courses onto my Macbook? Fingerlicking delicious.
Next: Apple announces they are banning browsers running on Macos, as most websites publishes an dedicated app anyway. No need for general purpose applications like browsers, as there "is an app for that".
Next to go: The filesystem browser. No need for a file system browser, as all data stored on your mac can be reached through an dedicated app. No need for general purpose applications...
rinse and reapet
I wonder whether the 'Macs' that iOS apps will run on may include (or even be limited to) new ARM-based Mac app Store-only Macs.
Offering a Macbook-priced combo Mac/iOS notebook computer with both touchscreen (iOS apps only) and trackpad would be a Grail device for normal everyday computer users and students, would give Apple higher margins (no Intel Tax) and increased revenue (and relevancy) to the Mac App Store. It would make these lower-end Macs more secure and easier to administer for large-scale deployments (businesses, schools)
Becasue "apps" generally are much dumber than a full OS app.
"Apps" live inside a closed platform with very limited input methods and do a specific task. Instead of using a multi-purpose tool to do many tasks, Apple's take on "apps" are that you need one specific app for each task. Instead of using one (1) browser to access http-content, I should download a large number of apps that does the exact same thing, only each of them are made specific for that exact content.
One app for reading New York Times, another app for reading FT.
This unification of the developer framework has strong incentives to quit doing proper tools and just relase stupid apps, even for a multi purpose machine like a desktop mac. That is dumbing down a great platform.
Who wanted this?
So they remove 32-bit mode because it gets rid of bloat. But now apps will be bloated again with platform-specific code "just in case" I happen to use it on something other than a Mac?
I think this is a positive step since the Mac App Store like the Apple TV store leaves a lot to be desired. With the exception of a dozen or so essential programs, it's really only good for updating the OS and 1st party software. OTOH the iOS App Store has great new apps every single week. I don't see them crippling MacOS but no one can deny the platform has been stagnant for a while now. IMO the last truly revolutionary and exciting OS X releases were Leopard and Snow Leopard. They were game changers that made OS X the clearly superior OS and coincided with increasing rates of Mac adoption. Before that I would see some people with MacBooks, but around that time it seemed like everyone had a MacBook.
A lot has happened since then. Many folks no longer have the need for a conventional computer especially if they are no longer in school and if their job has nothing to do with using a computer. For a large chunk of the population their primary computing device is their smartphone followed by a tablet. It handles all of the basic computing needs. The only reason to have a computer is to get real work done, whether programming, video editing, recording audio, engineering, or for most to use an Office suite with a real keyboard and mouse/trackpad.
This has been tried before, and failed miserably. However, Apple is in a good position to succeed in this area.
Windows failed because there were literally no Windows Mobile users and fewer Apps/developers. Tough to get people on board when nobody’s using your mobile OS.
Google is going to fail as well. Running Android Apps in a browser-pretending-to-be-an-OS? What’s the point? The idea of iOS to Mac or Windows Mobile to Windows Desktop is to have Apps that can run on your mobile device or your full-blown desktop OS. Going from Android to Chrome seems like a lateral move - from one limited OS to another.
Apple has a huge advantage because of the developer community for iOS. I highly doubt that this will result in the “dumbing down” of Macs. I think we’ll see useful Apps on iOS end up on the Mac (some might just be complex widgets) along with seeing more complex software make it from the Mac to iOS devices. I don’t expect (or want to) run iOS versions of something like Office on my Mac. But I have lots of utility Apps on iOS that would be nice to have available on my Mac as well.
Moving a limited app from a limited OS to a more powerful OS ... the app is yet still limited.
How is this going to work? There have been many discussions regarding screen size ratios and how apps should look, but how is a iPhone app going to look on a 27" display? A very small window which you can hardly see, or blown-up to cover the whole screen? Interesting to see hoe this is going to work out.
[doublepost=1517408925][/doublepost]
Don't waist your time on comments like these.
easy on developers...
... users could now question "Why do I need an iPad when i can run these same apps on a Mac? "
While multiple reports suggest Apple has decided to place a greater focus on improving the performance and security of iOS and macOS, which will delay some new features until next year, it appears the company still aims to introduce the ability for Macs to run iPhone and iPad apps later this year.
![]()
Mark Gurman and Ina Fried, reporting for Bloomberg News and Axios respectively, both claim the framework for combined apps remains on Apple's software roadmap for 2018, despite some planned iOS 12 features likely being pushed back to 2019, including a new home screen with a redesigned grid of app icons.
Apple's software engineering chief Craig Federighi reportedly revealed the plans during a meeting with employees earlier this month.
Last month, Gurman reported that developers will be able to design a single third-party app that works with both a touchscreen, and a mouse or trackpad, depending on whether it's running on an iPhone, iPad, or Mac. Apple would presumably also streamline its own apps on the desktop and mobile.
The report didn't explain how all of this will work, but Apple could be planning to release a new SDK with new APIs that enable true cross-platform functionality. Right now, Apple's UIKit and AppKit frameworks provide the required infrastructure for iOS and macOS app user interfaces respectively.
It's worth noting that Apple already has a private framework called UXKit, used for the Photos app on Mac. In 2015, Jason Snell said UXKit "sits above the Mac's familiar AppKit frameworks and strongly resembles UIKit on iOS."
Apple tentatively plans to begin rolling out the change in iOS 12 and macOS 10.14, so there will likely be an announcement at WWDC 2018 around June. Following a few months of beta testing, major new versions of iOS and macOS are typically publicly released in September and October respectively.
The project is reportedly codenamed "Marzipan" within Apple. Gurman speculated that universal apps would make it easier for Apple to one day create a single operating system for all of its devices, should it ever go down that avenue. At the very least, it could bring some renewed attention to Mac apps.
Apple would be following in the footsteps of Microsoft's Universal Windows Platform, aimed at helping developers create universal apps that run across Windows 10 and Windows 10 Mobile, the latter of which is being phased out.
Article Link: Apple Still Expected to Allow iPhone and iPad Apps to Run on Macs Later This Year
If you ever used Chromebook, you will know how it will works. Currently Android App runs on Chromebook with small window which emulating your phone screen. You can resize the app if you want.
This is probably how it will be done.
Apple is basically following the footstep of Microsoft and Google.
Best to market (in theory) for Apple, not first to market. Think Zune vs. iPod.
Phil Schiller quote:
"We think of the whole platform,” he says. “If we were to do Multi-Touch on the screen of the notebook, that wouldn’t be enough — then the desktop wouldn’t work that way.” And touch on the desktop, he says, would be a disaster. “Can you imagine a 27-inch iMac where you have to reach over the air to try to touch and do things? That becomes absurd.” He also explains that such a move would mean totally redesigning the menu bar for fingers, in a way that would ruin the experience for those using pointer devices like the touch or mouse. “You can’t optimize for both,” he says. “It’s the lowest common denominator thinking.”
Not an example as iMessage and Airdrop works perfectly for me and others every time I needLiving in a bubble?
Take iMessage. Sometimes I receive them on my iPhone sometimes on my iPad. How is that for working very well?
Photos, take a pic with iPhone wanna retouch it on iPad... gee, where’s that pic? No, it does not work very well. I have to send it via Airdrop or iMessage (really) to my iPad.
Apple under SJ: “it just works”.
Apple under TC: “we try to get it work as soon it comes out of the pipeline”.
“You be amazed what we have in our pipeline” “If we can make it work, that is”
Microsoft already addressed that question by making the Surface Studio desktop with an adjustable touchscreen that angles down very low to the desk, like a drafting table or Wacom tablet. Did you honestly not know about new form factors such as this, or did you purposely choose to ignore it?
And Phil should not be one to criticize "lowest common denominator thinking" when Apple is busy stripping functionality from their current Mac apps in an attempt to make them resemble the iOS versions.
.....Performance compromises are rarely needed (the processor in my iPad Pro is faster than the one in my MacBook).
Guys, when I said "performance", I wasn't thinking about speed or power, but I actually meant "feature" compromises, such as when iTunes11 replaced iTunes10. I'm well aware today's iPhones run on a 64 bit platform with very capable Arm processors, so perhaps my incorrect choice of words led to confusion. Mea Culpa.....If it running off the co-processor that's been talked about the last couple days then there will be no hit in performance on either even if it's not processors are more than powerful enough to run a container with an arm app.
That's working under the assumption of how programs are currently constructed. Major vendors, like Adobe and VMWare, will adapt just like they did with the PowerPC>Intel transition.
I feel like a lot of the problem with the discussion about this is that people are assuming that the apps that will be the result of this transition are the same as what we have now on iOS and that what we have on the Mac will be replaced by dumbed down versions of whatever the developer currently offers. I personally don't see how that would possibly be the case.