Adobe AIR Developer Experience Conclusion

Adobe AIR Development

After a day of experimenting with what it’s like to develop a BlackBerry® 10 application for the first time, the team here in Mississauga has made some discoveries on what we can improve to make things easier for developers. Here are some of our key findings for the day from the Adobe® AIR® side:

  • The flow of developing your first application by following the Adobe AIR developer site needs some improvement. We discovered there are some disconnects with how developers go from downloading the tools to getting their helloWorld application created and deploying it to a simulator or a device.
  • Finding our way through the documentation was confusing. We found that when we were trying to complete certain tasks, the docs were not very straightforward or easy to find.
  • The downloads page doesn’t include links to everything you need to download. For example, if you don’t have JRE 1.6, you’ll need to download and install it before you install the SDK. Also, to use FDT, you’ll need to download and install the Flex 4.6 SDK.
  • There were system requirements for each tool you needed to download. It would have been nice to see one amalgamated requirements list.
  • Samples need to be easier to download and should be easy to get working in supported platforms.
  • There needs to more information and documentation around developing a BlackBerry 10 experience in AIR and more best practices.

We have many more pages of notes that we took throughout the day. The next step is to create bugs in the Developer Issue Tracker so that you can follow along with the progress as we make improvements for a better Adobe AIR development experience. You can expect those to come next week. We hope to address the top issues in the coming weeks.

Join the conversation

Show comments Hide comments
+ -
blog comments powered by Disqus