In this post, I’ll be talking about some AI-focused no-code platforms:<\/p>\n\n\n\n
The objective of these platforms is to reduce the use and integration of AI APIs and tools to a drag-and-drop process. Given how much of, for example, a Python implementation of LangChain is boiler-plate code, this isn’t as lofty a goal, as say AppSmith or Bubble, which seek to do the same but for a broader audience.<\/p>\n\n\n\n
All of these tools, at least from the AI perspective, are in their infancy. I know N8N of old, whilst the other two contenders are new to the block. As such, they all have weaknesses which will mean they’re probably not production ready – but that doesn’t make them any less useful for MVP (minimum viable product, aka first prototype) development or for general noodling on an experimental basis.<\/p>\n\n\n\n
Here’s a totally unobjective review of the strengths and weaknesses of the three candidates:<\/p>\n\n\n\n
My final take: I’d use Flowise for a proof-of-concept and then use that as the basis for a ‘living specification’ and subsequent development in a conventional programming language. The no-code environment provides very natural way to experiment with ‘prompt engineering’. Every flow having an authenticated endpoint and being embed-able is a killer feature. <\/p>\n\n\n\n
In time, if any of these platforms gain traction, I’d expect them either to be absorbed by the likes of make<\/a> or zapier<\/a> or gazumped by one of the Big Boys (if I was a betting man, I’d say Microsoft…).<\/p>\n\n\n\n No-code is, without doubt, here to stay. I don’t think we’ve scratched the surface of what it can do – we should be able to lay out the initial flow in natural language, and then tweak in a gui for example – but be wary of ‘eggs in baskets’.<\/p>\n","protected":false},"excerpt":{"rendered":" In this post, I’ll be talking about some AI-focused no-code platforms: The objective of these platforms is to reduce the use and integration of AI APIs and tools to a drag-and-drop process. Given how much of, for example, a Python implementation of LangChain is boiler-plate code, this isn’t as lofty a goal, as say AppSmith […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-86","post","type-post","status-publish","format-standard","hentry","category-uncategorised"],"_links":{"self":[{"href":"http:\/\/patrick.direct\/index.php\/wp-json\/wp\/v2\/posts\/86","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/patrick.direct\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/patrick.direct\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/patrick.direct\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/patrick.direct\/index.php\/wp-json\/wp\/v2\/comments?post=86"}],"version-history":[{"count":1,"href":"http:\/\/patrick.direct\/index.php\/wp-json\/wp\/v2\/posts\/86\/revisions"}],"predecessor-version":[{"id":87,"href":"http:\/\/patrick.direct\/index.php\/wp-json\/wp\/v2\/posts\/86\/revisions\/87"}],"wp:attachment":[{"href":"http:\/\/patrick.direct\/index.php\/wp-json\/wp\/v2\/media?parent=86"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/patrick.direct\/index.php\/wp-json\/wp\/v2\/categories?post=86"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/patrick.direct\/index.php\/wp-json\/wp\/v2\/tags?post=86"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}