Kannopy, Inc. is a Rich Internet Application development company focused on the development of applications built for the Adobe AIR runtime. Kannopy was initially started by Sean Moore as “Sean the Flash / Flex Guy” doing freelance development in late 2006. In January 2008 Sean incorporated and Kannopy, Inc. was born. Kannopy has worked on Flash, Flex and AIR applications for the entertainment, health care, commercial real estate, banking and education industries. The types of applications so far have been: kiosks, inventory management, point of sale, social networking/web 2.0 and chat. In addition to development Sean has been heavily involved in technical authoring and reviewing. He's also given presentations and contributed many projects and ActionScript source code to the Flash/Flex community.

Kannopy specializes in Adobe AIR development but also provides Flex development for browser based applications including BlazeDS enabled apps.

Kannopy prefers to work hands on with small to mid-sized businesses. Onsite development and consultation is an option, please contact to discuss rates and availability.

Flex best practices: Part 2: Development practices

Following best practices during the development process can help organize and structure an application. Standardized development provides clarity, stability, longevity and salability. I worked with several members of the Flex community and the Adobe Flex Team to create this article outlining over 90 best practices for the Flex development process. Thank you to everyone who helped review the article. Also thanks to everyone who provided input!! And, thanks to Adobe for the opportunity to write this!!!

Here is a short passage from the article:

“In this article, you will learn how to manage assets so that your application's dependencies will be well organized. I will also discuss widely accepted ActionScript 3.0, MXML, and CSS coding standards currently being practiced by the Flex development community. I'll review ASDoc, a tool that you can use to create API language reference documentation as HTML from your application's source code. In the application architecture section of this article I'll show techniques that you can use to help define the blueprints for your application's foundation.”