The benefits of Fragmentation….
March 2nd, 2006
Update2: To be clear, this post is not talking of Java only, but of all mobile technology! So I will clarify this in a later release…. (end of update2…)
Ok, the title is a little bit controversial, but “Fragmentation” is usually considered as the worst thing that could happen in this industry. Even if it’s a real pain, let’s be more positive. I see it as a result of what is one of the most interesting things of mobile: innovation… Mobile is an incredibly innovative environment: in applications, services, software, hardware….
Innovation, by definition, creates fragmentation: this create new opportunities, or different ways to do things, sometime better, sometime worst. Then, with time, on a specific topic, things stabilize, winner emerges, and fragmentation reduces. In the meantime, other technologies are coming in other areas. There is a continuous shift, where older innovations become standard, while newer creates fragmentation. The fact the life cycle of a mobile is “relatively” short, help a lot…We don’t deal with ten years old phones, but only with four years old phones….
This does not mean that we should put effort to reduce fragmentation, but we should find a way to balance in finding ways to reduce it, while still keeping room for new ideas…
Update: C.Enrique pointed out a point that I forgot to mention. Of course, there are drawbacks, especially if fragmentation is used by big companies as a tools to break standardisation, and not a tool to promote innovation. And he gives Nokia SOA as an example of this wrong approach….
So, I have a few clarifications:
- fragmentation happens in all areas (and no, I am NOT talking of Java fragmentation): Brew, Java, FlashLite,SVG, Wap/XHMLT, Ajax, etc…are fragmenting technologies. Some are complementaries, some are competing…
- fragmentation happens also for hardware: bluetooth, WiFi, NFC/Rfid are all fragmenting technologies in a sense, but great innovations
- Other example of fragmented areas: business models, payment methods….
- As discussed earlier, the bad side of fragmentation, is to use it to create walled garden with competing with standard technologies. Of course, this is obviously not a benefit of fragmentation.
Technorati Tags: wireless, java, j2me, fragmentation
Entry Filed under: Wireless
4 Comments Add your own
1. C. Enrique Ortiz | March 2nd, 2006 at 6:14 pm
I agree. But I disagree with fragmentation, just for the hell of it. For example, long time ago I wrote a piece on my blog titled “WORA will never happen” where I touched on this point of innovation. That is fine. Innovation will always continue, and is necessary. Then I wrote another piece on my weblog titled “Comments on Nokia SOA” where I criticized Nokia for introducing fragmentation, because in that case, there was no need to. Since then, they have corrected that error.
Companies, especially the ones with a lot of weight in this space, must be responsible about when to fragment and when not to. If fragmenting, they must follow up with standardization.
Enrique
2. Marco Casario | March 3rd, 2006 at 11:31 am
Hi Tom,
but in my opinion we should (and handset manufactures) find a way to work with innovation and new ideas without increasing fragmentation !
The way of following standard is the God, but it’s not a quick process.
When I read your post I wrote my opinion on my blog :
http://casario.blogs.com/mmworld/2006/03/mobile_fragment.html
3. C. Enrique Ortiz' Mobilit&hellip | March 3rd, 2006 at 5:54 pm
When Fragmentation is a Good Thing……
In his blog, Tom Landspurg writes about the The Benefits of Fragmentation, and how
Innovation and Fragmentation are related to each other…
I agree with Tom. At the same time, I disagree with fragmentation just for the hell of it. For example, lo….
4. +34.net » Blog Arch&hellip | June 9th, 2006 at 1:54 pm
[…] ¿Son inseparables la fragmentación y la innovación? ¿Tendrán futuro los Mobile Widgets? […]
Leave a Comment
Some HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
Trackback this post | Subscribe to the comments via RSS Feed