After our session on MTS there were two questions. I think that those questions need some comment. We were not 100% sure of answers, so we said that it will be the best to make some test and check how the phone will behave. We didn’t have possibility to do this on MTS, so we have done it now. The results confirmed our answers. Read more
As promised, below you can find conference materials from MTS – The devil is in the details – building high-performance applications for Windows Phone:
In case of any questions please do not hesitate to contact me.
Only few days left to start of MTS conference. I hope that everybody who wanted to join the conference have managed to register on the presentation that I will have pleasure to lead – The devil is in the details – building high-performance applications for Windows Phone. It will start at 14.30 in second day of the conference. It will be placed in room E.
During the presentation I will try with my friend to convince the audience that the micro optimisations can significantly improve application performance. We will show two examples that have been taken from real projects and demonstrate forgotten hints that will allow to boost our application. You should be able to identify places with possible performance issues after watching our presentation.
Despite the fact, that the title of presentation suggests that it will only apply to Windows Phone devices, the guidance contained in it will be also valid for other platforms. The results may not be as spectacular as on Windows Phone, but certainly the application should work better after this changes.
MTS 2012 conference is also a chance to talk to experts and make new contacts. I encourage you to visit the Ask The Expert zone. I will try to be there from the early beginning. So if you have any questions connected with Windows Phone, I hope that I will be able to help you. To make sure that I will be there please send me an email.
Windows Phone application must pass certification criteria. You can find two of them that are strictly connected with application start-up time:
- the application should show first screen of application in less than 5 seconds. Of course this can be splash screen,
- the application should respond to user actions no later than 20 seconds after launching.
You might wonder if this is a lot. From my point of view it is very difficult to overcome these two limitations. However, if we look at application from user’s perspective, waiting 20 seconds for start of application can be terribly annoying. You should be aware that after next 10 seconds screen saver could be launched. For this reason I propose to consider the possibility of improvement of starting time of application.
I assume that such things as:
- running long operations in different thread than UI thread,
- showing notification to user about the status of on-going operations
are obvious and need no explanation.
One of the biggest gaps in performance counters is the lack of information about current memory usage. One of the requirements for the certification of applications on Windows Phone 7 is limitation to 90 MB memory usage by an application for phones with less memory than 256 MB. At the moment there is no phone on the market that meet this condition. Theoretically, we should not worry. However, according to the information from Microsoft the next generation operating system Windows Phone Tango should already allow for the production of low-budget phones with less memory. Read more
When you are creating application you should always remember about its performance. Application should run smoothly, information about the change progress, response to user actions, etc. In the case of mobile platforms, this problem is even more serious. We are used now, that computers have more powerful multi-core processors, large amount of memory, or fast disk. What was once important in the software development process – the effectiveness of proposed solutions – are often not taken into account. Now, shortcomings in the code are being compensated for by efficient equipment. Read more