I feel I should point out that this quote seems to be the only mention of open source, it doesn’t seem to be mentioned on the resources you link to either (also you don’t seem to have asked any questions, at least in the current version of your OP?) Is the project open source? And if so what do you mean by that, is it say MIT/BSD licensed, or GPL, or is it dual licensed so authors choose between paying a fee to distribute their games closed source or distributing them open source along with say your GPL code? The intention is unclear to me… can we for example see the Java source for the Android app?
On Texture you note that it requires an Internet connection yet I believe the games can be downloaded as HTML files and presumably could be packaged using say Phonegap to run as Android and iOS apps. I suspect that Texture is a simpler system that your own with less scripting ability, however your “summary for version 1” sounds more like what little I know of Twine, which like Texture is also web based, in that it uses client side web technologies (HTML, CSS and Javascript to run).
I am curious what you mean by “You have a range of devices that wont work (properly) with javascript.” especially as it seems the demands of an “expression interpreter to evaluate logical and mathematical expressions” would be rather basic, and it looks like you are depending on a WebView for rendering your layouts. What devices have such poor Javascript support that they can’t handle simple expressions? (I actually want to know btw; I understand there are limitations when it comes to newer HTML5 features, especially pre-Android 4.3, but the devices with really poor support, must be in a tiny minority which is ever shrinking as devices get dropped or traded in for newer, better models) Without further explanation it just sounds like you don’t like certain technologies, which is fine, it’s just that’s different to claiming nebulous problems (you mention wanting to be “native” but your screenshots look no more native then HTML running in a webview).
With the suggestion “I will release the first version of the editor in the playstore for free and ask for donations if you find it useful or like to see further development.” I see that as being rather a tough sell over an open source, well established Twine 2 backed by an existing community. Not least because while an author might have some pain to use say Phonegap to publish a Twine story on iOS and Android, the author knows that their story won’t die even if Twine’s community (not a single person) were to vanish; it would seem with your system the author is dependent on your app for their work to live on, and they have to trust that you will neither release changes that will break thier story nor change the terms that make that app available to end users in order that those users can play the author’s story (I myself am new to the community but I have noted concern over format support is a real issue - authors want their stories to be available for the long term and it seems that they have seen many authoring systems/formats)
I do think it’s great that you have solved a problem for yourself, I just feel you have shared less information about your intentions in this thread than your replies seem to suggest you feel you have, and from what you’ve actually mentioned it seems premature to ask people to buy into this idea. I’m sure there is room for alternatives for authoring choice based games, but it just seems like you dismiss the existing solutions too flippantly, and the people trying to help you too callously, for this to be worth much attention in my humble opinion.