After uploading a description of the CG's purposes and its background, it can now be officially considered as active.
As a reminder, popularity of mobile software applications (often referred to as mobile apps) and various app stores have presented service providers with interesting challenges. They affect a variety of building blocks that form the end to end user experience. They range from data connectivity over-load to power consumption on terminals. The base document shared by GSMA on this topic is a timely step to raise awareness amongst the community. However, the next step of updating the document is a non-trivial exercise as we intend to hear other voices on the same topic(s)to ensure the highlighted issues and remedies remain all encompassing and relevant to as wide audience as possible.
The broad topic has been in the news; the following is a good example.
Some research work has also been conducted in the broad context by MSFT in collaboration with Purdue university. The outcome supports our general approach
I have sent a request to hold a teleconference with the view to move forward at a quicker pace in this CG. The intention is to make the communication more interactive, immediate and humane. I believe by doing so, we may be able to persuade more brilliant minds to contribute to the CG's proceedings.
One key topic for discussion is to ensure we can cross reference both W3C's document (which has a specific web browser focus) and the GSMA's document which is meant for native applications. It is important to identify points of intersection as well as any common grounds to make them more complementary in content and mission than they are.
GSMA’s proposed changes for the new update of the base document
The base document may be downloaded from http://www.gsma.com/technicalprojects/wp-content/uploads/2012/04/gsmasmarterappsforsmarterphones0112v.0.14.pdf
1. Application downloads (from Server/Store) and updates - policy and recommendations
2. Selection of Communications mode – Cellular vs Wi-Fi – policy for selection and switch-over if Wi-Fi is available (partly covered by other WI in TSG and OMA)
3. Inclusion of other platforms in addition to the existing ones. Samsung and RIM have expressed an interest to contribute chapters on their respective platforms
4. Ensure a close alignment with GSMA’s EM guidelines. For example on the incorporation of an element of randomness into scheduled network access
5. Expand Push notification (C2DM) as it was new to Android when the document was drafted and new information has come to light since
6. Rework the section on MSFT’s Tombstoning to ensure it is consistent across all of the platforms (each of which achieves the same effect in a different way). That also means embedding/expanding appropriate text for each of the remaining platforms in a consistent manner
7. Step-by-step tutorials on how to embody the guidelines in applications. To supplement the document with a set of Eclipse (or other IDE) projects + narrative text that guides a developer to create a single application that incorporates each of the guidelines. Meaning the tutorials will be developed for each of the platforms included in the document
8. Better use of Dalvik in developing Android based apps. Android makes use of Java as a means of developing applications which are subsequently compiled into Dalvik’s byte code for execution. Developing a good Java application in the Android world does not necessarily translate to good Dalvik (or any other VM) bytecode . It is important to explain the pitfalls and common mistakes to ensure a more optimal outcome. This is a Android specific suggestion but its message would be valid for any VM based environment
9. When designing an application, it is important to fully utilize dark wallpapers and themes for saving smart phone battery. More than any other component of a smart phone, the display consumes battery life at a devastating pace. Switching to dark wallpapers and themes can have a big impact on battery life