Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Building iPad Pro features in Swift

swiftbysundell.com

Post reply on HN
Print view View original

31–40 of 73 posts

Re: Building iPad Pro features in Swift

#31

Post by jrockway »

clay_the_ripper wrote: post #11

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…

I just have an ssh window and web browser open, both of which the iPad mostly handles fine. For me, it was a no-brainer because it's light and easy to travel with, and doesn't require 40 minutes of updates every time I open it (hello, Surface Pro 4, my previous laptop). Does it replace two 32" monitors? Nope. But I never had those when I was travelling.

I also draw and edit photos on my laptop. The iPad handles that fine. I have a Cintiq Pro 13" and it's a piece of garbage that made me hate drawing. I am glad it's gone from my life. The Apple Pencil is way better. (I hate Lightroom/Photoshop on the desktop, so I am trying to deal with Affinity. We'll see how that goes after I go on a trip where I take some photos.)

All in all, there are many tasks that can't be done on any laptop. That is why you can buy desktops. If the primary goal for your mobile computer is to not have to spend 40 minutes disabling Cortana, the iPad is perfect, which is why I bought one.

My only complaint is that Safari requests mobile sites instead of desktop sites. That is super annoying. I have a desktop-sized screen and a keyboard. Give me the desktop version.

Re: Building iPad Pro features in Swift

#32

Post by rangibaby »

jrockway wrote: post #31
clay_the_ripper wrote: post #11

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…

I just have an ssh window and web browser open, both of which the iPad mostly handles fine. For me, it was a no-brainer because it's light and easy to travel with, and doesn't require 40 minutes of updates every time I open it (hello, Surface Pro 4, my previous laptop). Does it replace two 32" monitors? Nope. But I never had those when I was travelling. I also draw and edit photos on my laptop. The iPad handles that…

> My only complaint is that Safari requests mobile sites instead of desktop sites. That is super annoying. I have a desktop-sized screen and a keyboard. Give me the desktop version.

Hold the refresh button you can reload the page as the desktop version

Re: Building iPad Pro features in Swift

#33

Post by lilyball »

Using UIPanGestureRecognizer for gestures that should be recognized immediately on touch down is a common mistake I see a lot of people make. The problem is UIPanGestureRecognizer doesn't actually start recognizing until the touch has moved a short distance, and at this point, you can't recover the original touch location, only the location at which the gesture recognizer began recognizing.

The solution is to use a UILongPressGestureRecognizer with minimumPressDuration set to 0. With this configuration, it will begin recognizing immediately on touch down, allowing you to take action even before the user has moved their finger (or pencil).

Re: Building iPad Pro features in Swift

#34

Post by saagarjha »

rangibaby wrote: post #32
jrockway wrote: post #31

Earlier quoted context omitted.

I just have an ssh window and web browser open, both of which the iPad mostly handles fine. For me, it was a no-brainer because it's light and easy to travel with, and doesn't require 40 minutes of updates every time I open it (hello, Surface Pro 4, my previous laptop). Does it replace two 32" monitors? Nope. But I never had those when I was travelling. I also draw and edit photos on my laptop. The iPad handles that…

> My only complaint is that Safari requests mobile sites instead of desktop sites. That is super annoying. I have a desktop-sized screen and a keyboard. Give me the desktop version. Hold the refresh button you can reload the page as the desktop version

This doesn't always work, because many websites use ways other than the User Agent to customize their websites (e.g. @media queries).

Re: Building iPad Pro features in Swift

#35

Post by clay_the_ripper »

djrogers wrote: post #20
clay_the_ripper wrote: post #11

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…

> 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…

I own an iPad Pro for reference. I should have been more Clear: while the iPad can do some of those things and certainly the hardware is good enough, iOS dowsnt fit my use case well (doing lots of things at once).

Re: Building iPad Pro features in Swift

#36

Post by clay_the_ripper »

GeekyBear wrote: post #18
clay_the_ripper wrote: post #15

Earlier quoted context omitted.

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…

That’s pretty cool and would be useful

Re: Building iPad Pro features in Swift

#37

Post by yargg »

lilyball wrote: post #33

Using UIPanGestureRecognizer for gestures that should be recognized immediately on touch down is a common mistake I see a lot of people make. The problem is UIPanGestureRecognizer doesn't actually start recognizing until the touch has moved a short distance, and at this point, you can't recover the original touch location, only the location at which the gesture recognizer began recognizing. The solution is to use a U…

How do you track the translation during the gesture if you use UILongPressGestureRecognizer? Do you have an example you can link too?

Re: Building iPad Pro features in Swift

#38

Post by jbigelow76 »

IOT_Apprentice wrote: post #19
jbigelow76 wrote: post #2

Cool 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.

Yep, I have a feeling this will happen alot, even if Apple waits 18 months to refresh iPad hardware that's still only 4-6 months from iOS 13's release. And maybe some hardware criticisms, like only one USB-C port, will be addressed (probably not though)

Re: Building iPad Pro features in Swift

#40

Post by tluyben2 »

saagarjha wrote: post #34
rangibaby wrote: post #32

Earlier quoted context omitted.

> My only complaint is that Safari requests mobile sites instead of desktop sites. That is super annoying. I have a desktop-sized screen and a keyboard. Give me the desktop version. Hold the refresh button you can reload the page as the desktop version

This doesn't always work, because many websites use ways other than the User Agent to customize their websites (e.g. @media queries).

Indeed, and it's very annoying. There should be an actual way to completely fake the site into believing you are a desktop.
Post reply on HN