426 karma · joined June 24, 2019
We've built all kinds of internal tools using Lowdefy, CRMs, reporting apps, ticketing systems, workflow, SOP and QC tools, call centre automation tools, customer portals, survey apps and more.
We find that having a well define abstraction framework in place helps us scale our custom apps really efficiently, particularly from a maintenance pov. Also sharing work across our team, etc. It helps if everything is pluggable, and well documented. By making Lowdefy open-source it has helped our team maintain the discipline to enforce best practices across our stack.
Lowdefy is very declarative, and it lets you build data intensive web apps in just a few lines of yaml. With AI code gen, this is where the power of the framework guard rails and generated apps really accelerate the apps we can create while following the same patterns that our team applies over all the solutions we build.
As for change in direction, no. We have a demand for building agentic experiences from our customers, and found that we could wrap it really nicely into the Lowdefy framework, especially when building in additional functionality like agents co-authoring web forms and more.
We feel that agents inside your apps is a great fit, since you can expose the same api routes, auth roles and more to agents with ease.
Well done on spawnfile. Looks very interesting!
for the everything else it was a win. will give it another chance in a month or three to see if it can do, excited to have a setup that easily navigates code diffs.
choose a good one and your can save you and your llms 1000s of decisions and future maintenance overheads.
frameworks exists because they scale.
Ofcourse large corps will have fancy proprietary models, but for every day queries and tasks, local feels like a huge, and just slightly out of reach.
Am i missing something fundamental?
Genius level AI marketing
This allows a trusted and tested abstraction layer that does not shift and makes maintenance easier, while making the code that the agents generate easier to review and it also uses much less tokens.
So as always, just build better abstractions.
i’ve always felt that oss licenses needs to include responsible use terms or something. some orgs dont mind paying for value contributed but you need to provide a structure to do so, even if that is on a voluntary basis.
If anyone from Lovable etc sees these comments, great opportunity for sponsorship where it can make a difference upstream.
Some companies have done this well, at a stage Retool use to sponsor a number of open source libs which greatly helped them with exposure to devs. Surely a better way to spend ad revenue imo.