Thursday, October 6, 2011

Flex Without Frameworks

I have used the Swiz and Mate frameworks for Flex development, as well as an injection-framework of my own devising, and now worry about their use for applications that run on minimal-memory devices like phones and pads.  The libraries take up extra space and the benefits, such as making it "easier" to develop complex applications, not so applicable.

I like to use the presentation model in Web and Air applications but do I need that complexity for Android and IPhone apps?  And what about abstract classes and multiple-inheritance through interfaces?

A lot of apps are so "simple" in flow that having components dispatch events that are handled by their parent screens seems are lot more efficient in development terms.  Efficient in requiring less code and creating no more debugging.

To resolve these conflicts, I intend to develop an application for multiple devices and then re-factor it for the popular frameworks.
  

No comments:

Post a Comment