While you can add multiple data sources, mostly in the form of unique Honeycode tables, you can’t do things like trigger a REST call from a form submission and get data back from a third party service to inform the next step in the user experience.

Web service endpoints are not as ubiquitous as they could be.

While some basic field level validation exists, real data processing is limited to what a user can derive from spreadsheet based functions.

Business logic management appears to be somewhat limited at launch.

Not a bad concept, but not a great solution for some of the hobbyists or entrepreneurs hoping to launch their own app on the App Store. This makes it feel like more of a B2B solution where users will install the vanilla Honeycode app, log in, and get access to apps their organization has published.

Honeycode.aws apps can be published to the App Store, but only through the proprietary Honeycode.aws app.

We are still in the process of confirming these limitations and welcome any helpful feedback, but here are some of our concerns: This is one signal to me that there is much more planned here, and that the beta is limited by design.

– there are a few areas that are limiting in the beta release.

While the product team at Honeycode has nailed some of the usability concepts that other platforms have lacked – in-app guides, usable templates, etc. Will Honeycode end up like Google’s App Maker platform and be deprioritized in favor of some acquisition later? Google did purchase AppSheet recently, who we covered last year through an interview with Santiago Uribe, now a Senior Product Manager at Google.ĪWS doesn’t really have the same history as Google though, and could Honeycode evolve into something beyond a Quickbase or AppSheet competitor? Should vendors like ProcessMaker or other workflow automation vendors be concerned? What can I really build with Honeycode? With the release coming in the form of a beta, we won’t really know the planned scope of this platform for some time.

Nocode web app builder