Hello Alex,

Could you please send this email to [email protected] where I will be happy 
to help you.

Best Regards,

Heather

> On 16 Jan 2026, at 05:06, Alex Shaw via use-livecode 
> <[email protected]> wrote:
> 
> Hi Heather
> 
> Thanks for clarifying things re the current EULA.
> 
> Still think the functionaly kill switch should have been clear on the initial 
> launch site @ https://future.livecode.com/faq/
> 
> If I may, just a few questions linger for me.
> 
> Does this EULA and the end of application functionality apply to Classic or 
> Create apps that don't utilise any of the LiveCode-provided backend services?
> 
> Eg. If a devleoper happened to make the perfect little niche app for persoanl 
> use that didn't use any external services, will that also stop working if 
> subscription lapsed?
> 
> Re LC Classic, @ 
> https://legacy.livecode.com/resources/support/ask-a-question/ under "Do 
> Standalones created with the LiveCode Standard Plan expire?"
> 
> The stated answer is:
> 
>> No. Even if your LiveCode Standard Plan subscription is not renewed, any 
>> standalones you built with it will go on working indefinitely.
> 
> Does this only apply to Classic apps developed from LC version 9 and below?
> 
> Current FAQ @ https://livecode.com/faq states:
> 
>> You cannot buy LiveCode Classic on its own. You will receive a complimentary 
>> license to LiveCode Classic with a purchase of Create, while Create is still 
>> in beta.
> 
> Is that in relation to being able to switch between Create and Classic mode 
> in the DP releases? Because I can't seem to get LC10 activating anymore.
> 
> At just a little over 21 years, I am very much at the conclusion that my time 
> with Metacard/Livecode is ending but I'm wondering as a courtesy for many 
> years of support if it would be possible to get a license for LC9 to tidy up 
> some old fav little tools and compile executables that will last a few more 
> years?
> 
> The only accessible Classic license in my online account seems to be for 
> LC5.5, which is probaly too old to be useful on current machines.
> 
> regards
> alex
> 
> On 6/1/2026 2:08 am, Heather Laine via use-livecode wrote:
>> Dear Curry,
>> 
>> Thank you for taking the time to share your feedback, and Happy New Year to 
>> you.
>> 
>> We have reviewed your comments regarding the LiveCode Create EULA. The EULA 
>> is intentional, lawful, and reflects a licensing model that is standard and 
>> widely used across the modern software industry. It is neither immoral nor 
>> illegal.
>> 
>> To clarify a key point: continued use of any licensed software is contingent 
>> on that licence being valid and paid for. If a licence is not renewed or is 
>> materially breached, there is no reasonable expectation that access to the 
>> licensed platform—or services dependent upon it—should continue. This is a 
>> basic and accepted principle of commercial software licensing.
>> 
>> Apps built with LiveCode Create may optionally make use of LiveCode-provided 
>> services such as cloud hosting, backend infrastructure, and data services. 
>> These services incur ongoing operational costs for us. It would not be 
>> reasonable, or commercially viable, to expect LiveCode to continue providing 
>> such services indefinitely for applications that are no longer licensed or 
>> paying for those services. Similar provisions exist in the terms of most 
>> commercial development tools, SaaS platforms, and cloud-backed systems in 
>> use today.
>> 
>> The EULA will not be changed on the basis of this feedback.
>> 
>> Finally, please note that the use-livecode mailing list exists to help 
>> participants use the software effectively. It is not a forum for repeated 
>> accusations or attacks against LiveCode Ltd. We ask that discussion on the 
>> list remains on topic. If individuals have specific questions regarding 
>> their licence or require clarification on the EULA, I am always happy to 
>> address those directly through appropriate support channels.
>> 
>> You are, of course, free to decide whether LiveCode Create is suitable for 
>> your projects and risk profile, as with any other software tool. However, we 
>> do not agree with your characterisation of the licence, and we do not accept 
>> the conclusions you have drawn from it.
>> 
>> We consider this matter closed and do not intend to engage further on this 
>> point. Please refrain from reposting on this thread or using similar 
>> emotionally loaded language (bordering on slander in places) in respect of 
>> the company or the licensing we have chosen to employ.
>> 
>> Kind regards,
>> 
>> Heather
>> 
>> 
>> Heather Laine
>> Customer Services Manager
>> LiveCode Ltd
>> www.livecode.com
>> Build Software You'll Never Outgrow
>> 
>>> On 4 Jan 2026, at 23:23, Curry Kenworthy via use-livecode 
>>> <[email protected]> wrote:
>>> 
>>> Heriberto Torrado:
>>> 
>>>> I honestly don’t know how to help LiveCode Ltd.
>>> Yes - but luckily, it's so simple to help!
>>> Here's how. In the LiveCode Create EULA ...
>>> 
>>> Twin clauses, Extreme risk -
>>> 
>>> 8.2/3.3 Runtime kill switch = fragile Toy Apps.
>>> Instant disaster! Loss of built products and users.
>>> 
>>> 8.1 Blank check terms = legal/financial minefield.
>>> No protections; this can bankrupt or derail operations.
>>> 
>>> Kill built apps?
>>> 
>>> This is nuclear! Likewise Blank check.
>>> Not workable. Not safe. Not acceptable.
>>> 
>>> Remove those 2 - huge impact. More users and no downside.
>>> People have been retooling elsewhere; no choice.
>>> 
>>>> Because somewhere in the world, there is probably a child
>>>> who ... will discover LiveCode and realize that controlling
>>>> a computer and making the most of it can still be simple and fun.
>>> Exactly - And a child or adult/senior needs positive, safe discovery;
>>> Not a EULA gun to the head, with fragile Toy Apps!
>>> 
>>> Getting frustrated, harmed, or squeezed - that hurts everyone.
>>> No excuse for Runtime kill switch and Blank check terms.
>>> 
>>> No legitimate purpose -
>>> 
>>> You can't gain more HONEST money with a Blank check.
>>> You can't MORALLY or SAFELY leverage users with app kill switch.
>>> 
>>> I realized the giant risk; I use a custom AAC, etc! For handicap.
>>> Imagine that cut off - I'm sure some others in same boat.
>>> 
>>> Both are extreme and dangerous. I realized it would be immoral
>>> not to warn the rest of you! So I did.
>>> 
>>> Meet the LiveCode Create EULA -
>>> https://livecode.com/eula
>>> 
>>>> With the arrival of the Internet, large manufacturers such as
>>>> Microsoft and Apple pushed amateur programmers out of the ecosystem
>>> Not quite! Amateur programmers today benefit from an abundance
>>> of online resources and free tools. Just not the SAME tools.
>>> 
>>> Many dev tools do NOT require Internet login or any subscription.
>>> But we want the HyperCard style dream to expand, right? So ...
>>> 
>>> A real LiveCode EULA fix is needed; not emotional persuasion techniques,
>>> nor circular nostalgia exercises that lead away from any solution.
>>> 
>>>> What I am certain about is that LiveCode must continue.
>>> I hope for a fix; that is why I've donated my awareness effort
>>> in free public service here, not easy after long illness!
>>> 
>>> Not thinking only of myself, and some chance of retaliation.
>>> But I'm glad to speak up, because it's the only moral thing to do.
>>> 
>>> Opportunity -
>>> 
>>> LiveCode recently requested my feedback to help improve.
>>> Glad to help. Easy to fix, if LiveCode chooses.
>>> 
>>> Either way, the HyperCard dream will expand further -
>>> Among other dreams. Managing risk too, meanwhile.
>>> 
>>>> A hug to everyone, and Happy New Year!
>>> Thank you! Bright future / new year...
>>> 
>>> Best wishes,
>>> 
>>> Curry Kenworthy
>>> 
>>> _______________________________________________
>>> use-livecode mailing list
>>> [email protected]
>>> Please visit this url to subscribe, unsubscribe and manage your 
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>> _______________________________________________
>> use-livecode mailing list
>> [email protected]
>> Please visit this url to subscribe, unsubscribe and manage your subscription 
>> preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> 
> _______________________________________________
> use-livecode mailing list
> [email protected]
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to