I have been summoned.
To give some context on my perspective
I work for a school as a programmer, tasked with automating all their tedious manual labor. Because I will inevitably leave this job my main goal is to keep maintenance as low as possible, I effectively need to automate myself away. Giving non-technical colleagues the ability to automate and maintain their own workflows is a core part of this strategy, and in theory Activepieces fits the bill perfectly.
So where does this go wrong in practice?
I’ve been experimenting with how easy it is to set up simple workflows for non-technical users. So far this hasn’t been as successful as I had hoped, for three main reasons: lack of polishing, lack of documentation and abstraction leaks.
I have a lot to say about the latter two, but I’ll keep myself to polishing for now 
Enough foreplay, here’s the (partial) list of things I’ve encountered so far:
(Note: it’s very likely that there’s already topics on some of these, and probably one or two that have been fixed in the meantime.)
- There are a lot of small grammar/spelling/Capitalization issues across the product.
This usually doesn’t hurt the experience, but over time it tends to sour the perception of the product significantly. - Error handling is often suboptimal.
Two concrete examples I wrote down were “Look in console” that time some connectors broke and a vague “Throws an error” message around the “Tables” input when a MySQL connection fails. - There’s no way to edit/rename (database) connections.
- The “Webhook” trigger is not in the “Core” category.
- A “favorites” system for pieces would be sweet, since most people only use a tiny subset of them.
- Piece configuration and the test run console fight for very limited vertical screen space.
- There seems to be no way to cancel paused runs.
- The “Reset zoom” button uses a refresh icon.
- “Use as draft” in the Versions panel is odd to non-technical users who aren’t used to a “dev” and “production” version. My initial vibe was to suggest renaming it to “Revert”, but that’s not entirely accurate. Maybe this is just a teaching issue?
- Being able to label/name versions would be sweet.
- There’s no “Community” link at the top of the website.
- As mentioned earlier, comments are essential to keeping non-trivial flows maintainable.
- Google Sheets’ “Insert Row” piece has a question “Are the First row Headers?”.
Wacky grammar aside, what does this mean? Why is it relevant for adding a new row?
The description underneath (“If the first row is headers”) has a high “the floor here is made out of floor”-level
I have a bunch more, but I’ve ran out of energy to translate them somewhat coherently for now