I just don’t see how an iPad Pro could ever really work as a computer replacement for true professional workflows. I’m talking about multitasking between final cut, building a website, creating assets in photoshop, taking screenshots, downloading things from an email...these are daily tasks for me. An iPad would struggle to do one of these at a time let alone all of them at once. iOS is just too limited to ever make it a real “pro” machine. For limited things like a photography workflow or photoshop workflow, maybe, if that’s all you do. So I think it’s time to give up on the idea of an iPad as a true pro machine. It will never replace your laptop and Apple doesn’t want it to. It’s a shame though because the hardware is certainly capable enough. It would require Apple basically throwing out iOS for iPad and designing a whole new way of interacting just for iPad. iOS is great for iPhones but not great for professional applications. It would be cool, but I doubt Apple will do it.
Building iPad Pro features in Swift
11–20 of 73 posts
Re: Building iPad Pro features in Swift
#12Earlier quoted context omitted.
I think given the specifications of these devices, the pricing, while definitely high, is not completely unreasonable for what the hardware can do - these iPads do things no currently shipping Mac notebook can - 120hz refresh, 240hz touch/pen tracking, FaceID, performance in similar ballpark to a $3k MacBook Pro while passively cooled (!) etc etc. It’s just such a shame iOS isn’t quite ready yet to provide the kind o…
I'd be surprised if Apple ever does more than the current two-window model. A multi-user feature would certainly be nice though. I think iOS is mostly fine. I don't think it's supposed to be a macOS replacement. There are some things a Mac is better for and other things an iPad is better for. Apple wants you to have both.
You can actually kind of fit three windows on an iPad: two in Split View and another one on top in Slide Over. Even if you can’t interact with the background windows when Slide Over is active, they continue to refresh their contents.
Re: Building iPad Pro features in Swift
#13I just don’t see how an iPad Pro could ever really work as a computer replacement for true professional workflows. I’m talking about multitasking between final cut, building a website, creating assets in photoshop, taking screenshots, downloading things from an email...these are daily tasks for me. An iPad would struggle to do one of these at a time let alone all of them at once. iOS is just too limited to ever make…
I'm with you, but we have to remember that most people including most "pros" meaning working professionals do not do coding. For 95% of working professionals, the iPad may actually be more than enough.
Re: Building iPad Pro features in Swift
#14I just don’t see how an iPad Pro could ever really work as a computer replacement for true professional workflows. I’m talking about multitasking between final cut, building a website, creating assets in photoshop, taking screenshots, downloading things from an email...these are daily tasks for me. An iPad would struggle to do one of these at a time let alone all of them at once. iOS is just too limited to ever make…
I’m an artist who owns one and I totally agree despite it now being an essential tool for me. Lots of airdropping files back and forth with my MacBook is the reality and it works great.
You quickly realize just how crucial a mouse and it’s modifier keys are for efficient design work. It’s great for early stage thumbnailing. I’ve actually never been able to thumbnail as effectively as I can with the pro and it’s solely for the fact that I can use it as a sketchbook with integrated google images. Once a project gets rolling it’s mostly used so I can shuffle over to my comfy chair and do some detail work with the pencil.
That said, I wouldnt put it past a young person who hasn’t been molded by a desktop to blow me away with it. It’s not like my desktop workflows don’t have hacky and annoying steps along the way to a final.
Re: Building iPad Pro features in Swift
#15I just don’t see how an iPad Pro could ever really work as a computer replacement for true professional workflows. I’m talking about multitasking between final cut, building a website, creating assets in photoshop, taking screenshots, downloading things from an email...these are daily tasks for me. An iPad would struggle to do one of these at a time let alone all of them at once. iOS is just too limited to ever make…
I’m an artist who owns one and I totally agree despite it now being an essential tool for me. Lots of airdropping files back and forth with my MacBook is the reality and it works great. You quickly realize just how crucial a mouse and it’s modifier keys are for efficient design work. It’s great for early stage thumbnailing. I’ve actually never been able to thumbnail as effectively as I can with the pro and it’s solel…
Right it can work for part of the workflow for specific things like detail work with the pencil. What I find challenging is actually finding a smooth workflow that it’s not wasting time trying to get the iPad to do what I want. I feel like I spend most of my time working around it’s limitations so it’s hardly worth it (for me). Maybe that will improve with time though.
I also don’t really use iCloud Drive, maybe that would make things easier as one of the biggest problems is simply getting the things you want on the iPad ON the iPad. Importing photos for example, you have to import into photos and then double import to Lightroom.
Re: Building iPad Pro features in Swift
#16I just don’t see how an iPad Pro could ever really work as a computer replacement for true professional workflows. I’m talking about multitasking between final cut, building a website, creating assets in photoshop, taking screenshots, downloading things from an email...these are daily tasks for me. An iPad would struggle to do one of these at a time let alone all of them at once. iOS is just too limited to ever make…
I'm with you, but we have to remember that most people including most "pros" meaning working professionals do not do coding. For 95% of working professionals, the iPad may actually be more than enough.
Right. My use case is probably not the average one. I suppose if I did a lot of just emails and word processing/web browsing it would work. But it kind of defeats the purpose of all that horsepower.
Until Apple puts its own pro applications (like final cut) on the iPad, it’s not a real pro machine in my view. If it’s so “pro” then make your own apps work on it!
Re: Building iPad Pro features in Swift
#17Cool hardware, but there's no way I could justify the price to myself with the limited functionality of iOS as it stands today. A lot Apple tech writers/podcasters keep saying "just wait for iOS 13!", but the earliest a developer is going to see iOS 13 is 6 months from now at WWDC, the earliest the general public will get any additional functionality is 11 months from now. That's a LONG wait to see if any changes wil…
I think given the specifications of these devices, the pricing, while definitely high, is not completely unreasonable for what the hardware can do - these iPads do things no currently shipping Mac notebook can - 120hz refresh, 240hz touch/pen tracking, FaceID, performance in similar ballpark to a $3k MacBook Pro while passively cooled (!) etc etc. It’s just such a shame iOS isn’t quite ready yet to provide the kind o…
Wouldn't be surprised to see an ARM build of MacOS with new mac models on the A12+ chips.
Re: Building iPad Pro features in Swift
#18Earlier quoted context omitted.
I’m an artist who owns one and I totally agree despite it now being an essential tool for me. Lots of airdropping files back and forth with my MacBook is the reality and it works great. You quickly realize just how crucial a mouse and it’s modifier keys are for efficient design work. It’s great for early stage thumbnailing. I’ve actually never been able to thumbnail as effectively as I can with the pro and it’s solel…
Right it can work for part of the workflow for specific things like detail work with the pencil. What I find challenging is actually finding a smooth workflow that it’s not wasting time trying to get the iPad to do what I want. I feel like I spend most of my time working around it’s limitations so it’s hardly worth it (for me). Maybe that will improve with time though. I also don’t really use iCloud Drive, maybe that…
Adobe seems to be putting a lot of effort into Photoshop CC for iPad to make sure that moving back and forth between the desktop and iPad versions is effortless if you choose to work that way.
>the biggest change of all is a total rethinking of the classic .psd file for the cloud, which will turn using Photoshop into something much more like Google Docs.
“The beauty of it with Creative Cloud and the Cloud PSD and the innovations there is that you can just pick up where you left off, and you can be somewhat agnostic,” Belsky says. “You can always go back in history. You can share it and have other people be able to go back and undo things you did.”
https://www.theverge.com/2018/10/15/17969754/adobe-photoshop...
Re: Building iPad Pro features in Swift
#19Cool hardware, but there's no way I could justify the price to myself with the limited functionality of iOS as it stands today. A lot Apple tech writers/podcasters keep saying "just wait for iOS 13!", but the earliest a developer is going to see iOS 13 is 6 months from now at WWDC, the earliest the general public will get any additional functionality is 11 months from now. That's a LONG wait to see if any changes wil…
And another reason to wait a year at least to buy a new iPad Pro if you already have one. Wait till A13x or A14x to see an iOS that can utilize it properly.
Re: Building iPad Pro features in Swift
#20I just don’t see how an iPad Pro could ever really work as a computer replacement for true professional workflows. I’m talking about multitasking between final cut, building a website, creating assets in photoshop, taking screenshots, downloading things from an email...these are daily tasks for me. An iPad would struggle to do one of these at a time let alone all of them at once. iOS is just too limited to ever make…
> An iPad would struggle to do one of these at a time let alone all of them at once.
You haven’t touched a modern iPad, have you? Not only do they not ‘struggle’ to do one of those at a time, they’re butter smooth at it. The workflow/task juggling aspect is definitely an issue, but there is nothing preventing an A10x or A12x iPad from doing any of those things with all the performance you’d expect from a $3k+ MacBook Pro.