AndyP wrote: ↑Sun Oct 02, 2022 9:41 am
Why is appli, appli and not LiveCode?
A truck and a sedan are both vehicles, and have overlapping use cases, but also sufficient differentiation that there's a thriving place for each among people looking for vehicles.
The LiveCode engine is very powerful, thanks in large part to an expressive, flexible scripting language with a very rare integration of GUI elements as integral parts of the language. Time invested in learning to use LiveCode Script well pays ever-bigger dividends in the scope of what a developer can do with it.
This offers tremendous benefits for developers and even hobbyists who enjoy programming. But people enjoy many things, and not all of them include programming.
Yet nearly everyone can benefit from bespoke software, and since the dawn of GUIs there's always been a niche for
assembling software visually. CourseBuilder, OWL, VPL, Authorware, Prograph, Scratch, and many others are as much a part of the evolution of making software as Pascal, HyperTalk, C, JavaScript, Python, and the rest.
In recent years there's been a renewed interest in visual programming, rebranded for today's audiences under the moniker "no-code".
(As a side note you'll also see the term "low-code" used these days, but that term is so vague and overused it serves no useful purpose for understanding software tool categories; I generally avoid it in all discussions outside of SEO.)
Exactly why has entered a new heyday in this third decade of the 21st century is worthy of study. There's more to it than the catchy "no-code" phrase. I believe it rests on a combination of UX achievements supported by cloud technologies and computing ubiquity via mobile, coming together resonantly for an audience who came of age in a world of smaller-focus apps, setting the stage for a new set of expectations reasonably well met by some of the better "no-code" tools.
I think the UX part of this is key, not only for understanding this resurgent interest but also in recognizing the mutually-complimentary relationship between LC and Appli.
LC Ltd is a technology company whose core strength is delivering a rather amazing collection of tooling that makes crafting GUIs simpler than nearly any alternative covering the same scope of platforms.
LC's core audience has never been any one segment, but a very long tail of diverse use cases ranging from courseware in schools to analytics in the enterprise and thousands of extremely vertical solutions for small and medium organizations in between.
LC offers no specific solution to a specific segment (and indeed attempts to focus on one have been disappointing), instead delivering a unique way of working that allows programmers to craft a vast diverse range of unique specialized solutions cost-effectively.
Appli is primarily a design effort. With all the strengths of LC as an underlying technology, the Appli team can focus on deep research and a highly-iterative design process to craft a user experience finely tailored for a specific subset of personalities and organizational roles.
Either project could do what the other does (and since LC also makes an IDE and the Appli team writes a lot of code, to some degree they do). But why?
There are only so many hours in the day. Every activity carries opportunity cost: doing any one thing means not doing everything else.
A technology company with a long tail and a design project with laser focus on one segment seems a very good compliment for one another.
And apparently LiveCode agrees: Appli was the subject of a featured talk at the last LiveCode conference, and based on that I would imagine we'll see more comarketing going forward.
They seem very happy with the arrangement between the two products, and I'm equally happy supporting them both.