How to get contents to all mobile devices.More on mobile fragmentation

Mobile fragmentation is one of the aspects a mobile developers have to face with.
Today I met with the CRO of Genius Byte, a Ricoh Premiere Partner company, and he told me about their Office P2P solution. That is a system that controls the information required by each user and arranges the file in the more accessible and appropriate node. When a file is requested, a search is conducted on all the nodes and the results are sent back to the user.
They started to develop a version of their system for mobile devices, but after few months they quitted due to long development process especially for porting the application through different phone models.
Another victim of the J2ME fragmentation.
Recently they saw a German Adobe presentation on Flash Lite and they contact me to evaluate to develop some services of their system with Flash Lite.
They believe that Flash Lite will become a standard for mobile phones and one of the major reasons is that it will reduce the fragmentation process and it's a 3rd party technology universally accepted.
Developers / Publishers / Manufacturers  trust Flash.
Totally agree.

At the end of the meeting he suggested me to read this article by Doug Barre titled : Device Differentiation Drives Demand for Wireless Content Management.
It's a great article that gives us some recipes for "Order from Chaos" of fragmentation.
The author succesfully replies to the question :
How does a content publisher get all of their different types of content to all devices to a mass market of users in a world where the parameters are in a constant state of flux?
There are number of areas that are critical to success going forward : 

First, publishers must have a way to consolidate information about all devices and all operators. This entails having access to a database that is constantly keeping pace with device requirements, specifications and a myriad of other details.

Experiential information is another key requirement. Reading a handset manufacturer’s specification sheet is not enough, since it won’t help publishers understand the ‘nuances’ that may come into play, such as how the device performs under stress, and/or inherent bugs and idiosyncrasies that have been detected and verified over time.

Coupled with the knowledge of these variations and deviations is understanding how to work around those issues and modify content in order to get it to function effectively on the device(s) in question.

Publishers also need to have a thorough understanding of all the variations in testing content and quality control procedures to meet specific operator and/or device requirements.

Consistency in the deployment process is absolutely key especially in environments where multiple developers may be working on different versions of the same applications. It is imperative to have the measures in place that ensure consistent results in the end product.

Process efficiency is required for economic survival in this industry. Publishers need to create processes that maximize resources, leverage existing content and automate as many functions as possible.

Effective asset management is integral to the development process. In the increasingly complex environment of mobile game development and deployment, the pressure to know what has been deployed where, who is in charge of what content and when, and the various stages of porting and testing continues to grow.

Good points !!
I know this is the last post on mobile fragmentatio, but it's a troublesome issue !

Other posts about mobile fragmentation :

• When Fragmentation is a Good Thing...
• J2ME makes mobile projects difficult, so use FlashLite
• Mobile Fragmentation is not the evil (for Flash Lite)

• Bookmark on del.icio.us
• Digg this site
• Technorati Tag