News for hackers. Stuff that matters.
Re:Ask HN: What are some good no code / low code tools to le... by _qjt0 on Thursday January 09, 2020 @02:02AM (#21999111)
Interesting, based on this experience, what must-have criteria would you look for in evaluating a tool? Ability to export the code if the tool proves too constraining? What else?
Re:Ask HN: What are some good no code / low code tools to le... by codingdave on Thursday January 09, 2020 @09:10AM (#22001274)
It is not so much about the tool helping a future dev re-invent the solution in a high-code platform. It is more about preventing lock-in. I'd like to see a vendor whose business model embraces the fact that their most successful apps will move to something more powerful. Where they consider themselves to be a stepladder up to a fully developed app, and not a platform that will take over all of enterprise IT. So they would be more of an internal app incubator, not a permanent app hosting platform, focusing on service to their customers, and therefore when it comes time to move on they are a fully engaged partner, not an adversary.

At the same time, it would be terrific to help the devs on low-code platforms avoid mistakes. Flag redundant data, point out when they have written sub-optimal workflows, give them easy ways to implement re-usable code blocks when the system notices they just wrote the same function twice with one parameter change. Data imports are also always a struggle, because most anyone can figure out how to get a CSV or Excel file brought into a system, but reading from a web-based endpoint, or parsing data from Word files tends to be beyond the capacity of most users, even if the system itself supports it.

Re:Ask HN: What are some good no code / low code tools to le... by kinj28 on Wednesday January 22, 2020 @10:45AM (#22118483)
I run a nocode platform with some large and global applications made/run on our platform.

During architecting phase of the application - we do estimate if nocode tooling will hit a ceiling. If yes then we explore 4 options:

- no brainer, export code and take it from there

- write custom Ui controls and patch them into your nocode tool

- write custom function and patch in the workflow engine or front end logic

- build Ui/UX using external code and use nocode to build backend process and connect front end with apis of the workflows/dbs

- generally complex algorithms - eg route optimization, would become a candidate of converting into a web service and eventually consumed in the nocode tool.

In my experience - One of the core essentials to write an application on nocode is having your sprint 0 dedicated towards a design phase.