IFTTT comes to iPhone with a crisp app featuring native Photos, Reminders and Contacts channels
The digital glue service IFTTT is finally launching an iPhone app and it brings with it a set of new channels specific to Apple's platform and a lovely mobile platform for both building and using its automated actions.
Context & Ripple Effects
IFTTT has been pushing beyond its original web-service glue: in June 2012 it rebranded around a new look and moved into the physical world via Belkin WeMo compatibility, making connected hardware a trigger for automated actions. The iPhone app is the logical next step — until now, recipes could only be built and managed from the browser, leaving the fastest-growing smartphone platform without a native client.
The launch drew unusually broad pickup on day one — The Verge, GigaOM, Mashable, MacRumors, iMore, MacStories, PetaPixel and IFTTT itself all carried it — which reflects how contested the question of mobile-first automation had become. What makes this more than a port is the three new Apple-specific channels: native access to Photos, Reminders and Contacts puts personal data stores that other apps only reach through explicit permissions directly into IFTTT's recipe engine.
First-order effects
- iPhone users can now create and run recipes on-device rather than through a desktop browser, removing the main friction that kept casual users off the service.
- The new Photos, Reminders and Contacts channels turn Apple's own personal-data stores into triggers and outputs, giving IFTTT recipes reach into the core of iOS that third-party web hooks never had.
Second-order effects
- Connected-hardware partners like Belkin stand to gain most immediately: an always-in-pocket client means phone-side signals can now drive WeMo devices, strengthening the physical-world playbook IFTTT started in 2012.
- Rival automation and workflow tools now face a platform-by-platform race for equivalent native access — whoever secures deeper OS-level channel integrations first sets the bar competitors must clear.
Third-order effects
- If the native-channel pattern holds, consumer automation migrates from generic web glue toward OS-sanctioned integration, making platform holders like Apple and Google the gatekeepers that decide which automation services get deep data access.
- That gatekeeping dynamic points toward automation becoming a default expectation baked into mobile platforms themselves, squeezing standalone services to either become infrastructure partners or be absorbed into operating systems.
The trend: Task automation is migrating from browser-based web services into native mobile clients, with each platform's willingness to expose personal-data channels determining how far the category can go.