Last week Corona Labs announced their new tool, yet in a beta stage, called Composer GUI (graphics user interface), which is pretty cool, by the way. If you haven’t seen it, check their blog.
Minutes later, I received an email from a Kwik user asking about how it would change Kwik’s positioning for the future. You can read about my entire thoughts below but, in a few words, I would like to say that Composer GUI targets a different audience than Kwik. To clarify that, I decided to make a homage to Corona Labs, reproducing their demo in Kwik. See and take your own conclusions:
A Threat Or An Opportunity?
First of all, I believe is too early to say how good Composer GUI will become. As Walter said in his posting, it is in an early beta stage at this moment. So, my words here may not be valid in a short term. Also, I don’t think it is a threat to Kwik or ANY OTHER Corona plugin. A competitor? Maybe. But not a threat. Having worked for so many years at Microsoft in the Office group, I’ve learned that competition pushes you forward to improve your products and expand your markets. Indeed some users may find better to move from Kwik to Composer. However, these are the reasons I see Composer GUI as an opportunity to Kwiksher:
- At this moment Composer GUI is just available for Corona PRO users. It is not clear yet if Corona Labs will bring it to all Starter and Basic users in a near term. Fact is, 90% of Kwik users are on Corona SDK Starter;
- Composer GUI feature set is very limited right now, comparing what you can do in Kwik. While Composer can handles linear animations, physics and positioning, Kwik can create full code, with several pre-made interactions.
- Composer mostly targets developers willing to create levels and speeding up scene compositions. Kwik targets Photoshop users willing to create their own products without (or with limited) external code. Again, 90% of Kwik users are not developers;
- Composer requires pre-made assets (images with different resolutions, previously created in tools like Photoshop or other image editors), then it requires repositioning of all scene elements. Kwik does this part of the job as well, just with a click of button;
I do see opportunities for Kwiksher in:
- Providing a tool that exports Photoshop compositions directly to Composer GUI (think Kutt on steroids). This would target designers working with developers, but not willing to create full apps with Kwik;
Something like Composer GUI for Photoshop, where the plugin could create/read/update composer projects. A strip down version of Kwik, for example, only with features for Composer users;
Or Composer GUI PRO for Photoshop, something like the full Kwik (doing much more than Composer) integrated with Composer GUI.
Again, these ideas may never come up but, I am just trying to make a point that Corona and Kwiksher can (and probably will) continuously work together to provide the best tools for every audience we can capture. Where some see crisis, we see opportunities.
What do you think?