Comments on: Taking Corona SDK to the Next Level

By: PAF #2 Show and tell | Potato Life

PAF #2 Show and tell | Potato Life — Tue, 27 Aug 2013 05:10:59 +0000

[…] This postÂ probably sums up much of the problems with the SDK itself and provides suggestions for a way forward from someone who has been using the SDK extensively. At the end of it, my feeling is if I needed to write something that would work on iOS and Android quickly, I would probably go with Corona today. If I only needed to support Android, I would probably go with a native Java stack. […]

By: David Rangel

David Rangel — Tue, 13 Aug 2013 13:42:12 +0000

Jesse – we saw your post a while back and discussed it internally. I just realized we never posted here, so doing it now. THANK YOU very much for taking the time to write this. We really appreciate it. This is all fantastic feedback and we are paying attention. Of course, as you clearly realize, this is a ton of work :) But we plan on getting there.

Of course, feel free to email us any time. My email (which I think you have) is david AT coronalabs

By: Rob

Rob — Sat, 13 Jul 2013 06:45:16 +0000

well argued sir.

By: Rob Vermeulen

Rob Vermeulen — Wed, 10 Jul 2013 10:37:29 +0000

Good ideas and well explained. But since this is sooo much work, I think it will never get there.
I’m a b2b app developer, using Windows and I continuously struggle with the simulator not being able to display the native widgets. This is really frustrating as testing on a device takes 10x longer and there’s no debugging :(

I’m looking at other high level SDK’s but can’t find one that appeals to me. I dislike web tech (Javascript, HTML5, CSS).

Any suggestions?

By: Jen Looper

Jen Looper — Tue, 09 Jul 2013 03:03:51 +0000

So much here it’s almost TLDR :) but I’ll just note that WRT components/widgets, I am not sure the Corona folks look at the framework for building utility apps. Which is a shame b/c that’s really where the consulting money is, not so much for games. +1 and 100% agree we need a Sencha-style MVC framework. Been saying that for a long time, and I feel that junior devs can get into some really bad habits as coders if they cram everything into main.lua. Regarding language choice, I think the investment in lua is very profound, but allowing authoring in a diverse set of languages is an interesting idea. In my survey of devs at the Boston Festival of Indie Games last year, almost everyone was writing in C-something.
Really interesting and good ideas :)