Is the code generated so far suitable for mobile applications??

You need to read previous chapters in order to understand this article.

-

In this tutorial we used Flash Catalyst to create custom components and convert the Illustrator layout into several native components (Scrollbar, DataList, TextInput, ScrollPanel).
We also included transitions and interactions trying also to optimize the MXML code generated by Catalyst for it to be of good quality and well structured, dividing the application into different components.

Although, as we saw, Flash Catalyst can be used to create prototypes or even complete web sites and applications, from my point of view, the biggest advantage of using this software is that you can easily skin individual components to reuse in Flash Builder.
We will see in a future tutorial how to use this code in Flash Builder.

MOBILE APPLICATIONS IN CATALYST?

From the Flex SDK 4.5 you can create mobile applications for Android, BlackBerry and IOS devices.

Although the MXML code generated by Catalyst can be used in mobile applications to skin components or create application Views, the project we developed in this tutorial is not suitable for this purpose. Here are some considerations:

• First, the newer versions of Flex include components and themes for mobile applications.
  So, often you won’t need to use Flash Catalyst to skin components such as the scrollbar or input fields because you will already use the default assets.
• ItemRenderers generated by Flash Catalyst DataList components are not optimized for mobile devices and the performance might be affected significantly. Currently, in mobile Flex applications, List-based components should only use the default itemRenderer available in the Flex SDK 4.5 or higher that are optimized for mobile devices or, alternatively, create itemRenderers entirely in ActionScript 3.0.
• Flex 4 Burrito provides the ability to create Mobile Projects that already manage the ActionBar and Application Views through specific classes.
  As a result, the code generated by Catalyst although still useful for implementing custom graphics, will require some manual changes to be integrated into a Flex project Mobile.

-
WHERE TO GO FROM HERE

• Getting started with Adobe Flash Catalyst CS5
• Adobe Flash Catalyst CS5 best practices
• Introducing Adobe Flash Catalyst “Panini
• Building a data-centric application using Flash Catalyst CS5 and Flash Builder 4
• Flash Builder and Flash Catalyst Designer/Developer Workflow
• Mobile development using Adobe Flex SDK “Hero” and Flash Builder “Burrito”

-
RELATED ENTRIES

• Optimizing MXML code in Flash Catalyst “Panini” - Introduction
• Optimizing MXML code in Flash Catalyst “Panini” - Part 1 - From Illustrator to Catalyst
• Optimizing MXML code in Flash Catalyst “Panini” - Part 2 - CUSTOM/GENERIC COMPONENTS
• Optimizing MXML code in Flash Catalyst “Panini” - Part 3 - Vertical Scrollbar component
• Optimizing MXML code in Flash Catalyst “Panini” - Part 4 - DataList component
• Optimizing MXML code in Flash Catalyst “Panini” - Part 5 - ScrollPanel component
• Optimizing MXML code in Flash Catalyst “Panini” - Part 6 - Interactions and Transitions
• Optimizing MXML code in Flash Catalyst “Panini” - Part 7 - Text Input component
• Optimizing MXML code in Flash Catalyst “Panini” - Part 8 - MXML Code optimization
• Optimizing MXML code in Flash Catalyst “Panini” - Part 9 - Develop Mobile apps with Catalyst? (this)