JOIN US: This is a chat-based conversation about how do-it-yourself IT development is becoming a staple in creating and fine-tuning new-gen enterprise applications.
A5 -- absolutely, #lowcode and #nocode still have a long way to go till they're mainstream. Today's CIOs have largely not even heard of them, and many hand-coders still scoff at the whole idea.
I think if the name evolves it will help.... we just don't get many devs who are excited to call themselves low-coders - same issue for CIOs who have to justify buying the platforms
A5 predictions from leading analysts are that low-code will be more common than traditional coding in a few more years - it's becoming the new normal... which begs the question, what will come next!
A5: definitely more mainstream especially for business internal apps. The technology will get there sooner than the mass market adoption, because of inertia and legacy systems.
A5 - it will become more mainstream because if companies don't learn to evolve faster they won't be around long - look at the average age of companies on the S&P - dropped to close to 10 yrs (from over 60) - automation is a key reason
will become mainstream when apps can not only be built faster with grater simplicity but more importantly IT ability to embrace the apps with full standards based developer friendly code customization and governance in place.
A4 - one person telling a platform what app to build is a great vision, but the reality is that this is a team sport, with collaboration across product and technical people. Facilitating such collaboration is essential to #lowcode today -- makes Agile's customer involvement real
I'm not going to argue with you that #lowcode enables "agile development". Devs have been talking agile development for decades. What I am saying though is that #nocode changes the level of abstraction. A team of people could collaborate at a higher level of intent
I agree with Jason's earlier point that the no-code and low-code platforms are converging - why not get the best of both worlds? This truly expands the talent pool but ensures flexibility and control when it's needed.
A4 - Deloitte did a keynote at our conference in denver a few weeks ago where they showcased an imagined future of development - all development done with a siri-esque assistant - describing what was wanted - it was quite entertaining - video on our site
a fair point. It's like I said earlier --- low-code/generate native code, sell to IT, that's all good and valuable and it is evolution. That is why every platform now claims it is low-code (some like Outsystems are real, some are not).
it's true that if you take a walk around any major vendor event - low-code is on every sign :) it confuses the market a little and I expect other terms will evolve over the coming months to attempt to provide clarity
A4: if I may make a bold claim, I think no-code app platforms have to be intelligent or they are not going to be very useful. The whole point is to understand the high-level intent of the app creator and automate the code that would otherwise have to be written.
A4: let's say a business user has a fleet of trucks that need to be inspected by the drivers every day. And if there's damage a report with photo needs to be sent to the manager. She wants an app for this. That's the high-level intent. It is no-code. Little else should be needed
@editingwhiz well that's the info. One way or the other, that's what the app creator inputs into a no-code system. The question I ask is --- how little translation should they need to do. Can the platform understand their intent the way they think of it?
Agree. AI evaluates the app, recognizes the development environment used to build the app, the frameworks, and methods inside the app, the resources available to the app and more.
A4: So many apps are similar across companies. #lowcode vendors typically offer templates for many of these. But with the right AI, they could automate the process of tweaking a template for specific needs.
A4: With the industry shifting away from traditional database architectures towards centralized, org-wide event streaming platforms, vendors will need to figure out how they fit into the event-streaming landscape.
