IFTTT for iPhone 01

Get the most up to date on iPhone/iPad innovation: Ipads Advisor

IFTTT, the internet services automation startup backed by $8.5 million from NEA, Andreessen Horowitz, and others, is now available as a mobile app for iPhone. Like the internet variation of IFTTT, the app permits you to develop and edit tasks (in IFTTT lingo, ‘dishes’) that permit you to start activities based on other tasks. For instance, if it’s raining, then text me, or save my Gmail attachments to Dropbox. However by its mobile nature, the new app can likewise now use iOS native applications like your iOS Contacts, Photos and Reminders.

The startup’s name is an acronym which describes what it performs in distinctly geeky terms: ‘If this, then that.’ The concept to put devices that stitch together and automate internet services in the hands of customers has been around for a long period of time – most significantly, maybe, with Yahoo Pipeline, an online service for mashing up and adjusting content from around the internet.

But where Yahoo Water lines is still overly complicated for the normal end user, IFTTT is extremely simple.

After spending time with the mobile version, there are 2 things I’ve actually come to recognize. One, that the minimalistic and tappable mobile interface is now my favored way to interact with this service. It’s perfectly made and incredibly simple to utilize.

And two, that I want the iOS app integration were a little even more durable.

The IFTTT app recommends a mobile-specific dish upon first launch called ‘Save my iOS Photos to Dropbox.’ While that seems useful enough, the capability to auto-upload camera photos to Dropbox is really a feature of the Dropbox iOS app itself (though IFTTT lets you configure a particular folder), so it’s not as handy as it first noises.

This illustrates among the obstacles I have faced with IFTTT in the past. The idea of IFTTT is occasionally more excellent than the reality. This isn’t always the startup’s fault, though – it’s frequently an issue with the openness of the APIs it counts on.

iOS Recipes

Of the 67 channels that are supported, 3 have been built for iOS. In terms of these brand-new iOS app-specific recipes, those created to work with the iOS Photos app are the most helpful, I found. For example, you can set up IFTTT to instantly publish images to a selection of services, even specifying which kind of pictures go where (e.g. images taken with the front-facing camera, screenshots, those in certain cds, and so on) Nevertheless, IFTTT fails on performing among the more obvious mobile-specific activities you’d want to take next, like sharing pictures with someone else via TEXT.

According to CEO Linden Tibbets, the TEXT restriction, in the meantime, is by design. Though he explains that it’s technically possible to make it possible for IFTTT to text others, the business wished to put safeguards in location first so that hadn’t been abused.

When it concerns a few of the other iOS app options, I spotted a few other missing out on products, as well. There was no iOS Calendar trigger, which seems like an additional evident miss out on. I ‘d enjoy to be able to utilize Apple’s own calendaring application, then have it sync somewhere else, or trigger other activities to happen, for example, like sending out texts to participants, or including tips to Evernote.

However, the business describes that, unfortunately, there’s not yet a method for it to straight get in touch with the iPhone Calendar due to Apple restrictions. That may change with iOS 7, however for now, the entire option is missing out on due to this limitation.

Meanwhile, when working with iOS Contacts, there was only one trigger to start with: including a brand-new contact. Again, activities that look like the next rational step following that activity are also lacking. You cannot send out the contact a form email, for instance – something that’d be practical to those networking and marking individuals into specific contacts groups. You can’t buddy them on Facebook or LinkedIn or follow them on Twitter. You cannot send them a text message, which is something new buddies frequently do to make sure the various other individual has their phone number, too.

In a lot of cases, these issues are technical in nature. Tibbets agrees that the friending use case is ‘super legit’ but kept back by API and limitations.

‘Among the things we are actually delighted about is helping our channel partners take more ownership over things they’ve the ability to do via IFTTT,’ he says, implying a demand for even more direct relationships that’d enable IFTTT to bypass some API constraints.

API Limitations Are An Issue

Many web companies have been dialing down the functionality they provide by means of their APIs to various other third-party developers in order to have even more control over their service and network. Facebook, has actually infamously pulled its ‘discover pals’ feature from a variety of challenging apps and Twitter is constantly adjusting developers’ abilities, and desiccating some businesses at the same time. While business sometimes have legitimate reasons for doing this sometimes, IFTTT’s constraints are the other side of those constraints. This is why we cannot have nice things.

In addition, Apple’s notoriously tight lockdown on its os and apps prevents a few of the adaptability that Android users have when it pertains to relocating information between the mobile app silos, or using apps like Tasker to automate various other elements of their phones, such as enabling and turning off numerous features and modes, transferring files, auto-dimming displays, and more.

A great deal of those kinds of things are out of IFTTT’s reach due to the fact that of Apple’s limitations or insufficient web APIs. It’s a problem that IFTTT will have to identify how to conquer with workarounds or direct partnerships. It’s also one of the problems I have had with IFTTT in the past. Commonly, when it strikes me to automate a job using the service, I find that the specific task I want is missing, though the internet service I am hoping to link to is supported.

I can’t always point the finger at IFTTT in all cases, obviously. However other times, I think there’s room for IFTTT to offer a little more personalization for power users who want to go beyond the defaults. Or heck, even include an ‘unless this’ to the end of operations.

But that’s me being selfish. IFTTT prospers by straddling between a service for power individuals and being one for the ‘normals.’ Going too far with personalization options might turn exactly what’s easy and quickly into an intricate mess – even more like Yahoo Pipes.

Android Could Be Better

I am a little let down that IFTTT is an iPhone-first app, too. While iOS is undoubtedly an essential platform to resolve in terms of customer reach and market share, it doesn’t actually exhibit IFTTT’s potential on mobile. The relative openness of Android could’ve enabled a wider selection of phone-related activities and would’ve been a substantial draw for a user base who wants an appealing app rather of those (like Tasker, sorry) that look like they were created by a business IT division.

Android is on the roadmap, says Tibbets. ‘Android is in no way a 2nd place. It’s really cool and getting cooler all the time,’ he includes. ‘It’s simply an issue of limited resources.’ And individual interest, it appears. The IFTTT group utilizes iPhones, so that’s where they started.

At completion of the day, IFTTT’s app is a wonderfully designed production and one that’s somehow even simpler to utilize than it was on the internet. It’s still a must download for active web individuals. But with the restrictions around Apple’s OS and other web services’ APIs, IFTTT cannot yet reach its full potential on internet, iPhone or whatever comes next.