Mobile project basics



Adobe® Device Central defines each mobile project in an XML project document that it saves in a file with the suffix .adcp. You use the Device Central Project menu and Project window to create and manage your projects.

Note: Device Central mobile projects have no relationship to Flash® projects or Mobile Application Builder projects.

    Elements of a project

    Device Central projects consist of three sets of elements:

    • Resource files, such as FLA, PNG, or SWF files, optionally structured into hierarchal folders

    • Devices, optionally structured into hierarchal device sets

    • Tasks that operate on selected members of the resource files

    Thus, for example, you can create and run a task that sends a set of resource files to an FTP server for distribution

    Project tasks

    Tasks perform actions using project contents. You create and use tasks to export project files to the following destinations:

    • Bluetooth mobile devices, typically for testing.

    • Directories, for example, for testing on non-Bluetooth devices.

    • FTP servers, typically for distribution.

    Tasks are especially useful for quickly publishing repeated versions of applications that contain multiple files and can run on multiple devices. Tasks help you quickly test the files and distribute the results.

    Why use projects

    Mobile projects can access all the files in a mobile application from a single interface. For example, you can open project resource files for editing in their native application by double clicking the file in the Resource Files list.

    Project resources are links to files and devices. Therefore, the project always reflects the current state of your resources. Most projects include FLA files and the corresponding compiled SWF files. Similarly, a project would include both source PSD files and distributable PNG files. When you update any file, the project accesses the updated file. For example, if you change and compile a FLA file, the FLA and SWF file entries in the Resource Files list automatically access the changed files.

    Mobile projects can automate tasks that you perform repeatedly. Suppose you frequently change a mobile application that uses PNG and SWF files. In this case, create a task that tests the files together on a Bluetooth device. This feature can be useful during the development process to test incremental changes many times each day.

    Mobile projects also ease application distribution. Sometimes, you distribute a set of files repeatedly. You can create a task that FTPs the files to the destination server, and run the task each time you update the server files. If you add files to the application, you only have to add the files to the saved task before you run it.

    Mobile projects ease the distribution of complex applications that have the following characteristics:

    • Include multiple files

    • Deploy on multiple device types

    • Require different sets of files for different device types

    You can place all files that are specific to a device or device type in a resource file folder. Similarly, you can group related devices with similar characteristics into a device set. You can also place all source files in a folder or folder tree. You can then create device-specific tasks, each of which uses sets of resource files that are required for a specific device type.

    Project workflow

    Mobile projects are flexible and can accommodate different workflows to meet varying needs. The following text describes only one possible flow.

    1. Use the New Document feature of Device Central to create device-specific source files in their authoring applications. For example, use the File > New Document In menu to create FLA files in Flash, PSD files in Photoshop®, or AI files in Illustrator®.

    2. In your authoring tool, convert source format files to distribution format files. For example, compile FLA files to SWF files, save PSD files in PNG format, and save AI files in SVG format.

    3. Test individual distribution format files in the Device Central Emulator and correct them as needed.

    4. Add the source and distribution files to your project. When you double-click a source file in the Project window, Device Central opens the corresponding editor.

      Note: Adobe Captivate users must publish final mobile SWF content in Adobe Captivate. (Device Central tests Captivate content by using temporary SWF files. Adobe Captivate support is available in Adobe Device Central 2.1.)
    5. In Device Central, create a set of folders, as follows:

      • Create common folders for any files that are used in many or all target device types.

      • Create device-specific folders for files that are used in only specific devices.

      • The specific structure can depend on your development standards and distribution methods.

    6. Add the files to the folders as needed.

    7. Add any additional files to your project, then structure your project by placing files in the appropriate folders.

    8. Add devices from the Device Central device libraries to the project Devices pane. You can add complete device sets from Device Central, or you can add individual devices and create project-specific device sets.

    9. Create device-type specific tasks for publishing your application.

    10. Publish the application to test devices.

    11. Run the application on the test devices and make any needed corrections to the application files and tasks.

    12. Repeat steps 11 and 12 as needed.

    13. Run your tasks to deploy your application or send it to a client for review.