You can't compare the accuracy of speech recognition to LLM task completion rates. A nearly-there yet incomplete solution to a Github issue is still valuable to an engineer who knows how to debug it.
One factor that no one seems to have noticed is that both cofounders, Ravi and Joshua, have already built fairly big companies. Ravi was the co-founder at Heap (he took over my co-founder spot after I left), and Joshua was the CTO at Benchling.
Both of those companies have raised >$100M. After that success, the prospect of continuing to run a middling company in the shadow of Retool isn't very appealing.
There are lots of examples in the use cases section of any low-code vendor, but in short, most internal tools are not in the horizontal categories you listed. They're in vertical, industry-specific categories at SES (Software-Enabled Services) companies.
A quick commerce startup, for instance, is unlikely to find an inventory tracking app off-the-shelf that fits their workflow, since existing ERPs are not going to fit their workflow.
Agreed. So far, building macros (https://www.plato.io/blog/introducing-macros), we've found that if you provide an easy and immediate way to map program elements to their meaning, non-techies can understand pseudocode in the form of linear lists of actions, even with branching/looping via indentation.
We support concurrent editing, so you see updates from your teammates in realtime, but we just haven't built a frontend for it yet, so you don't get the visual indicators a la Figma of where your teammates are and what they're doing.
Mostly, yea. It's generated from the sequence of actions the user takes in the UI, with a little bit of inference so we can detect, for example, that a user actually is trying to update the first row in a filtered table, rather than a specific row with a specific ID.
And they can be triggered in lots of different ways (buttons, forms, events), not just keyboard shortcuts.
We're not looking for partnerships right now, but message me and I'm happy to chat about visual programming. Max/MSP is the OG (though we of course are bullish on macros vs. flowcharts).
Definitely, though the semantics of field mappings often only exist in a user's head, so will need to be explicitly defined.
English prompts will no doubt be a big part of Plato, though. We're still figuring out exactly where the line is between English and traditional UIs. Have you read any good analysis on the subject? Here's one that explores the limits of LLMs: https://magrawala.substack.com/p/unpredictable-black-boxes-a...