Built.io is #15 in Top 21 Mobile App Builders

Last updated: October 06, 2016
Build mobile apps fast, Connect your digital business, Deliver content everywhere.

Positions in ratings


#15 in Top 21 Mobile App Builders

Alternatives


The best alternatives to Built.io are: Parse, Appcelerator, Adobe PhoneGap Build



Latest news about Built.io


2016. Built.io launches an IFTTT for business users



Built.io has long offered an integration tool Flow that allowed technical users (think IT admins and developers) to create complex, multi-step integrations with the help of an easy to use drag-and-drop interface. Now the company has also launched a more basic version of Flow that is aimed at business users who want to create IFTTT-like integrations between applications like Cisco Spark, Slack, Gmail, Marketo and Salesforce. To clarify the difference between the two services, the old version of Flow is now Flow Enterprise, while this new one is branded as Flow Express.




2016. Built.io Flow makes building enterprise integrations easier



Built.io is launching a major update of its enterprise integration service Flow that will make it easier for businesses to build more powerful integrations. Flow is a drag-and-drop tool for building enterprise integrations. It’s a bit of a mix of Yahoo Pipes (R.I.P.) and IFTTT for connecting services like Salesforce and Marketo to help automate the sales process in an organization, for example.  It’s worth noting that in the world of enterprise, integration is still a big business, with plenty of development shops doing very little else but helping their customers connect various third-party services. The Built.io team argues that it can take a process that often takes weeks and reduce it to a few hours.


2016. Distributed content management system Contentstack launched of a set of mobile SDKs



Built.io Contentstack, the headless content management service (CMS) that aims to challenge the likes of WordPress and Drupal in the enterprise, is getting a major update today with the launch of a set of mobile SDKs for Android and iOS, as well as a refreshed interface for both developers and content editors. The idea behind offering a headless CMS is that content tends to live on a multitude of platforms these days. So instead of having a monolithic CMS that also handles the presentation of the data, a headless CMS only focuses on content creation and developers can then integrate this data across different platforms.