I stumbled upon flex/air technology during work for a big french newspaper.
They needed a client app, for its reporters and editors, so they can edit those articles with some strict guidelines, and then send them to a server. Also they needed history.

Well, on normal basis, this can be doen fairly easy in PHP technology (or other web dev techs), by building a server app, putting an administration tool, and accessing it in web browser. Editors could use it very well, its a tested and proven concept.

But, what if you need to work offline ? and then sync with the server ?
Well the decision was made to use an AIR app on the client’s computer, that can connect to the server and sync.

I was building the server side (php), with a known framework. Once the AIR dev gone to holyday, i needed to step into the AIR/FLEX development to continue his work.

First impressions: AIR/FLEX is quite in impressive tools, with lots of functionalities, and many ease-up tools that can make your life easier. But also, regardin the OOP part, from my point of view, it still has some isssues to deal with. In AIR you can build your app as with an MVC pattern, so transitioning from php or ruby, is done realy ease, in terms of architecture.

Many scopes are quite visible (as i was startled at first).

So i continued building this desktop app (AIR/FLEX), the server as PHP, and communicating between those 2, there is a good php library using a AMF style, that eases the transformations, and data, and can easily support securizing it.

AMF = concept that allows flash apps to connect directly to server class objects.

I still do not know the memory implications of this tech, of course i cannot compare it to MS MFC, or MS C in Win, or Native C in Unix, but as an all-platform programming technique, i believe is quite productive.

Will continue doing that, plus the need for knowledge is still great.

[related-links]