As we are separate products/companies, we can only accept this situation although we can assure all of you that we have tried to reverse this situation many times. We are trying to improve our support to the Construct2 community, we have offered to meet with the Scirra team many times to talk and improve the Canvas+ support and even provide some solutions to some problems that they have refused to implement.
it's really sad to hear this. But it seems like a matter of Ashley belief: he believes that Crosswalk is better (even if NOW it is not better) so he just don't care about real people experiences. He says: You can make big game with Crosswalk. But in reality you can't make serious, big game with Crosswalk due to it's many issues. Or you can make big game and then feel shame because of it's terrible framerate.
He is not making any games recently, so he doesn't know this feeling: smooth in CocoonJS Canvas+, slow in Crosswalk.
[quote:1gruuiwg]We would also like to comment that having the export to CocoonJS as a paid option was a unilateral decision from Scirra and we never saw a penny out of it (and never asked for a penny). We think it is not fair to blame for money returns for a product that we offer for free to the Construct2 developers.
Exactly.
[quote:1gruuiwg]We are trying that these modifications do not have to do with Canvas+ as much as we can, and be more related to mobile restrictions, but sometimes it is nearly impossible and minor modifications (one or two lines most of the times) on Construct2 would solve the issue instantly.
+1