New 3DTouch Uses For The ST IOS App

Apps & Clients iOS
1

As more people buy into the newer iPhone offerings over the next 12 months, will SmartThings make use of the new features offered from Apple, such as the 3D Touch feature. . . They did a nice demo of a forced press upon an app icon from the hoe screen . . . that then opened up a sub menu of recent or common or pre-assigned gestures / rules etc

this could be used throughout the ST app, for example:

1.) On iPhone home screen, force-press on the ST icon to open up most common rules/switches/or change modes

2.) when in Rooms View within the ST App, force-press a rooms name to open up a quick sub menu for switches/rules/modes related to that room

3.) force-press a device to quickly look at the other sensor data of that device without having to get deep into the preferences section (y)

any other views and ideas on this ?

4 Likes
2

This would be great to also:

  1. Quickly dismiss Smart Home Monitor false alarms directly from the iPhone home screen.

  2. Arm/Disarm the Smart Home Monitor.

  3. And most helpful, add a customization option in ST to let users create their own custom 3D Touch shortcuts that triggers an action.

2 Likes
3

i couldnt agree more :slight_smile:

4

Just make sure there’s an easy hands-free accessibility option for everything as well, and I don’t care how you do it. :sunglasses:

But there’s also the argument that the iOS experience should not be dramatically different from the android experience and the windows phone experience. So I understand that position as well.

5

That argument is false — an app should take advantage of the native experience offered by the platform. People choose for a reason. :slight_smile:

2 Likes
6

While people choose the OS they want for a reason, a company offering an app has three choices:

  1. Only support one OS

  2. Support multiple, but keep each app experience similar

  3. Support multiple, and take full advantage of the individual differentiating features of each OS.

As soon as they go to 3), their own support costs go way up. They have to be able to solve the same problem in multiple ways, and they have to be able to answer the same question in multiple ways while still keeping individual nontechie customers happy with the answers. :wink:

When the app is supporting a physical device purchase, I think most companies do go with 2). The customer can have whatever phone they like, but their relationship with the company will be more about the primary product, and less about the app. So I think it makes sense if the app doesn’t necessarily take advantage of every possible advanced feature of each separate OS.

If the company’s primary product is the app itself, then I think it makes more sense in terms of the customer relationship to have fully differentiated Apple versions and android versions and windows phone versions . In part just because they have to compete with the single OS apps that will be their competitors.

So there a lot of factors that go into the business decision of which features an app will support. I don’t think there’s a single right answer. It’s often a balancing act.