Here a list of the questions and answers asked during Wednesday’s Webcast:
WILLIAM Asked:: In the real world there seems to be a much larger presence of iPhone and Blackberry touch screen mobile devices than Windows mobile touch screen devices. What are some suggestions for developing web applications that cover these devices that have the majority of the market as well as the Windows mobile devices? Answer: Yes a good strategy is to develop for Standard (non-touch) since these apps will work equally well on touch devices – the reverse is not true. Remember that non-touch devices are optimized for one-handed operation.
Hilary P Asked: Where are your DLLs? All I see is the text file ... are you writing/highlighting somewhere? Answer: Open the dumpmem.txt file. Search for the following line: 1819F000 1141000 F NA This is the largest free memory block and the bottom of the RAM DLL load area and the top of the program stack, resources, and heaps area. The DLLs are just below this line. The ‘Image’ lines belong to the DLLs.
D.P. Asked: understand the need for signing the apps... but can still distribute unsigned apps if they do not need signing... right?
Answer: Yes this is a strength if the Windows Mobile platform in that you can distribute your applications however you see fit. However, you run the risk of your application not being able to be installed, if the mobile operator has configured the device to disallow unsigned applications from installing or running. Additionally you will run into the problems (mentioned in the webcast) of having the user to respond to prompts during installation, or mysterious failures during silent (Enterprise) installs. Most application resellers require that you have your application signed (Handango, Motricity) before they will carry it.
D.P. Asked: Are there any free (not vendor locked) APIs for putting code in ROM?
Answer: Only OEMs, not ISVs, can change the device ROM. Technically when you install an application is it stored in flash (ROM) memory.
EDUARDO Asked: nice all