Funny because with your thinly veiled attempt to diss Apple you've just summed up the entire tech industry. And one would wonder why you are on an Apple-centric tech website.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Encourages App Store Developers to Adopt 3D Touch
- Thread starter MacRumors
- Start date
- Sort by reaction score
Funny because with your thinly veiled attempt to diss Apple you've just summed up the entire tech industry. And one would wonder why you are on an Apple-centric tech website.
Yes. It has guided my purchase decisions for the last couple of weeks and it will continue indefinitely.
Do you only buy at stores that have apple pay or only use Apps that only support touch ID?
As much as i would like to use 3D touch, i much prefer to have a smooth experience while opening safari tabs, links etc
Hey apple I encourage you to not charge me 100 bucks a year to develop apps on overpriced hardware I have to purchase, and now you want to tell me i need to write software in order to justify your device? Anything else I can do for you while I'm at it?
Force touch is just a right click...get real it's not needed in 99% of use scenarios.
How bout this, force touch integrated apps get 100% commission on each sale? While we are it, Why don't devs get discounts on hardware? Students do.
Oh yeah Apple and instead of claiming "we paid out billions to devs last year" let's be honest, it was your iOS users that did the paying, you took a huge share for simply hosting, and then tried to take the credit.
honestly Apple should be paying us 100 bucks a year to develop for them.
Force touch is just a right click...get real it's not needed in 99% of use scenarios.
How bout this, force touch integrated apps get 100% commission on each sale? While we are it, Why don't devs get discounts on hardware? Students do.
Oh yeah Apple and instead of claiming "we paid out billions to devs last year" let's be honest, it was your iOS users that did the paying, you took a huge share for simply hosting, and then tried to take the credit.
honestly Apple should be paying us 100 bucks a year to develop for them.
Last edited by a moderator:
Gee Apple, maybe you should add 3D Touch support to the Simulator if you want more devs to develop for it!
https://developer.apple.com/library...Phone/#//apple_ref/doc/uid/TP40016543-CH1-SW7
Neither does Xcode 7.2 =P
https://developer.apple.com/library...Phone/#//apple_ref/doc/uid/TP40016543-CH1-SW7
Neither does Xcode 7.2 =P
I also used to delete apps on my 6+ that didn't support the large screen but would never think about deleting any just because they don't support 3D T. But on the other hand it only shows how lazy some developers are if they don't bother adding functionality of a new feature even after 4 months.
By the time there is enough 3D Touch users, Apple have changed how it works. It means double effort. Current 3D touch is v1. (or beta)
This. Although I am more than happy with battery life already. But 3Dtouch...sounded cool but it is nothing but annoying in practice.
I just wish they'd stop saying "This app now supports 3D Touch" when all they've done is put in a deep-linked menu into the app that you can access from the home screen - and that's it.
"3D Touch Support" should mean integration throughout the app (which is where the feature is most useful), not just we've added a menu (That let's be honest, no one will ever use).
That's pretty dumb, to be absolutely honest.
"3D Touch Support" should mean integration throughout the app (which is where the feature is most useful), not just we've added a menu (That let's be honest, no one will ever use).
That's pretty dumb, to be absolutely honest.
Last edited by a moderator:
3D Touch doesn't make sense for any/every app. So if you're really "only" buying apps from developers that implement 3D touch - well, you're encouraging some developers to use something just for the sake of using it. Personally, I think that's silly.
My 6+ has awesome battery life. When I had a Galaxy S5 I was charging at least once a day as the battery life there sucked. Since I got to the 6+ at the end of the day I think the worst I've seen is 25%.
Wireless charging would be nice but not a must have.
In fact, Apple should make iOS 10 exactly like iOS 1, just with improved battery and charging!
I'm pretty sure Apple has the maximum practical # of engineers working on both "gadget gimmicks" (a term usually used by the unimaginative among us) and improving battery technologies.
3D Touch reminds me of the screen size change in iPhone 5. Anyone who gets the first device to implement a major change that requires app devs to support it gets stuck between the old way and the new way from app to app. It will take a second iPhone released with the same feature before we see commonplace adoption.
I'd like to second that. I think one of the best use cases for 3D touch is peak/pop for email, but I don't use the stock email app. I use Outlook and Inbox for my respective emails. Outlook did what you described above (just added 3D touch to the app button) and I was really hoping for peak/pop functionality. Seems like adding peak/pop to an email app would be almost easier that the home button thing, which probably requires more work on the back end to deep link their app.
Overall, since I don't use the stock mail app, my 3D touch experience has been a little disappointing. The app button thing is ok, but I always forget to try it, even wanting to see if it would help my experience. The only other place I use it is Safari, which is great when you have good service, but is more annoying when your service isn't great (holding the precise pressure for a peak gets annoying while waiting for something to load).
As a developer actively maintaining multiple apps I have not found a single reason to add force touch anywhere.
There is no best practises how or where it should be applied yet so it's more of an easter egg kind of thing where it does work. There is no consistency in the behaviour across the community.
Most of the time where it has been implemented it feels like "just because" rather than it making sense from a UX perspective.
From a general usage point of view it's difficult to separate the action of force touch from a long-press. I think it's confusing more than anything else.
I'm going to call gimmick on this one until I find a compelling use case.
There is no best practises how or where it should be applied yet so it's more of an easter egg kind of thing where it does work. There is no consistency in the behaviour across the community.
Most of the time where it has been implemented it feels like "just because" rather than it making sense from a UX perspective.
From a general usage point of view it's difficult to separate the action of force touch from a long-press. I think it's confusing more than anything else.
I'm going to call gimmick on this one until I find a compelling use case.