ethanpil's Forum Posts

    Although I have no issue with the pricing of C3 if the platform is good (I think most people should wait to have the full feature list before complaining or not), I do have an idea that may be interesting.

    Ashley Why not adopt a model similar to that used by Xojo? See here: https://xojo.com/store/index.php

    You can develop for free on their platform, but when you want to export the final version, you need a license. They also have several levels of pricing depending on the export targets. This would allow people "playing around" with C3 to do so free of charge and anyone wanting to distribute their game would pay a fee according to the platforms they want to use.

    XOJO has the exact license model I proposed in my original post. Here is a quote from the FAQ at the bottom of the linked page:

    [quote:327u5xvo]How does a Xojo license subscription work?

    All new licenses allow access to Xojo updates for the next 12 months. After that, you can continue to use versions of Xojo that were released before your license expired indefinitely, and your apps continue to be yours to sell or share! To get access to new releases of Xojo for another 12 or 24 months, renew your license. Your Xojo license is set to auto-renew. Click here to adjust your auto-renew settings.

    You will still be able to use your offline version even if you don't plan to renew, but you won't be able to access the cloud services such as exporters etc...

    Other than that, they aren't changing the payment method.

    What I am suggesting is that you can continue to use the full versions of offline exporters and all other offline features that were in the last version one downloaded when the subscription was active. (The updates to these exporters and other new features would not be available because the new version would need an active subscription to download.)

    Tom and Ashley I would like to propose the following alternative or compromise to subscription pricing, which I think will allow Scirra to maintain a similar revenue stream to your original plan, while preventing the loss of many users who may defect at subscription only options:

    • $125 gets you the first year of Construct 3 access online / offline. Can use cloud any time or download offline versions and updates for 1 year.
    • If I choose to renew the subscription on or before expiration it will continue at $99 per year. If I don't renew then I will lose cloud access, but can still use the last offline version I downloaded while my "subscription" was active.
    • If I wait to renew more than 30 days after expiry, then it will again be $125 per year.

    With this pricing scheme, Scirra gets the benefits of a subscription model from those who see the value, but doesn't alienate the customers who can continue to use it without interruption and don't see the value in paying Scirra for updates. Additionally, the $125 vs $99 provides an incentive to maintain a subscription instead of renewing only when needed. Conversely, if I know I will be bust for 2 years, I can hold off and wait....

    Any thoughts?

    [quote:eta6mocx] won't say that, I think CSS styling is a great thing and gives you tons of options to make your forms look less like well, forms.

    Sure C2's one action per CSS styling isn't great and the language itself might require some research but I think it's better compared to the native alternative, which is using "sprite-forms" for the most part. (We also still have the option to use the great 3rd party CSS import plugin. )

    The issue isn't so much the simple HTML form elements, where, I agree, if it was only CSS needed we would be ok. What is missing and currently very difficult to implement are commnonly used higher level widgets like listview, toggle, silding, accordian, menu, etc.

    Ashley any chance of seeing some kind of extensible/skinable widget set for C3?

    Some of the competing platforms have already rolled this out, would make it easier to create UI for classical apps...

    I know we have HTML form inputs now, but they are not very skinnable or flexible, and certainly don't look native on any platform..

    I think to be useful, at minimum something like:

    • Button (with Icon)
    • Menu
    • Tab Bar
    • Date Picker
    • Listview
    • Slider
    • Spinner
    • Switch
    • Progress Bar
    • Input

    Any thoughts?

  • What I mean is how I can integrate it into a C2 game...

    1) How can I include NPM module in a C2 export?

    2) How can I access methods in NPM module with C2 interface?

  • Thanks for this wonderful and useful resource.

    Would love to see some detailed information and examples about using NPM modules in games

  • If I send out an update to the app over Google Play or iTunes, won't that result in the localstorage data being deleted? How can I securely maintain the localstoage over upgrades?

  • cranberrygame I have purchased this plugin from the Scirra store and it is not working today. Can you please provide a fixed version. I have compiled with phonegap build. Your barcode plugin works fine, but the camera will not.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • clarkkentnicdao I cannot activate the mobile camera with default plugins of C2. Does it work for you?

  • I cannot get default plugins to work with camera on mobile devices. I tried to compile with phonegap and it wont activate.

  • Regular plugins didn't activate my camera on PhoneGap

  • cranberrygame the Cordova Camera plugin isnt working.

    I also tested to see if file exists CordovaCamera.CameraPicture usnig the plugin and the result is false. Seems the app cannot read the saved file from the camera plugin.

  • After hours and hours, I have finally got the barcode plugin working on phonegap build.

    1) Must add to config.xml:

    <preference name="android-build-tool" value="gradle" />

    2) must edit the plugin text and remove spec="2.0.0"

    change this: <plugin name="com.phonegap.plugins.barcodescanner" spec="2.0.0" source="npm" />

    to this: <plugin name="com.phonegap.plugins.barcodescanner" source="npm" />

    How can we fix the plugin to automatically do this for all future builds?