It’s water under the bridge, but in retrospect I think the proper way for Livecode to have structured their business was to have 3 products: Livecode Desktop, Livecode Mobile and Livecode Web. Each product should have maintained their own revenue stream unbound and unburdened by the other two. As it is, any financial burden developing for Mobile or Web is shared by Desktop. If one fails, all fail.
I also think that the Non-Commercial version we used to have (as much as I took advantage of it) was a bad idea. Give people something for free that they would otherwise have to pay for, guess what? They will use the free thing. Finally, I think that Livecode, much like Now Software of the past, overextended themselves. Now Software tried to develop a new product from the ground up and learned what all developers learn: It’s REALLY HARD to do. Livecode attempted to incorporate what I would consider to be niche technologies, so their resources have become much diluted. The native compiler project is dead I assume. Mobile is probably sucking resources from other things because it seems like every other week iOS or Android are making prior builds obsolete by their incessant changes. V10 has taken how many years to produce? Don’t get me started on Artificial Intelligence!! And I don’t NEED a no-code way to develop apps. I LIKE CODING!! All I ever wanted was to create utility apps to make my life and my job easier. That is it. I don’t need the bells and whistles, but I have been investing in those all these years just to keep desktop deveopment alive. Now I will not be able to afford developing for just the 3 internal users I have, and approaching my employer to incorporate my applipaction throughout the company is dead in the water. Thank GOD I didn’t already do so! So by whenever in 2027 this awesome party ends, I will likely bid farewell to you all and consider abandoning my development hobby completely. It feels like I have been given 2 years to live. Bob S On Jul 25, 2024, at 9:30 AM, William Prothero via use-livecode <use-livecode@lists.runrev.com> wrote: I second Graham's comment about apple's requirements for getting an app to work on the iphone are a huge pita. Bill William A. Prothero, PhD Prof Emeritus, Dept of Earth Science University of California, Santa Barbara On Jul 25, 2024, at 7:31 AM, Graham Samuel via use-livecode <use-livecode@lists.runrev.com<mailto:use-livecode@lists.runrev.com>> wrote: I’m in roughly the same position as Bill. Long ago I wrote Livecode apps for sale, but in the last several years I’ve just written a few personal apps, and have more or less stopped work, due mostly to old age. However I don’t like to say I’ve entirely given up as a hobbyist, and I was thinking of revisiting an app idea I had at the time of the pandemic - so I’m glad of Kevin’s reply. At present I’m thinking about iOS apps and wonder how much help from Create I will get for deployment - obeying all of Apple’s rules for the publication of an app (even a free one) into the public space. For me this part of app development proved far more of a PITA than the actual coding, and I know I will always need all the help I can get on this aspect. Maybe I missed it, but I am not clear what Create will offer. My other use of Livecode scripting has been to use it as “IYSWIM” (“if you see what I mean”) modelling tool, where I get the logic straight before plunging into a relatively hostile coding environment (think the Apple Watch, which will never be covered by Livecode in any form). As far as I can see, I will be able to go on using versions of Classic for this, even if the become outdated over time. I’m glad about this. Best Graham _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
