iOS Apps Update Model - Trigger
chipp at chipp.com
Thu Dec 9 18:55:40 EST 2010
There are several advantages to using the StackRunner (I'm calling it
AltRunner ;-P) concept:
1. I can program stacks on my PC instead of having to use a Mac
2. I can provision the exact same AltRunner client for different
customers, and give them different links, and they will be running a
completely different application. So, I only need to mess with Apples PIA
3. I can beta test products faster.
4. I can update my applications instantaneously, instead of the
ridiculous 2 to 4 day update process Apple uses.
5. I can load several different apps onto the AltRunner desktop, and run
any of them individually.
On Thu, Dec 9, 2010 at 5:17 PM, Chipp Walters <chipp at chipp.com> wrote:
> Yes, I believe that is the case for commercial development.
> FWIW, I am working on an iOS 'StackRunner" which works on iPhone and iPad.
> With it, you can provision your enterprise customers, and then they can
> download stacks directly to their device by entering in a stack URL. When
> complete, it will show an icon for every stack you've downloaded, along with
> a file browser to update or delete the stacks and their contents.
> I've currently got it downloading stacks to both iPad and iPhone. I'm
> planning on making this part of the presentation Andre and I will be giving
> at the LiveCode conference later next year.
> On Thu, Dec 9, 2010 at 3:40 PM, Sivakatirswami <katir at hindu.org> wrote:
>> Can anyone share the update requirements for iOS Apps?
>> Do we simply change that in our standalone settings push a new version and
>> then the App store alerts all users?
>> anything else we need to know?
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
> Chipp Walters
> CEO, Shafer Walters Group, Inc.
CEO, Shafer Walters Group, Inc.
More information about the Use-livecode