---

Results of Survey for Mobility Pack 5.5 for CDC

The original CDC 5.5 Survey was published at http://mobility.netbeans.org/cdc55-survey.html in December 2006. Responses were accepted through the end of May 2007. The 10 questions from the Survey are re-stated below along with the tabulated results from the 62 participants.

Q1: What devices are you targeting?

Devices listed	Total selected	%
Symbian OS smartphones (Nokia Series 80/SonyEricsson UIQ)	35	56%
Windows Mobile PDAs	30	48%
Other mobile phones	27	44%
Multi-Function Printer	3	5%
Set-top boxes	8	13%
Other	6	10%

Other devices included: Blackberry, Docomo, iPhone, Palm OS (2x), Nokia S60 (CDC support will come later in 2007)

Q2: How are you deploying your applications?

Method of deployment	Total selected	%
File copy	45	73%
SCP	5	8%
Http post	17	27%
Bluetooth/Infrared	31	50%
Other	11	18%

Other deployment methods included: email attachment, DSM-CC object carousels, REST web services, OTA, USB cable (3x), Nokia Active Sync, database

Q3: What "profiles" are you developing your applications for?

	*# participants*	%
Foundation Profile	28	45%
Personal Basis Profile	28	45%
Personal Profile	36	58%
Advanced Graphics and User Interface (JSR209)	25	40%
eRCP/eSWT	10	16%

Other Profiles included: eSWT, MHP, OCAP, GEM, Java TV, JMF

Q4: What features of the Mobility Pack for CDC are most useful for you?

	*# participants*	*% of 62*
Matisse support	44	71%
JUnit integration	10	16%
Packaging, Signing and Deploying	42	68%
Building, Running and Debugging	41	66%
IDE integration	44	71%
Other	4	6%

Other useful features mentioned: Interaction with REST-based webservices, MIDI applications

Q5: Which of the following would help you be more productive with Mobility Pack for CDC?

	*#*	*% total*
More features	42	69%
More stability	12	19%
Better UI and workflow	8	13%

Features requested by respondents to this question:

1.Ricoh integration need bug fixes and feature enhancement 2.Integrated SVG creation and animation in IDE 3.Web services client wizard and support(3x) 4.Full or better linux implementation and support, including emulator (3x) 5.Better integration with real devices, skins that match actual devices and their API's 6.Ability to customize Platforms for MHP, OCAP, and GEM with selectable optional features. This is how Platforms and APIs are implemented in Mobility Pack for MIDP. It would just be really helpful to instantly see which classes and methods are available in each of the profiles or platforms, and to use this information with the javadocs display and code completion 10.Integration of external devices, via USB, COMM. I'm interested in Barcode scanning and MIDI application interface.

---++++More stability: 1.IDE can't find the installed CDC platform on my machine - or even the CDC platform bundled with the CDC Pack 2.Netbeans CDC Pack crashes often 3.Netbeans can be slow, even on a fast CPU.

Better UI and work flow:

1. CDC should behave more like CLDC with better/more complex UI and Flow Design support (4x) 2.better emulator integration 3.Hot deployment of jar file to emulator

Q6: What additional features would help your CDC application development?

1.eRCP/eSWT support 2.Ability to use WEME (IBM) as target. 3.More Bluetooth Support 4.More IDE integration 5.Web Services client wizard (3x) 6.More UI Components 7.Better documentation with lots of examples. 8.Refactoring tools that would allow me to remove Java 5 dependencies from code (e.g. generics enums etc.). Maybe retroweaver integration so I can just compile Java 5 code into CDC code that would actually deploy. Better real device support and skins. Tools to ease porting of Java SE code into CDC code, e.g. take an existing Swing project and convert it automatically to 209 by commenting out code that makes use of features that don't exist and leaving a "TODO comment". Maybe a refactoring tool that takes 209 code and converts it to AWT code for personal (or is it foundation?) profile? 9.Easier to deploy and test on devices, Symbian phones, 10.Mac OS X support for the Mobility Packs 11.API for Wifi like the Bluetooth (JSR 82) 12.Guide for developing my own emulator. 13.Include the Profiler as Standard Java Application. Thread Monitoring tool Memory Monitoring tool 14.Ability to add pocket pc 2003 emulators and simputor emulators. 15.multi-OS, multi-processor support in a (partially?) optimized implementation. Current targets are ARM 9 and ARM 11. Support (or support hints) for non-gcc target compilers. i18n and l10n support that is OEM driven. 16.JDBC plugin for cdc 17.Linux version with emulator (2x)

