Standalones on el Capitan?

Sannyasin Brahmanathaswami brahma at hindu.org
Sun May 1 22:29:54 EDT 2016


From 2013…

http://www.slideshare.net/techahead/html5-vs-native-app-battle-infographics


But still interesting. The “code once run anywhere” vs “Native dev”  is the underlying driving force behind HMTL5 app dev. 

So if you can sell LiveCode by marketing that same line… you can target an entire segment of users who can’t, or just don’t want to, eat the JS learning curve. They either hit the wall 

“too complicated for me!  Days and days to get the smallest thing done!”
OR
“I have better ways to use my brain than labor over JS and this xTalk is just too fun/productive…”

I have young people, doing silly things with online tools like “Scratch” and it would take very, very little to push them over to LiveCode… once hooked they will look at Javascript as arcane and painful.

But if iOS is off the plate. Then that pitch doesn’t work. 

Yes, Monte, that is an “Apple Problem” but we live in a contingent (unless you believe Kafka and Sartre, which I don’t)  universe, so… one has to adjust…or lose the game.

BR 



On 5/1/16, 2:44 PM, "use-livecode on behalf of EED-wp Email" <use-livecode-bounces at lists.runrev.com on behalf of prothero at earthednet.org> wrote:

>Any market researchers out there who could actually begin to answer this? 
>Bill
>
>William Prothero
>http://ed.earthednet.org
>
>> On May 1, 2016, at 4:23 PM, Alex Tweedly <alex at tweedly.net> wrote:
>> 
>> No, it's not an Apple problem - they're not losing any money over it, and they're certainly not losing any sleep over it.
>> 
>> I think it's a Livecode Ltd problem (for the reasons described in the earlier post), though it is partly caused by Apple.
>> 
>> Yeah. it would be great if Livecode Ltd could use the Community version to allow folks to publish GPL apps, and it is Apple that prevents them.
>> But I'm sure that's not the only possible solution - and Livecode Ltd should find, or consider, some of the others.
>> 
>> For example, would it be possible to create a version of that allows building IOS standalones under commercial license, but nothing else. Then such a User could build IOS standalones (non-GPL), other standalones (under GPL), they could NOT distribute or use encrypted stacks, etc.
>> 
>> And if necessary license that version for $5 per year :-)
>> 
>> -- Alex.
>> 
>> 
>> On 02/05/2016 00:04, Monte Goulding wrote:
>>>> On 2 May 2016, at 8:46 AM, Sannyasin Brahmanathaswami <brahma at hindu.org> wrote:
>>>> 
>>>> Forgive me, Monte.. But I think this is an extremely “blinkered” regressive point of view that seriously limits the possible future user base. The “middle ground” is not small at all. The digital revolution is *exploding* faster than anyone can possibly comprehend. In our very small world wide membership… I can’t count how many young boys and girls would jump on LiveCode if I put them onto it…
>>> With all due respect what you are complaining about is an Apple problem not a LiveCode problem. I actually think Apple’s position on GPL should be tested again now that they have free provisioning profiles.
>>> 
>>> Cheers
>>> 
>>> Monte
>>> _______________________________________________
>>> 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
>
>
>_______________________________________________
>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