Hi Clint,

The best way to handle this is for your customer to sign up to a publishing membership, but at the same time you could also submit the app to us by signing up yourself to a publishing membership, it's totally up to you.  

Basically once the app is submitted from the InteractBuilder we compile it and submit it to the app stores. If you want to use your own developer account we can transfer the app to your account or your customers account once we get it submitted.

As far as using our app, please watch our numerous videos, or look through our user guide to learn all about our software.  Our YouTube channel is: www.youtube.com/interactstudios.  You can download our software for free at: www.interactbuilder.com.

That's fantastic Ann!  I'm glad that helped.

This would be extremely difficult for us to do Serge (at least at this time). You could put a timer on the page and use the Timer conditions to determine if the action set should run.  There might be another way to handle this, I will give it some more thought.

Version 3.2 is coming out with an updated Player.  This will resolve any issues such as the one you have reported here.   The new version of InteractPlayer for iOS devices should be available within the next couple of weeks assuming Apple can get their developer site back up and running (we are on day 8 of them being down).

Actually most of the examples that you are mentioning can be implemented using the current software.  I think it would be a good idea for us to create some samples of these to show the community how this works. I will ask my team to work on some samples.

The new InteractPlayer that will be released in the next couple of weeks will mimic the builder and shares the exact same engine.

This actually looks like the program is having an issue updating the database.  You have an apostrophe somewhere that is causing the error.  Do you have a text element with an apostrophe, or maybe the title of your app. Obviously we don't want to prevent the usage of apostrophes, but that is what is causing the error. If you can narrow down for us where you have the apostrophe, we should be able to correct the error in the next update.

This is definitely on our roadmap.