Q7: Is there a serious bug or UI flaw in the functionality that affects your daily work?

YES	10	16%
NO	52	84%

Comments: 1.Sudoku app on Google code doesn't allow proper navigation when run on the default color phone emulator. (Arrow keys and number keys don't respond when pressed.) 2.No web service/consumption tutorials, user trying to write Amazon Web Services client couldmn't get the stubs generated. 3.Performance 4.AGUI is not always available on target platform, need easier way to define my platform features/limitations. 5.amd64 compatibility 6.Linux port with emulator (4x)

Q8: How did you hear about the Mobility Pack for CDC?

	# participants	% of 62
Web	53	85%
Advertisment	1	2%
Blogs	14	23%
Other	6	10%

Other: 1.Long term NB user (3x) 2.Google 3.SUN website 4.someone talked to me about it

Q9: What areas of CDC development using the Mobility Pack for CDC would you most like to see discussed in articles and/or tutorials?

1.Web Service consumtion and deployment with a real server like Amazon/Google etc(6x) 2.Integration with eRCP/eSWT 3.End-to-end tutorial (Could be multiple articles) 4.Using Bluetooth to connect from a phone to another device (3x) 5.User interface development 6.Step-by-step install and set up of needed software for the best usage of this pack (eg: Quick Start) (5x) 7.3d graphic and multimedia APIs (4x) 8.SVG Compatibities 9.Database integration/connectivity (3x) 10.Hot syncing with a device 11.Device support matrix with tips for deploying apps on those devices. 12.Advanced application development, not just simple hello world tutorials. 13.Signing, certificate use, secured connections (SSL,HTTPS), Lowlevel hooks to hardware. 14.Networking 15.MIDI and external device communication. 16.Porting to "new" hardware. 17.How to use optional packages

Q10: Would you use a localized version of this product if it existed?

NO	44	71%
YES	18	29%

Top Language Requests: 1. Three Requests for: Brazilian Portuguese, Arabic, Chinese, Japanese *Note:* ZH and JP are localized. 2. Two Requests for: European Portuguese, Italian, German 3. One Request: French, Spanish, Indonesian, Polish

---+++ Summary of potential Action Items for Development and Documentation teams:

Feature suggestions:

* Support for eSWT (2x) * SVG authoring tool integration (2x) * Linux support! (in both CDC toolkit and IDE) (6x) * Make CDC web services and flow design more like CLDC/MIDP pack (3x) * Refactoring tool for converting AWT to Swing (and reverse) (2x) * Ability to port Java SE to CDC code * Tool that removes Java5 dependencies in code * Fix Ricoh bugs and integration issues * IDE has trouble finding/recognizing compatible CDC emulators

Doc/Tutorial Suggestions:

* More examples in tutorials * How to create your own emulator/skins guide * How to consume web services tutorial w/ real world example (Google, Amazon or such)(5+ requests) * Bluetooth tutorial with specific examples of real uses(3x) * End-to-end tutorial that's a creates and deploys a practical, "real world" application (2x) * UI development tutorial that's more in-depth/ multi-layered * Database connectivity tutorial (2x) * 3D API, multimedia features (3x) * Hotsynching document/demo * Security implementation in CDC (certificates, secure connections, SSL/HTTPS, low level HW connections)