How about free until a certain limit then paid?
How have I not noticed this plugin before…? I agree with others that this seems like something that is amazingly useful for anyone releasing builds on the stores. There’s nothing worse that rolling out a build to 100% of users, only to find that there is a typo somewhere that was missed during testing and crashes the app for most people.
I actually thought it was 100% against both stores terms to use non-embedded script in an app, so I’m glad that is not the case (unless you completely change the app’s behaviour of course).
I’m assuming that there is no way to have the plugin read encrypted script files to make them less user-readable? I know that ultimately if someone is determined to crack your code they’ll find a way, but it’s still nice to make them work for it if possible 
Alan,
encrypted (pre-compiled?)
When you say encrypted, do you mean pre-compiled? If so, then there should be no problem reading compiled scripts as long as you compile them using the scripts for Corona plugin making. I do this all the time when demoing to clients. i.e. I pre-compile key scripts then send them a zip of the project demo.
Rules, rules, rules
For the longest time it was against the rules for the iOS store. Since Swift took off however, they seem to have loosened up the rules a bit. So, I say, do it, but with caution and as you say, don’t change the behavior of your app, just fix bugs and add minor features.
What about free and paid version?
The free version helps to decide that the paid version (with more functionality) actually needed for the end user or not.
…
I have a question about the patcher plugin.
What do you mean about last paragraphs at the end of this article?
https://www.theregister.co.uk/2017/06/07/apple_relaxes_developer_rules/
Janos
Thanks for the feedback.
- There is no way I can make a free and paid version. i.e. If it is free, there is no reasonable way to add code that forces folks to pay for it in production games and apps. Also, reducing functionality would simply make it not work.
Please note, my plan, if I were to release it free, was to release the source code which is pure lua.
- Be aware, I didn’t write the article. Are you referring to this long sentence?
“The change does seem to loosen the requirement on downloaded code, specifically around the framework and language of the downloaded interpreted code, which means that other scripting languages not using Javascript language are allowed for injection, such as Lua, RubyMotion, and the like.”
If so, I assume it is saying, you can do essentially what this plugin lets you do. Download Lua code and execute it.
If not, please quote specifically what you are asking about and I’ll try to answer/clarify.
Everyone - Please be aware this is settled. The suggestions are predominantly that I not do anything and leave the products as paid.
This is the easiest plan for me and I’m happy to do that.
thank you
Both 1. and 2. is clear.