Some of your Questions:

Q. How does LeBLANC compare to lowcode or nocode platforms?

Glad you asked! LeBLANC is intended to implement the larger core business systems, like expenses payable, project billing, logistics, insurance handling or a reservation system. Core systems own the data and handle the whole business process from start to finish. Core systems typically offer APIs to serve for example the lowcode/nocode utility apps.

Current lowcode/nocode tools are fit for creating small, few screen utility applications that typically implement one or few business process steps for oganizational users. These utility applications handle use cases like: Manager can view and accept travel expense, Show my timesheet and report working hours, Show the next destination for distribution van driver...

Q. What's LeBLANC view on Agile?

Our method, and most principles listed in Agile Manifesto aim for the same results: Continuously deliver valuable software, with working software being the measure of progress. We welcome changes, and include the business expert in key role during the design. If you were asking whether the work with LeBLANC can be organized to sprints and other Scrum practices - Yes, by all means. Or any other method you may prefer, we don't really care.

Instead of Agile, we see our approach closer to Lean: We eliminate fat from application development. Everything that can be automated, should be automated. We think that no customer should pay for things that can be automatically produced; Writing thousands of lines of boilerplate code, implementing repeating tasks, idioms and standard LOB features. Please don't. Instead: Add your unique business content, we handle the rest.

Q. MDD has been around for a long time, how is this better now?

Our method is based on 60+ years of real life business application development experience, not solely on academic interests like the 4GL mostly was at the time. Another difference is that we are not trying to solve how to build every imaginable application, but to limit the problem domain and keep tight focus on line-of-business applications (I wouldn't recommend building Fortnite gamer user interface using LeBLANC). We constantly seek repeating patterns and tasks in LOB application development, and try figure out how to automate these. Also finding the right abstraction level is crucial - there are things that are easier to code, than try solve with models. One major caveat in previous attempts was that the CASE tools used to be rigid - you couldn't touch the generated code without breaking the application. We can. Also - this is not a black box. You get full source codes that you can modify, and you have no vendor lock.

We have actual proof from real life projects that our method really works.

Q. What is a white labeled application?

The application you get as a result from Fusion Transformer is "white labeled". This means that the user interface you get is themed with our default LeBLANC look and feel, and the idea is that you theme it to suit your needs - add the company colors, your logo, footer texts - you can alter the whole application outlook with CSS style sheets. We've reserved app.css stylesheet for your customizations, which you can use to override our default white label theme.