LC Built Apps held Hostage, Runtime execution rent - looked at FAQ
harrison at all-auctions.com
harrison at all-auctions.com
Mon Dec 22 09:50:59 EST 2025
Hi Curry and Riko,
This is really terrible! I’ve never seen a company
want to cut it’s own throat this way before!
Under databases, I didn’t see support
for PostgreSQL specifically listed either,
and that really concerns me.
Seeing it in print makes users want to bail as
quickly as possible! I sure hope the people
at LC seriously reconsider what they are
doing immediately and change course!
Just my 2 cents for the day.
Rick
P.S. Here’s the link for those who haven’t seen it:
https://livecode.com/faq
> On Dec 22, 2025, at 4:13 AM, Riko Abadi via use-livecode <use-livecode at lists.runrev.com> wrote:
>
> This means already-built apps are permanently dependent on ongoing license
> renewal just to execute.
> That is highly unusual for developer tools and represents significant
> business, operational, and ethical risk.
>
> Industry-standard practice is that licenses are required to build or
> update, not for existing apps to keep running. Under the current terms,
> LiveCode Create is not a viable option for serious, long-lived applications.
>
> I hope LiveCode will reconsider this runtime licensing model.
>
> On Mon, Dec 22, 2025 at 3:46 AM Curry Kenworthy via use-livecode <
> use-livecode at lists.runrev.com> wrote:
>
>> LC Built Apps held Hostage, Runtime execution rent - looked at FAQ
>>
>> More perspective on a top concern -
>> Kill switch details; it's even worse than I remembered.
>>
>> "Apps require active [LiveCode Create] licensing to run.
>> If your license lapses, your apps will no longer be licensed
>> and they will not continue to run."
>>
>> Meet the LiveCode FAQ -
>> https://livecode.com/faq
>>
>> Built Apps - not 'continue' to run?
>>
>> This is unusual and high-risk for developer tools -
>> App execution is forever tied to ongoing LiveCode renewal.
>>
>> Runtime execution rent, ongoing = fragile Toy Apps.
>>
>> subject to renewal, whim, outage, billing, or glitch.
>> much more so than just using hosting or data.
>>
>> App Runtime hostage reality -
>>
>> Unethical for consulting/recommending;
>> Dangerous for business operations.
>> Careless for patients, charity, freeware.
>>
>> would I ever build Apps with Create under these terms?
>> not a chance. glad I looked again.
>>
>> but easy for LiveCode to fix if they choose;
>> LC recently requested my feedback to help them improve.
>>
>> What’s normal/standard -
>>
>> Dev tool licenses are required to build, compile, or deploy.
>> Lapsed licenses typically Disable updates, new builds, support ...
>>
>> but Existing, already-built apps keep running.
>> That’s why they are 'built' apps!
>>
>> huge step backward -
>>
>> I will not follow that wayward direction;
>> my future plans include robust apps and clear ethics.
>>
>> window is closing to fix LiveCode pricing/terms issues.
>> LiveCode Classic - '2027' end of life.
>> people have been retooling elsewhere.
>>
>> so ... hope this requested advice improves LiveCode Create.
>>
>> Happy Holy-days of Christ's Mass!
>>
>> Best wishes,
>>
>> Curry Kenworthy
>>
>> "Dominate documents with WordLib and LC"
>> https://livecodeaddons.com/wordlib.html
>>
>> (Still recuperating from illness - comments limited.)
>>
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
More information about the use-livecode
mailing list