Hacker News new | ask | show | jobs
by dgllghr 487 days ago
Looks very nice with a well thought out landing page and explainer video. I wish there was an offering like this that also included a low-code interface builder like Retool/Budibase/etc. so that it was easy to put a human in the loop with a web app. Appsmith has built in workflows but I have never used them because they are behind a paywall and I don't want to start paying before I know how good the workflows are.
1 comments
shivsarthak34 487 days ago
I agree , a brief explainer/demo video does a lot of convincing. Would you mind explaining your usecase ? I'd love to know if something can be accommodated in flowripple.
link
dgllghr 486 days ago
Sure! Here is a use case that I have now encountered multiple times. We want to do data ingestion of some kind, but one of the steps involves human intervention (editing, confirmation, annotation, etc.). For these human intervention steps, we have wanted to build a custom web UI very quickly and only for internal use. So we have turned to a low-code tool. However, we then have to do custom integration between the low-code tool and the workflow automation system. We have ultimately never actually used a workflow automation system because we end up just handling the "workflow" from the low code web UI through a DB.

But what I really want is a workflow tool that integrates with low-code in the following way: as records come in, they are stored somewhere. There is an interface where a user can "claim" a record and then do their work on it. The workflow tool handles concurrency so that a record can only be claimed by one user at a time. The user either finishes processing the record and it moves on in the workflow, they discard their work and it returns to the original state so that it can be claimed again in the future, or they save their work so that they can come back and finish processing it later. There would need to be some kind of time out mechanism or a way to return a record to the original state.

The actual processing of the record happens using a custom interface that is built with low-code. So for text annotation, they land on a custom text-annotation interface when they claim a record.

Does that make sense?

link