[not quite OT] Serving a standalone

[William Prothero]

Richard and Kay:
Thanks for the stimulating thoughts.

Each of your arguments are very persuasive. And it seems that the most important thing is where you decide to start. If you focus is on mobile, Kay’s approach is the most sensible. I like Richard’s for desktop, but would expect to have to modify it to get it on iOS.

Re-iterating the two approaches:
1. Make iOs apps and create enhancements, like say “myApp basic”, “myApp Plus”, “myApp Pro”, etc. This means you would probably have a bunch of apps in the store with a common code part and a specialized part.
2. Make desktop app with Splash system, like Richard uses. Later, going to iOS would mean combining bits of the various pieces that get downloaded by the Splash app into a single app for iOS, and eliminating features unacceptable to Apple.

One factor is that going the iOS/App store route, you don’t know anything about your customers. I’m interested in educational apps that might be used in colleges, high schools, maybe even middle schools. I would really like to know my users. Of course, I could have a Facebook page where folks might log in and express their ideas, but… hmmm…..

But, it sounds to me like taking a bunch of pieces from a system like Richard describes and combining them into an iOS app might be a reasonable way to start. I would have to carefully structure it so features that wouldn’t be acceptable to Apple could be broken out easily. Just thinking. One of the pieces I plan on involves online writing and peer review. This part might not be so attractive on an iPad and certainly not on an iPhone.

Bill

> On Feb 8, 2015, at 5:17 PM, Kay C Lan <lan.kc.macmail at gmail.com> wrote:
> 
> On Mon, Feb 9, 2015 at 5:59 AM, Richard Gaskin <ambassador at fourthworld.com>
> wrote:
> 
>> With LiveCode we can do the same by merely extending the "anchor window"
>> (or "splash stack") setup to open stacks from URLs rather than local files:
>> 
>>  go url "http://yourdomain/stacks/stackfile.livecode"
>> 
>> And if you MUST cater for a school full of iPads (the school my wife
> works at is ALL Apple) how does that work? If you wanted to live the LC
> dream of code once and deploy Linux, Win, OS X and iOS what approach would
> you take? Now it's naive to think that you can really code once, there will
> always be some platform dependant code, but if you wanted to keep this at a
> minimum, so that your MVC for each platform was as close to identical as
> possible, how would you go about that?
> 
> The statisticians may say 8%, or what about the 85%, but all those figures
> are irrelevant if the first question you are asked walking through the door
> is 'can you write an iOS app' and the first requirement you are given is
> 'it MUST work on iPad'. What would your approach be if your primary goal
> was to build an iOS app and as an after thought you decide it would be
> sensible to make it cross platform but with as little additional code as
> possible?
> _______________________________________________
> 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