Great to hear your plans Vlad. I will support your Patreon for you and hopefully Rob. Since the 2 of you have been doing nearly all the work on Corona for sometime now, I see no reason Corona will not be able to go on and thrive as long as enough of us support thru Patreon or even a monthly/yearly membership fee. I feel better now, after hearing from you.
So we are getting offline builds, splash screen removal for free, open source, Appodeal paying for the transition, Vlad and (I hope) Rob positive to keep working on Corona (the product).
The most important for me, is having on board two guys who are capable and love their work.
And all we have to do is to be supportive and give some money (imho it will happen).
I can hear the good plan of vlads after getting up. I am very excited. Your professionalism in the forum has always helped us developers a lot.
I use both corona (for the main build) and unity (for the production of objects), and I have to say that Corona is really easy to deal with everything.
Although I was scared yesterday about Corona’s future, I will continue to live with Corona in the future.
Finally, I will actually support the Patreon project and hope that all Corona partners will together.
I was also looking into other Lua based engines - no more, after Vlad’s reply. I am a hobbyist, but I’ll pay my share every year to be able to use Corona.
Thanks for the clarification, Vlad.
I have a Corona game generating significant income, so I’ll be able to contribute monthly when Patreon is set up. Much more than what I’m paying with plugins right now.
I think we should be optimistic, many engines have thrived with open source systems. And if we can’t keep Corona forever, then we should make it last as long as possible.
A break down on iOS would be catastrophic for me and the combined losses between developers would literally be in the millions.
After hearing Vlad’s words I felt calmer and I have a hope about the future of Corona, we as developers must assume the commitment to make a financial contribution to keep Corona alive, it is fair, especially those who earn money and It is our business as a way of life.
(sorry for my horrible English, )
I do not know that so much income ($) is currently obtained by disabling the “Corona splash screen”, but it seems good (very fair) to pay for it. At least I have been paying for it a couple of years ago.
Perhaps publish a free version of Corona SDK type “Community” with “Corona Splash Screen”, and another Version type “PRO” or “Membership” (annual payment, USD 99 today) without “Corona sdk splash screen”.
It’s just an idea, maybe the value should be less to have more participants … That’s part of the discussion.
Vlad sounds like he has a good plan and knows what needs to be done to keep Corona not just alive, but thriving.
We (RosiMosi LLC) will be contributing nicely to his GitHub sponsorship once his contract with Corona Labs ends. I also had the idea of some of the bigger developers doing a match of their own (up to a limit) which combined with GitHubs would essentially quadruple donations.
You have been able to build your own ad plugins if you used Corona Native (formerly Enterprise). If you really needed the simulator, there was Self-Hosted plugins. The only restriction was we would not let you put free ad plugins up in the Marketplace. I think there may have been a restriction at one point about building plugins that Corona already had, but I’m pretty sure that got lifted some time ago.
But for certain, going forward that’s not going to be a restriction.
I have used Corona SDK since it’s inception. Majority of my apps were Corona and it feels good reading the positive feedback form Vlad and all support of the community in the continuity of Corona’s future.
In the end, it seems that enthusiasm wins over anxiety! Let’s hope this reaction lasts over time.
Like many people here, I am ready to help the transition phase.
@Vlads@Rob: What can we do to help in concrete terms?
Perhaps you could list the real needs (hosting, development, documentation, etc.): I am sure that many resources are available among community members.
It’s too early in the process to really gauge what resources are needed with regards to hosting and such.
Documentation is currently tied to our expensive infrastructure and build process. At some point it would probably be helpful for us to put that repo up on GitHub if it’s not there already. It’s all markdown. Once we decide where we will host it, documentation will probably need to move to a different system and help porting it would probably be welcome.
You can get started on the development side today. The open source is already in GitHub. You can start familiarizing yourself with it. Learn how to pull it down, build and test things and generate pull requests. There is quite a bit of Lua in the core (widgets, timers, transitions, etc.) Widgets need a lot of love, so that is an area where any Corona developer can pitch in now.
Does this mean that the admob plugin will no longer be updated?
No, that doesn’t mean that at all. The Appodeal plugin is separate. They will continue to work with Vlad to make sure we ave the latest version of the Appodeal SDK to work with and since they are funding the infrastructure, we will continue to make sure the Appodeal plugin works. Now Appodeal includes AdMob as one of it’s mediated source. Appodeal would appreciate more developers integrating the plugin. It’s a win for everyone.
Are ads still being served with the admob plugin?
It’s working well with the exception of Rewarded Video and that issue may only be on one platform. We can’t update it until we implement Android X and as Vlad mentioned above it is one of his top priorities after we complete the offline builds and address Apple’s OpenGL deprecation.
I couldn’t agree more. I’ve used several engines and libraries and Corona’s documentation is simply top notch. Its readability and ease of navigation, visual style, the aforementioned examples, gotchas and everything. There’s not really all that much to improve in my opinion apart from fixing some odd typos or such that occasionally come up or adding new features when they are added.