expressPython VS lowdefy

https://github.com/JaDogg/expressPython - goal was to learn some C++ and Python, I wanted to work on text input and wanted a UI.

https://github.com/JaDogg/sbx - flashcards console app (not sure if there are similar applications)

https://github.com/JaDogg/pydoro - pomodoro timer console app (I couldn't find such application)

We’re considering building a coding agent for Lowdefy[1], a framework that lets you build web apps with YAML config.

For those who’ve built coding agents: do you think LLMs are better suited for generating structured config vs. raw code?

My theory is that agents producing valid YAML/JSON schemas could be more reliable than code generation. The output is constrained, easier to validate, and when it breaks, you can actually debug it.

I keep seeing people creating apps with vibe coder tools but then get stuck when they need to modify the generated code.

Curious if others think config-based approaches are more practical for AI-assisted development.

[1] https://github.com/lowdefy/lowdefy

Internally, DatAasee is realized as a three tier software architecture, where each tier is encapsulated in its own container. The inner data-tier is a multi-model NoSQL database ArcadeDB. The middle logic-tier is an (HTTP-JSON-REST) API-server and semantic-layer around the database realized via Connect (aka Benthos). The outer presentation-layer uses Lowdefy as a prototype frontend which exclusively uses the API. This multi-container application is deployed and orchestrated via Compose.

Would love this for us to help us build interactive tutorials for Lowdefy, very cool. also think it is important that it exports well to youtube etc. and link back for when users want the interactivity.

Would be super if the player can be embed in docs.

https://lowdefy.com

We’ve built Lowdefy to address this use case and more, check it out https://lowdefy.com

Happy to answer some questions and show you what we’ve built with Lowdefy - It’s very powerful and easy to get started with and maintain. gvw at lowdefy.com

GitHub https://github.com/lowdefy/lowdefy GitHub Star 2.6k GitHub Fork 160 GitHub Issue 30 GitHub Pull Request 3 GitHub Contributor 24 Most Recent Update on GitHub Two mounth ago Open Source License Apache-2.0 Official Website https://lowdefy.com/ Documentation https://docs.lowdefy.com/

I'm really enjoying reading through the docs and the tutorial. We've created Lowdefy, a config web-stack which makes it really simple to build quite advanced web apps. We're writing everything in YAML, but it has it's limitations, specifically when doing config type checking and IDE extensions that go beyond just YAML.

I've been looking for a way to have typed objects in the config to do config suggestions and type checking.. PKL looks like it can do this for us. And with the JSON output we might even be able to get there with minimal effort.

Is there anyone here with some PKL experience that would be willing to answer some technical questions re the use of PKL for more advanced, nested config?

See Lowdefy:

https://lowdefy.com/

https://github.com/lowdefy/lowdefy

Awsome! With Lowdefy we tried to build a low-code framework that works like code. We’ve developed a schema in which to define applications and we’ve built all kinds of apps for enterprise customers. Massive, advanced CRM systems, call centre solutions, ticketing systems, a light MRP, all kinds of survey apps and so many dashboards. Even our docs and our website are Lowdefy apps!

Give Lowdefy a try and reach out it you have any questions or want to see what is possible :) (We need to invest a lot more into content and examples, bootstapping is a grind!)

https://github.com/lowdefy/lowdefy

Also add Lowdefy onto the list https://github.com/lowdefy/lowdefy

co-founder here :)

100% this. And yes, good documentation takes a lot of investment but it pays off like compound interest. But with that done, it becomes even more important not to pull the carpet for no good reason, you are building a tower and documentation is at the foundation.

We’ve built Lowdefy [1] as an open source project and documented it with all effort, 200 pages of docs. I often forget why or how something works and then jump to the docs. This investment keeps on paying of as we use Lowdefy to build customer apps, new devs in the team typically take less than two week to get up to speed and start making contributions, the sharp ones, just a two or three days.

This year, we’re extended our documentation onto customer apps aswell, with flow diagrams, state machine definitions, detailed field level explication schema definitions, and end user test procedures. The key here for this documentation is detail. It should be easier to reach for the docs and the the answer, than to dive in the code and interpret it.

1 - https://github.com/lowdefy/lowdefy

https://github.com/lowdefy/lowdefy Co-Founder here.