Rants And Ramblings About Mobile Technology

Opera Mini is awarded Product of the Year by GetJar. Well-deserved.

Free Java, Symbian, Palm and Pocket PC Software

I stumbled upon ZeeMe which is a Java ME application that enables you to play Z-Code (Infocom and third-party) compatible text adventure games on your mobile.

The interpreter didn't handle the input field too well (I had to scroll down to see it all the time), but at least you'll get a feel for what kind of games people played in the 70's.

A mini version of Zork I (one of Infocom's blockbuster games at the time) is included, and with ZeeMe Packager you can build new games based on combining Z-Code games with ZeeMe. See e.g. IF Archive for lots of free games.

ZeeME

Similar to Skype, fring uses P2P technology to provide scalability. That said, mobile phones (with the current fees and speeds of mobile networks) are not suited to act supernodes, so I wonder how they've achieved this.

It can communicate with Skype Google Talk (as of now), and also supports text chat.

Even though the service is in itself free there can be a considerable cost in the data transfer, and depending on the efficiency of the voice compression, might be anything from noticeably costly to very costly.

If you have a flatrate data sub, then fring might be exactly what you need.

As the site's page rank is none, this must be a very new service.

As lower-cost mobile telephony is so important to most people I'm sure many more service providers will jump on the mobile VoIP wagon.

fring - it's fringing free !

As outlined here, most such applications are part of a client/server solution, where most of the intelligence is central and shared.

Even so, the examples mentioned from Nokia, Salesforce and Orative show that we've moved from complete ignorance to at least some awareness and deployment.

The deployment part is really the proof of the pudding: It's easy to theorize about new things, but when it's actually being used, to positive effect, then it's way easier to convince future customers and investors that this will fly (and not just may fly).

Business Applications Squeeze Onto Mobile Devices - Yahoo! News

Contrary to the conclusion in this note by MobileIndustry.biz I'd say that less than 10% is still pretty good, considering most people just use their mobile phones as ... phones.

It's like comparing with cars: "less than 10% of car owners buy bumper stickers". So what?

Well, it's not a "So what?" if selling mobile content should be (or even needs to be) the new source of revenue. Even with much better access to mobile content, and more relevant content, we won't ever reach 100%. Read the bumper sticker analogy again.

I believe though that most efforts should be put into making mobile data a hit in general, and establish that as the main new revenue generator for operators. I've mentioned before that to get there operators need to change the business model:
* Provide enabling services, not the services themselves
* Introduce flatrate plans
Without this we haven't even moved from square one.

Less than 10 per cent buy content through their phones - study - News /// MobileIndustry.biz

In-Stat claims many mobile phone users still carry around dedicated cameras (80%), music players (>50%) and PDAs (75%). Hopefully only when such gadgets are needed though.

My old 4 Mp digital camera is still much better than the one in e.g. the Sony Ericsson K800i, but even with that rationale 80% is still a very high figure. Using a cameraphone is nowadays very simple, so that doesn't sound like a show-stopper.

I fully understand the figure for music: Phones still can't compare when it comes to ease-of-use and amount of memory (when talking mainstream phones). Even so called music phones are in my opinion too hard to use, as music functions fight for attention with so much other functionality.

The most odd is the PDA/smartphone bit: If a customer buys a smartphone at all, why not select one so the PDA can be ditched? Frankly, most so called smartphones are not equal to a PDA (e.g. the Nokia N series, that don't have alphanumeric keypad nor a touch screen), which dillutes the smartphone term. Yet, there are good smartphones that can replace a PDA 1-to-1, like the Treo's, Sony Ericsson P and M series, Nokia E and 9xxx series etc.

There might also be other reasons altogether:
* Gadgets are purchased for status reasons. Photographing with the latest Canon or Nikon is way more status-inducing than using a lowly cameraphone.
* Consumers might not buy the phones for the mentioned features. Take e.g. any non-business Series 60 phone: It's considered a smartphone but most buy them as vanilla phones.

It will for sure become better over time, both in terms of capacity and hopefully also ease of use, which will put a dent in the statistics as well.

Study: for most, all-in-one phones aren't - Engadget Mobile

Just a headsup that 5.5 is released.

There are several new Packs:
* C/C++ Pack
* Visual Web Pack
* Enterprise Pack

NetBeans 5.5 IDE

As this article shows, there's a lot of untapped potential in the use of mobile phones, but some of the mentioned applications seem more wacky than useful.

Telecom Asia: The wildest mobile apps

It's actually really smart (but also a bit cynical, despite the positive outcome): Asking students at high schools to send in SMSs with the text "Diddy". The school sending the most messages got to see P. Diddy in concert.

Likely no cost for the radio station setting this up, nor for the operator, only for the students.

In total the radio station received 170k messages during the contest. It doesn't say if there was a premium on the SMSs.

This could easily be broadened to the general public, and is already used by e.g. TV shows. Then the cost is typically premium, sometimes as high as $1 or more.

It costs to set up Premium SMS, but if the volume is large and consistent over time the benefit is an obvious new revenue stream.

Text messaging catches on in music business | Tech&Sci | Internet | Reuters.com

Informa believes that mobile access to user-generated content (Web 2.0 sites if you will) will be big business, and that existing brands in this market will lead.

I believe so too, but I also believe there are possibilities for mobile-only or mobile-enabling services to pop up all over the place and take a slice of the market. E.g. ShoZu is such a service: Without actual image archives ShoZu would be of no value.

Actually UGC can change news media as we know it. If most people read news at aggregation/popularity sites like digg, reddit etc the original news sources might be left behind from an end-user perspective, serving those that choose what news to highlight. Maybe even TV, radio and magazine news will get an element of UGC to try to stay on top.

Of course mobile UGC also applies to blogs, chat and other services, including those that aggregate several of the known methods of UGC, like MySpace.

News | Mobile UGC set for major boost - NMA

Inspired Gaming Group has started offering vending machines that can also sell ringtones and games, top up prepaid cards etc.

Topping up prepaid cards this way sounds very practical.

Ringtones sounds a bit more counter-productive and uneconomical, considering buying and downloading mobile content over-the-air must be much better, right?

I can though think of a few advantages:
* It's more in the face; customers might be more interested in trying ringtones this way
* You use normal coins to buy content; more tangible and minimal risk
* The vending machines can be themed, like selling Coca-Cola beverages and Coca-Cola ringtones etc

Of course vending machines with only mobile content would be a very risky venture. What if installing all those expensive machines would give nothing in return? In this case though the mobile content comes as an add-on to more normal offerings.

Quote: Initial results have been positive, according to IGG, with the new machines taking twice as much money as normal ones.

Ringtones, CDs, games? Go to a vending machine - Sunday Times - Times Online

Eric Giguere provides a tutorial on the use of Web Services in Java ME. It's a good read as it also mentions alternatives to integrated support if not available in phones.

A quick look at j2mepolish.org shows there are not many phones that support the Web Services API in Java ME, but luckily there are the open source efforts kXML and kSOAP that can be used instead.

That said, if you use PHP or ASP on the server-side it in my opinion still makes a lot of sense to use HTTP POST if the transactions are simple. That will work with every MIDP, PHP and ASP version combination.

Service-Oriented Architecture and Java ME

Michael Mace at Mobile Opportunity made a survey for the visitors to his issue of Carnival of the Mobilists. I leave it for you to read. There's too much in there to summarize.

If you are a CotM host I recommend reading the free form comments at the end (Suggested features and beyond).

Mobile Opportunity: Who reads Carnival of the Mobilists?

Richard Spence at BlueTrail commented on my Java ME in the enterprise note, so I did some analysis what they are up to.

BlueTrail focuses on know-how in the technologies needed for developing mobile applications in Java ME and adapting enterprises with mobility in mind, and for access from Java ME applications or the embedded messaging or browsing applications. Simply put, what's needed to know to mobilize enterprise services.

Their Mobriz solution provides mobile-based surveys. Customers configure surveys via BlueTrail's site and users then access the site by downloading a Java ME application and fill in information in a custom form (based on the configuration). This could have been done in WML too of course, but with less user comfort, unless installing a new application could be considered a discomfort in itself.

BlueTrail's Mobile CRM solution has been provided to Red Bull, and there's a success story about this.

I get the impression that BlueTrail also does customer-ordered development, so it's not just off-the-shelf product sales.

I noted experience in J2ME Polish and based on the screenshots it seems the survey and CRM applications are using that. I've considered it myself due to the compatibility with standard MIDP (1 and 2) form elements and the possibility to completely customize look-n-feel even though it will work on both MIDP 1 and 2 phones.

Richard mentioned that the location application described on the site uses a central service for location rather than the Java ME Location API. The Location API is still only available in a few phones, so this is the way to go for now.

He also added a comment on the fact that Java ME is used and not Symbian OS etc, which is similar to my way of reasoning: The enterprise side is an interesting area, in that some of the applications we have done have only really become viable when we implemented them on a mobile phone. Had we suggested a windows mobile device or palm, I am sure customers would not have been interested as they would have seen the introduction of new devices as a barrier.

And here's what he had to say about fragmentation among Java ME implementations: Another exciting thing about enterprise Java ME is that the fragmentation issues are less pronounced. Why? Well often the users have the same phone model or at least the same manufacturer (Nokia!).

BlueTrail - Great Applications for Mobile Phones: Java, J2ME, WAP, MMS

Informa estimates it to generate $13B in revenue by 2011.

Quote: Moreover, Informa predicts that the inevitable move towards flat-rate monthly packet charges will result in the imminent emergence of larger files of up to at least 200Kb.

True (yet operators still don't provide this), but we are not talking 200 kbytes, rather 2 Mbytes per file. When users have real flatrate data the dam will burst. Downloading times is not a major issue, unless the battery runs out of juice much quicker this way.

Surely networks will be faster until 2011 as well, lessening the issue of downloading multi-Mbyte files.

Even more than on PC-accessed music services I believe single song sales will completely dominate, due to downloading times, but also simply because that's the general trend anyway, and because at many times the song will be used as a ringtone, which will also affect how music is being made (more focus on releasing singles ahead of complete albums etc).

I expect monophonic and polyphonic ringtones (MIDI or other formats) to have all but vanished by 2011.

As I prefer theme-based elaborate classical or progressive rock albums in at least CD quality (compressed to a non-lossy format like FLAC) this is probably not for me anytime soon. I don't think music download services will care about "my" demographic as most customers will be happy with the latest heavily compressed single songs.

AllOfMP3 is as all knows completely illegal, at least based on non-Russian law (they buy one CD, rip it, and sell it in any number of copies; doesn't sound very legal to me), but one thing they've done completely right is to let the customer decide what format and quality to download. The larger the file the higher the price. Providing this flexibility for mobile phones probably doesn't make sense, but I hope music services will provide this for broadband or hot spot download.

To support FLAC and similar you need a lot of memory, but as Flash-based players and phones now have 4 Gbytes, it's feasible provided you can use a PC as main storage for all your media. My iAudio X5 supports FLAC, but it also has a 20 Gbyte hard drive, so it can store several albums in this format.

Mobile music market to reach US$13 billion by 2011, says research firm

I know this is strictly off-topic, but as this is still not fixed I can as well mention it here. We are talking the very latest version 1.5.0.7, but it's been this way a long time. Is it only me that's experiencing these things?

Cut/copy is broken

Try marking text right-to-left instead of left-to-right or marking the URL on the address line. It very often fails and I end up with nothing cut/copied. After a few tries it tends to work though, but why not always on the first try?

Crashes

Firefox seems much more sensible to rogue printer drivers than other applications, as it often crashes when I try to print something via File / Print. All browser windows crash simultaneously, so it's clear they are not running in different processes.

Otherwise it's no doubt a good solid browser that seems more light-weight than Internet Explorer.

After all this talk about the mobile web it might be interesting to know (probably mainly for myself) what I access via my mobile phone. Nothing racy going on, sorry, and if there was I wouldn't tell you about it anyway.

I nowadays primarily use a Sony Ericsson M600i, which is not a normal phone by any means, so the possibilities are a bit broader than on a mass market phone, especially in the display real estate and text input departments.

In brief I mainly use it for daily news and email.

Most Swedish newspapers have mobile sites, and I access those simplest via my own site wap.abiro.com / Mobile News. Tabloids tend to report the same news, so it's often enough to access one such service. As the information is optimized for mobile access it doesn't generate many "megabytes".

I also check my email account this way (which is not really about the mobile web, but let's ignore that). My ISP supports IMAP, so the behavior is quite similar to what I get on a PC, and erased emails stay erased also on the server. With the M600i I can easily write brief email responses.

After I had browsed through the operator's portal when I got the subscription I quickly realized I didn't have any use of it. I'm not in the ringtone and wallpaper demographic (at least not in terms of buying such), I don't want to pay for news, and games and applications are much better provided by other services.

For application downloading I mainly use GetJar (wap.getjar.com) and ClickApps (wap.clickapps.com). Especially GetJar has a lot of free applications, primarily in Java ME. I host my own applications at both sites.

When unknowns call me and I don't get time to answer I sometimes check who they are via Hitta.se (wap.hitta.se) or Eniro (wap.eniro.se). wap.hitta.se is in my opinion better, as it's more intuitive. I would have liked such a service being integrated with the phonebook, so unknown numbers were automatically looked up when someone is calling. Broadband VoIP services can do this, and it should be possible to do on at least Symbian OS and Windows Mobile phones. Some assembly required. The main problem is that these services are regional, but there might be enough users that want this in one specific country.

I of course also use my phone for testing my mobile sites and mobile applications. Every time I change my mobile sites I test them via a real phone (not just desktop Opera or a phone browser emulator) as WML is very sensitive to syntax errors. Also of course I need to test Java ME applications on real phones, as the WTK emulators can't be trusted when it comes to real phone behavior.

That's about it. I Not much to get excited about I guess, but at least I do access information services via my phone.

comScore Networks has provided statistics on the use of mobile web services.

Note that no Asian country is included in the statistics, which is a pity. It would be very interesting to see how Japan, Korea and China stack up. Probably very well.

It mentions that Nokia phones are dominating for mobile web access in Europe, but that's simply because Nokia dominates, period. Same thing with USA where Motorola dominates.

That so many Americans access other portals than the operators' while Europeans mainly access the operators' portal is quite remarkable. Because in USA mobile web services are mainly accessed from smartphones and hence can provide a more full experience? I don't know, and comScore doesn't provide a convincing argument either.

Europeans More Likely than Americans to Use Mobile Phones to Access the Internet

Update: I contacted Ephraim and got this feedback regarding whether it's actually possible or allowed to set up high power Wi-Fi towers: "I believe that the FCC limits the range of Wi-Fi by putting a limit on the strength of the antenna signal. So I believe you could not put up a high power Wi-Fi on a tower."


Ephraim Schwartz at InfoWorld argues that a major reason operators go for WiMAX is that it's licensed and hence can't be acquired by just "anybody".

Wi-Fi on the other hand is using unlicensed frequency bands. Maybe this is a signal to new wireless and data-focused operators to set up high power Wi-Fi towers covering towns or at least campuses (university, corporate or otherwise). Especially as more and more phones have integrated Wi-Fi and voice can be handled via VoIP.

How Wi-Fi behaves in a setting where there might be a thousand connected users per tower I don't know. WiMAX might have improvemements in this area.

As Wi-Fi (or rather sub-standards of IEEE 802.11) is likely to evolve faster than WiMAX, due to the pressure from inhouse corporate and home use, it's also possible performance over Wi-FI will be better over time than for WiMAX.

Behind the push for WiMAX | InfoWorld | Column | 2006-10-24 | By Ephraim Schwartz: "Behind the push for WiMAX"

SearchMobileComputing has a series on mobile application platforms, and this time it's about Java ME.

I agree with the core points highlighted here, and that incompatibilities between phones is the biggest issue with Java ME, but it's not a showstopper, as basic MIDP 1 applications will run unchanged on most phones, so I'm more positive than the people speaking through this article.

Most corporate applications are forms-based, hence basic MIDP 1 is enough for many corporate client/server. By deploying MIDP 1 Canvas it's still possible to provide reasonably looking graphics for e.g. diagrams and such. HTTP is part of MIDP 1, so basic service communication is supported as well. With J2ME Polish it's also possible to make forms look really good without sacrificing compatibility. I noted BlueTrail (see the comments) uses J2ME Polish.

Choosing phones based on preferred platform is often tricky and limiting as that might require swapping all phones a company is currently using. This is clearly the case when going for applications that require e.g. Windows Mobile. Java ME doesn't have that problem. Even worse if different corporate services require different application platforms. Then you are really in trouble.

I've previously posted entries about other forms of incompatibilities, like specification (mis)interpretations and outright bugs, due to the several providers of Java ME implementations.

Again, to be sure a Java ME application will run on a certain phone you therefor need to actually test on that phone. You can't just assume it will run. This is a big issue with Java ME (and also Linux), and much less a problem with Symbian OS and Windows Mobile.

Where it can get outright hairy is when you need to access the camera, PIM database, file system etc of the phone. Then differences between phones really show. Functionality differences should be expected of course, as different phones have different base functionality and features like PIM and file access are relatively new. Best case you can test for this in your application, provided that the application can still work without the lacking functionality.

That Java ME is in its "own world" on the phone can also cause issues with e.g. cross-application functionality, but that also (intentionally) provides protection from applications gone bad.

Quote: mobile Java is already available on many consumer cell phones. It has yet to hit its mark with smartphones and PDAs
That's not true, technically speaking. Java ME is available on pretty much all newer smartphones as well. It might not be used for other than games though, but that's more an issue of perception.

The article under-emphasizes Java ME's complete dominance in mainstream phones, and it seems the industry has just started realizing this is a fact.

Quote: "Given the prevalence of BlackBerrys, I don't think Java is going to dry up and blow away,"
This is a logical somersault: There are 1B mainstream phones with Java ME. That's the driver! Relatively speaking BlackBerry's don't exist, except in the hands of managers. Implying that it's mainly managers that need access to corporate services is of course nonsense. That's repetition of the notion that PCs were mainly for managers etc. They are in the minority, and all employees need access to corporate email, sales people need to get access to customer info, consultants need to get access to time reporting, etc.

Of course, you don't need to download an application to the phone. Many corporate services can be provided via a simple browser interface, but if you need a high comfort level on the interaction, a good look-n-feel, dynamic graphics, phone function interaction etc, Java ME is a darn good choice for mobile enterprise applications.

Mobile platforms: J2ME -- looking for its place in the enterprise

This is an interesting test as it shows speech recognition can be fast and secure enough to be useful for converting speech to text messages.

In this test the speech recognition software was running on a high power PC, so a similar solution running on a phone would need to be squeezed to fit in the available memory and also the CPU power is way lower on a phone. Also, mobile phones are normally used in noisy environments, which also would lower the score for speech recognition.

Nuance provided the speech recognition solution for the test, and my understanding is that it's actually running centrally rather than on the phone, so in a thought "voice-SMS" scenario you would call the service and speak the message that would then be converted into a real SMS. I wonder how one gets a confirmation that it actually understood the message correctly. By speaking the converted message back?

Computer beats fastest text messenger - Yahoo! News

I've dropped my landline subscription and will from now on only use mobile and broadband VoIP. It took a long time to make the decision, but now I wonder why I didn't do it a long time ago. The comfort level has increased substantially.

Some rationale:
* A landline is shared, but a mobile phone is individual and always with me, and free for inbound and outbound calls (unless I'm myself on the phone already, duh). In other words: Landline = stone age. Mobile = contemporary. Also try doing SMS via a landline phone. All newer DECT phones support SMS, but few operators do for landline.
* I have a fiber/100baseT-based broadband connection, so obviously I don't need the landline for that. Not even VDSL beats this, and definitely not from a stability perspective. As I'm responsible for the broadband sub in my area I also have a chance to renegotiate to get even better conditions, price and/or services.
* I very seldomly send and receive faxes, and if I need to I can do it via my mobile or an Internet service. I wish Skype could do faxes via Skype Out. Theoretically it's possible to write a plugin for this (emulating the fax signalling). Maybe something for e.g. USRobotics to do, now when async modems don't generate revenue.
* The cost for the landline was high, and the mobile subscription is needed anyway, so why have both? Sure, calls are more expensive on mobile, but when summing up all other household and business costs, telephony is a very small item. Mileage may vary.
* Calls, SMSs and MMSs within the mobile operator's network are completely free (using 3Bomben Friends), yet of course not to other networks, but the cost is still relatively low. Not as low as landline though, but most calls are actually inbound.

The main issue I've noted is that as all calls go to the same phone it's somewhat harder to separate private and work calls, and I do get work calls also in the late evening. To compensate for that I save all numbers, including from telemarketers, to the phone book. In the latter case so I know when I shouldn't answer. And in the general case ... sometimes for the same reason :).

What I want now is a subscription with flatrate data, as data is actually the biggest item on my phone bill. I guess I'm not that talkative.

It's great that Sun provides such tips, as they started the whole thing (both Java ME (on the positive) and the defragmentation issues (on the negative)).

Goal: aim to reduce the practice of generating a distinct executable version (jar file) of an application for each and every phone

Building different versions based on the same source code yet with conditional compilation is mentioned as one solution, but I don't consider it a such, as you still get many versions of the same applications. The other, more dynamic approaches, are more interesting. Especially when the application is targeted for newer phones that have tons of memory, and so can handle applications that have some functionality that's not actually used for a specific phone.

It's focused on the issues encountered in Canvas-based applications, yet also with general pointers.

Thanks Sun.

Java ME: De-fragmentation Technical Overview and Design Guidelines Index

It's a Java ME / MIDP application also for these platforms.

Opera Mini Web browser for your BlackBerry or Treo @ PhoneMag.com

eWeek has a note on SavaJe supposedly giving up.

SavaJe has been a long-time promoter of Java ME and specifically CDC (see my Java ME Terminology).

As far as I know SavaJe hasn't sold much of its CDC-based platform, yet is supposedly a 140 person strong organization. That's a lot of people when there's no revenue. The note even hints that SavaJe might already be closed down.

This could easily make MIDP 3 more important than CDC for future mobile devices, as MIDP 3 provides an upgrade path for current MIDP 1 and 2 developers, while CDC is something completely different at least in the UI department and hence not compatible with MIDP. Of course the few existing CDC devices support also MIDP.

Here are a few of my other notes on SavaJe, CDC and MIDP:
Mobile phones with Java ME CDC
Is there room for Java ME CDC?
Motorola promotes a better mobile Java
Java ME, still not Write Once, Run Anywhere
SavaJe Jasper S20, an all-Java phone

MEX has an interesting piece that complements my note about Who actually gets the loyalty from consumers, where it's clear third-party now provides the interesting services, not the operators, and that operators need to refocus to enabling services rather than providing said services, that they anyway don't do.

It's a destructive/static loop:
1. Operators want to provide also the information services,
2. but they don't,
3. yet others do,
4. but operators don't want them to,
5. because, ... (start over at 1.)
Operators need to break out of this loop and realize what consumers want, what operators are good at and what they actually can make money on, and in this case it's providing billing and other "backbone" services for information services.

Sure, operators often partner with leading service providers, but that's once the services have become established (see Flickr, ShoZu, MSN etc). In this hectic "Web 2.0" era, time is of the absolute essence, so if anything hinders service providers from establishing themselves quickly they might completely lose out on the opportunity, hence operators can't be relied upon as shopping windows for new services. See Web 2.0 on overdrive for more on this phenomenon.

MEX - the strategy forum for mobile user experience - Why value is slipping away from the operators

Yearly doubling the sales of mobile phones with Windows Mobile sounds like a great feat, until you realize the estimated 12M units for 2006 should be compared to 1B of phones estimated to be sold in total this year.

Also, the definition of smartphones mentioned here confuses things: "which can run software applications such as email, mobile TV and games". All phones released now can do email and games, and not more smartphones than mass market phones can do mobile TV (faked/streamed or via e.g. DVB-H).

Microsoft is fighting with RIM, Palm etc for a very small part of the market, and it seems Microsoft wants to stay there, as it's got almost 10 years now to refocus to the mass market, but seemingly has decided to not go after that market at all. The last mass market phone with Microsoft software was probably the Sony J5. That software platform was for some reason dumped and replaced by the very heavy Windows CE based platform now called Windows Mobile.

As always RIM is mentioned as one of the players Microsoft competes against, but also RIM is in a very tiny segment of the market, and is not likely to ever achieve large volumes (read: 10s of millions of units).

I wish Microsoft all the best, but it's not a stretch to predict Microsoft will not be an important player in the mass market this side of 2010.

When you look at the amount of media attention RIM and Microsoft get you might think they together dominate the market (and at least the business market). That's the effect of successful marketing, and the fact that journalists are in the target group.

Microsoft sees fast growth in Windows phones: report - Yahoo! News

MobHappy hosts this week's Carnival of the Mobilists, pulling together the best in mobile blogging, at the same time celebrating the 50th issue.

Carnival of the Mobilists #50 at MobHappy

I previously wrote a brief note about WICD Mobile 1.0, advanced Web support for mobile devices.

Paddy Byers at Open Gardens explains that WICD-M actually encompasses also XMLHttpRequest, which I initially thought was left out.

Quote: The WICD Mobile variant is essentially just a profile, demanding certain XHTML and CSS capabilities, certain SVG capabilities, and certain DOM and scripting capabilities including XMLHttpRequest.

He highlights SVG (Scalable Vector Graphics) as a way to enhance the user experience and as an alternative to Flash Lite.

He still believes Flash Lite has a lot going for it compared to SVG, due to good tools, and that it's already supported by some mobile browsers and by some phones. Certainly Flash Lite is not that much deployed. I'm sure there are way more applications using advanced graphics made in Java ME than Flash Lite. Just look at the mobile games market.

Whatever the potential of SVG, I think WICD-M could help a lot as a base for future mobile browsers, when we now leave the "crippled at birth" WAP/WML technology once and for all behind us.

WICD mobile: MashLite?

(via CEO's Mobility Weblog)

The PC market is relatively consistent when it comes to methods for enabling of Internet-based information services compared to the mobile market, due to the complete dominance of Microsoft and due to the few providers of browsers (that anyway need to be IE compatible) etc. There are many things you could say about the negative consequences of Microsoft's dominance, but I don't think anyone can deny that consistency is a good thing for service providers.

Not so for mobile phones where there are several ways to mobilize services, both via the phone's native functionality, like SMS, MMS, email, browser etc, and via downloaded applications for Java ME / MIDP, Symbian OS, Windows Mobile or similar.

Pragmatically it's easiest to make services that rely on the phone's native functionality, and if the service needs some level of interaction then the phone's browser is a reasonable choice, as it's possible to achieve good consistency over phones without having to test on all phone models (which is practically impossible). This approach has been taken by e.g. SoonR, and tools like WURFL and similar help smooth out the edges.

Java ME / MIDP is completely dominating in after-market mobile application platforms, but is suffering from the many providers of Java ME implementations with different interpretations of specs and different bugs/features. One would think that Sun would some day realize that they need to become the only provider of Java ME implementations to secure a higher degree of compatibility, but when reading information originating from Sun it seems they still think Java ME is Write Once Run Anywhere, and the decision to make Java ME open source will not increase consistency, despite other values of open source efforts.

Java ME is certainly still a good choice, and often the only choice, if you need to access the phone's functionality, like the camera, audio, location, file system, PIM database etc, and if you need to display interactive information including graphics.

Of course the camera (both for photos and video) can also be accessed via native functionality as photos/videos can be sent via MMS or email to the service, yet there's really no interaction with the service this way. It's more like "send and pray", yet the use case is very easy to explain, and has been deployed by mojungle and others.

ShoZu requires a special application installed on the phone. As I mentioned in
Web 2.0 not for phones? ShoZu would gain from also supporting MMS/email transfer of photos.

Advice to those that want to get into mobile services:
* Select client solution based on whether you want to reach the whole mobile market or you can survive by targeting users of specific devices (and application platforms); revenue doesn't need to be less if you limit the scope, as e.g. corporate users will pay way more for services and applications than the average consumer would; also you can start with a limited scope and broaden later (like ShoZu did)
* For maximum coverage with no interaction with local phone functionality, use an SMS-based approach
* For services that need some level of user interaction and look-n-feel yet reach a very broad audience, use a browser-based approach
* For interaction with the camera, yet with no need for other service interaction, use MMS/email
* For close interaction with the service, including advanced graphics and access to some local functionality, use Java ME / MIDP
* For the most advanced and broad access to local functionality, yet where it's OK that only a smaller part of the market is accessed, use Symbian OS and/or Windows Mobile

Here's another note with a slightly different angle on the subject:
Internet leaders: Mobile is tough nut to crack | InfoWorld | News | 2006-10-20 | By Nancy Gohring, IDG News Service
I question the control of operators mentioned here. At least in Europe you can do pretty much what you want via the mobile network, yet the operator is of course always the middle man charging you for the transfer of SMS, data etc.

The CDMA camp has the recent years claimed cdma2000 (1X, EV-DO etc) is real 3G. It's been very clear at exhibits that Qualcomm and their customers think so, and this note therefor claims cdma2000 leads with 80% of the 3G market.

Korea was very early on deploying cdma2000 (in practical use before USA), and I was taken back when a business contact I visited in Korea claimed he had 150 kbps while I hadn't even tried out GPRS yet, so at the time I had effectively 9.6 kbps on circuit-switched. That was quite different from the statements of European leadership in mobile that the local "propaganda" claimed at the time.

I'm sure the UMTS/WCDMA camp will say that cdma2000 is not really 3G, but the key point is really that cdma2000 is used way more than WCDMA, and secondly it's been used way longer for content and information services.

Does that still mean it's true 3G? I don't know, and I probably don't care either. The value of technology is only in its use and applicability.

Does cdma2000 have a chance in Europe? I don't think so. Too much is invested in WCDMA.

CDMA2000 Providers Claim 3G Lead - Yahoo! News

I've found FierceMarkets' daily email newsletters to be excellent. They don't just quote news, but also provide brief commentary to the most interesting stories. Free of charge and with several different focus areas. Worth a spin.

Publications | FierceMarkets

Strategy Analytics believes so in a new report on the topic.

The brief summary mentions IMS to foster IM and presence, while it's actually today's popular IM services that will drive the need for mobile IM, also for corporate use. Closed-community IMS-based IM will be a very hard sell to anyone, except from infrastructure provider to mobile operator.

Interestingly it mentions a need and availability of low-cost handsets with alphanumeric keypads. That need will surely be more obvious for business use, where also corporate email etc will be handled by the same phone, yet also for consumer/casual IM an alphanumeric keypad would simplify and speed up messaging (not just IM).

It also asks the classical question "will mobile IM cannibalize SMS? Email?". Who cares really? A more important question is: "Will future consumers at all care about the information services operators provide, instead of the much more attractive, contemporary and useful third-party services?"

Time for Real-Time: Gauging the $2.4 Billion Mobile Enterprise Instant Messaging Opportunity

At least this video might give you that idea, or not.

It's in Swedish and with texting in Spanish or something, but I think you get it anyway.

The guy in the middle was voted the world's funniest man in Sweden this year. Not sure what other countries think about that award.

It's slow today...



YouTube - Future of cell phone technology

Rough translation:

Left guy:

"Yes, it's Göte"
Miscellaneous conversation

"It's the new Nokia, GHF C58 ... Mobile chip under the finger nail ... Ghastly expensive"

Middle guy:

"Yes, it's Örjan"
Miscellaneous conversation

"Ericsson VTH 535 ... Speaker chip in the ear ... Microphone in the nose ... Sickeningly expensive"

Right guy:

Farts...
"I got a fax"

Swedish humor at its best :).

1B shipped this year, totalling 3B phones on the market, and 1B of those have Java ME. Nice numbers for anyone in mobile application and service development.

Nokia and Motorola increased sales, yet at other places I've read both decreased revenue.

Then comes Samsung, Sony Ericsson and LG. LG was #4 earlier.

IDC: 1 billion phones should sell this year | InfoWorld | News | 2006-10-19 | By Nancy Gohring, IDG News Service

David Wood at Symbian claims Web 2.0 services can't be directly transferred to mobile phones. That's a fact of course, due to current browser functionality, display real estate etc.

Yet it gets a bit confusing when also Ajax is mentioned. Web 2.0 is about service types (user-generated content etc), not specific technologies. Of course social network services can and will be (en masse) transferred to mobile phones, but they will have to be adapted to the different feature set of phones (both in terms of limitations, as well as additional functionality like a camera and location).

Quote: One way that Web 2.0 companies can similarly adjust their services for mobile devices is by relying less on browser-based applications and more on small software clients that users can download onto their phones. "The browser will fade into the background,"
That's an interesting point, as e.g. a Java ME application doesn't have the interaction limitations a phone browser based service has. Traffic can also be better optimized by transferring data only when relevant. There are issues with this approach though. Despite me being a Java ME afficionado, I'm well aware that it's easier to achieve cross-phone compatibility via WAP 2.0-based services than via Java ME. Also, Symbian OS and Windows Mobile have less cross-phone compatibility issues than Java ME, but are on the other hand much less prevalent in phones.

ShoZu is mentioned as one such service where an application is used to accomodate the user interaction and communication with the service. I'm not 100% for the ShoZu approach though: Most users only want to submit photos, not edit them via the phone, and in such a case simply emailing/MMSing the photo would be sufficient, and much easier than installing a special application. My advice to ShoZu is then to complement its use of an application for more advanced users, with an email gateway for everyday photo blogging. There's no conflict really, just more users.

Andy Tiller at Cognima (that made ShoZu) notes the barrier to installing applications: Downloading a client is a huge barrier, ... But right now, it's the best option
Actually, on most phones it's better/easier to use MMS or email if it's only about posting pictures.

See my Comments on Mobile 2.0 for more on Web 2.0 on phones.

Experts: Web 2.0 doesn't copy directly to phones | InfoWorld | News | 2006-10-18 | By Nancy Gohring, IDG News Service

Still to consider a rumour, but Apple likely wouldn't take these steps just for the fun of it.

I'm surprised no one trademarked iPhone ahead of Apple.

In the trademark filing for iPhone: "handheld and mobile digital electronic devices for the sending and receiving of telephone calls, faxes, electronic mail, and other digital data; MP3 and other digital format audio players."

Apple Files Patents For iPhones - Yahoo! News

Industry Buzzing with Apple iPhone Rumors - Yahoo! News

According to a report from Kaspersky Lab the risk is especially high for Windows CE (as used in MS Smartphone, Phone Edition and Windows Mobile) and Symbian OS (as used in Nokia Series 60 and UIQ), as a software developer has open access to many parts of the system. That there are not many Windows CE viruses today is likely because it's hardly used in phones (relatively speaking). Symbian OS (via Series 60) is much more prevalent, but is supposedly also a more protected application environment.

Like on the PC side I believe viruses for just destroying things will not dominate, but rather such that generate money for the virus creators/distributors. That completely drives the PC virus "industry" today.

That was the case with the Java ME virus Red Browser, that generated expensive SMS messages. Hence not even Java ME is safe from viruses, but to a higher degree than Windows CE and Symbian OS.

Even so, Red Browser (being a typical Trojan) relied on the user's gullibility to download the application in the first place, and then accept Red Browser's sending of messages.

Windows CE, Symbian wide open to attack

This is probably the most technical note I've written so far. You are warned.

This slightly off-topic entry is intended to cover a subject that I think the Java literature gets all wrong, trying to abstract something that doesn't need abstracting. Rather it makes it "magical", while it's pretty down-to-earth when you take a closer look. As programming is a precise art, any sense of magic is completely out of place, even for beginners. Even more so when coding for Java ME, due to the memory and performance issues on phones.

A simple fact: Java uses pointers for pretty much everything. Sure, they are more type-safe and much more managed than in e.g. C and C++, where use of pointers is outright dangerous. Java also has a much cleaner syntax for object use.

In Java-speak it's called references, but frankly it's all about pointers, so I use that term below.

When you write "[class] [name];" you don't declare an object. You are just declaring a pointer to an object. [name] can point to any object of type [class] as well as derived such.

It's first when you do "[name] = new [class];" or "[name] = [object];" that you actually assign [name] the pointer to a specific class instance (= object).

This also means a statement like "somefunction(new [class]);" makes complete sense, as what you do is allocate an object on-the-fly and then pass its pointer to the function.

As the pointer is passed to the function you can also alter the object within the function, and changes are normally retained when exiting the function. Not in the above implicit case though, as when the function returns there's no variable pointing to the object any more and the object will hence be removed.

"null" serves as an indicator that a pointer variable hasn't been assigned any pointer to an object. It can also be used to de-reference objects. Always a good habit when objects are no longer used.

All objects are stored on the heap, and once there are not live pointers to any object they can be removed by the garbage collector.

Another area of possible confusion is arrays of objects. E.g. "[class][] [name];" only allocates a pointer variable to a possible object that's an array of pointers to possible [class] objects. When you then do "[name] = new [class][10];" you don't create an object with 10 instances of [class] but just 10 pointers to objects of type [class]. It's first when you do something like "[name][4] = new [class];" that you actually create an object for the array.

The only exception from the above rules is primitive types (e.g. int). That's also why there are container classes to make them behave as real classes and objects.

Another area that might seem magic is the creation of a class instance. What happens is that space is alloced for the object on the heap, variables are initialized with default values (as per the class definition) and the appropriate constructor is called. If there are several constructors, the one with the right argument types is called (overloading).

Other object tidbits (and suggestions for improvements of the Java language):

In e.g. Visual Basic, PHP etc a string is considered a primitive type, which makes text management very easy. In Java you can concatenate strings with "+", but apart from that a String object is like any other object, which is evidenced by e.g. the less than intuitive method for comparing strings "str1.equals(str2)". It hadn't hurt if e.g. "==" also worked for strings, as it's used so much. Also, String objects are immutable (constant), so appending strings to a larger string is very inefficient and memory-consuming. StringBuffer comes to the rescue here, but to me the string handling in Java seems a bit too manual for Java to be considered a high-level language. The benefit is that you can get the efficiency you want.

Any class can have a "equals" method that should implement an appropriate comparison of similar-typed objects. Considering this, it's kind of strange that the "switch" statement only handles values of integer type. Rather it should use the equals method to allow e.g. strings and even more advanced objects.

This is an interesting new VoIP service that uses SIP for communicating VoIP via Wi-Fi. As such the transfer between Truphone peers is free of charge, while you get lower charges on long-distance calls to "real" phones, as the communication is transferred over the Internet and converted to PSTN locally.

My concern is that there are still not that many Wi-Fi hot spots, and of course the phone needs to have Wi-Fi. Truphone currently supports the Nokia E and N series. The client software is for Series 60 as of now.

Welcome To Truphone - Mobile VoIP has arrived

Last year almost all remaining European ODMs disappeared. Now it's time for the European phone brands to realize it's time to go. Nokia and Sony Ericsson are not affected (both have seen good growth this year), but on the other hand most of their phones are made in the less expensive Asia anyway. For Siemens mobile phone division (that was acquired by BenQ last year) and Philips' ditto it hasn't gone as well. Of course both Siemens and Philips are very strong in other markets than mobile phones, so from their point-of-view this is for the best.

Philips pulls a Siemens, sells phone biz to Asian firm - Engadget Mobile

Mobile Opportunity hosts this week's CotM. No carnival theme this time, just good reading.

Mobile Opportunity: Carnival of the Mobilists #49

The jury is still out on whether service providers will bother about .mobi and the guidelines stipulated by the associated company dotmobi, but that doesn't stop domain registrars and tool providers from seeing an opportunity to generate more revenue this way.

dotmobi has published guidelines called Switch On! that very briefly describes the guidelines for .mobi-compliant site.

dotMobi open standards for mobile content adopted by top hosting and developer companies - News Wire - Mobile Europe

As the hype factor has now vanished from 3G, consumers look more at what it actually costs to use, and according to this note the interest has dropped since last year due to the continued high costs.

Even though I have a brilliant subscription when it comes to voice, SMS and MMS I still pay $1.5 per megabyte of data via 3G. That can't be called inexpensive, yet the operator in question is still one of the better ones in my region when it comes to data cost. When surfing the operator's portal it doesn't cost me anything, but everything on the portal costs, including reading news etc, so I obviously go elsewhere for that.

As I noted before in A comment on Mobile 2.0, it must be flatrate.

Hanis Harun, Global Director, TNS Technology, comments; “Given that cost is such a key obstacle to the adoption of more advanced mobile services, mobile operators must provide pricing regimes which are fixed for unlimited use, transparent and affordable.
Hanis adds: “Cost is the quick fix and should provide fast usage uplift especially amongst those services already found interesting by consumers, such as songs downloads and realtime TV.”

Fewer people want 3G than a year ago - News Analysis - Mobile Europe

This longish note argues that the industry makes services to drive their own business rather than satisfying what consumers want or need.

I say: So be it, and let third party make the services that consumers actually use, based on what can be done via the network and with the available phones (and that's a lot, yet could be less expensive), and the serves as the key loyalty owners for the consumers. That's already happening, and will continue to decrease the value of specific network operators and arguably also phone brands. It's up to the telecom industry to do useful things, or not.

Interestingly when we move to increased use of information access on phones it's the content and service providers that consumers get hooked on.

When e.g. 3 now provides access to MSN from mobile phones, it's actually MSN that's dragging in the consumer, not 3. 3 doesn't go empty-handed though: They sign up the consumer for a longer time. Is that what the operators have left: artifical loyalty through long subscriptions?

Applications development – Power to the people - Magazine - Mobile Europe

World Wide Web Consortium (W3C) has released what they call Web Integration Compound Document (WICD) Mobile 1.0, that's an aggregation and subset of specifications being used on the "normal" Web.

It looks promising. It covers what we are used to from PC-optimized web sites, yet with tweaks for mobile devices. It even specifies which bitmap, audio and video formats need to be supported.

What I didn't like so much was that XHTML and ECMAScript is required rather than "street" HTML and Javascript. That means web sites always need to be specifically designed for WICD. I think we've had enough of that already, so browsers need to support the street dialects as well.

WICD Mobile 1.0

(via CEO's Mobility Weblog)

Gartner has provided a new report on the smartphone market that claims an increase in units of 57% since the same period last year. I hope the report provides a good definition of what a smartphone is, as it gets increasingly hard to tell smartphones and other mobile phones apart. Day to day it doesn't matter, but when justifying statistics and estimates it does.

This paragraph is striking in several ways:
Nokia owns 42 percent of the combined PDA and smartphone market, compared to single-digit market share for Research in Motion Ltd. (RIM), Motorola Inc. and Palm Inc

I know Gartner uses the criterium "phone running Symbian OS is a smartphone", which can be argued, but means all Series 60 and 80 phones are considered smartphones. That also means there's a lot of Nokia phones that apply as such, even when they are sold as mainstream phones.

Also very interesting is how little marketshare RIM has. We are talking the PDA/smartphone market here. If we instead look at the total mobile phone market, RIM sales figures become invisible. Based on the media frenzy you would think RIM is a leading provider of ... at least something. The reason RIM gets so much attention every time they release something is probably because it's the choice of managers and journalists, which is a pretty small part of the market.

That doesn't mean RIM's market is a financially unattractive one, as the total ARPU is pretty high compared to mainstream phones, as the server and subscription costs add to the revenue, but it's clear RIM doesn't have exclusivity in the corporate email market. Nokia could easily knock RIM out if they wanted to. Let's see what happens with the Nokia E series.

Nokia leads smartphone vendors - Yahoo! News

You might have seen the addition of an Application item in the top menu. Abiro partners with Clickapps to provide all kinds of applications for mobile phones and PDAs.

I've also launched my first commercial Java ME application at Clickapps. More applications are on the way.

It seems navigation is now the supposed killer app for 3G, not video as many analysts claimed a year ago, but I don't see any apologies from anyone. The only issue is, there are no GPS handsets, so we need to get such first, or?

Why not start with providing services that use cell ID or similar. That would work with all existing phones, and would be enough for e.g. restaurant/bar finders, etc. Would be a nice complement to Google Maps etc.

I get a bit anxious whenever analysts talk about new services that "just" require new phones and new infrastructure, seemingly without understanding the costs and times involved and the big risk that it will bomb completely.

This note also indicates the industry is still trying to sell pure technology to consumers ("3G anyone?"). From a consumer's point-of-view 3G is somewhat faster, but still just as expensive per megabyte as GPRS etc. Advice to the industry: Fix flatrate 3G before you fix GPS etc.

Surprising New 3G Killer Application

Interestingly WiMAX doesn't support devices that are moving, but will at the end of the year. That's obviously critical for use in mobile phones.

Also interesting is who Nokia will address with its upcoming WiMAX base stations: broadband operators. Does this mean Nokia doesn't expect traditional telecom operators to take the WiMAX route, and that we are looking at a major shift in the market, where broadband ISPs will take over the bulk of wireless information traffic? In any case I believe telecom 3G operators will experience a real pressure from broadband ISPs down the road if many phone manufacturers provide WiMAX handsets. Additionally this means Ericsson, Nokia and other infrastructure providers will experience pressure from Cisco, Nortel etc as you don't need much of traditional telecom infrastructure in networks using WiMAX. It's "just" an onramp to the Internet.

I'm one of those backwards people that don't think short distance Wi-Fi hot spots will ever make much impact on the use and economics of telephony and data, despite Skype phones etc, but WiMAX is very likely to.

Nokia expects to sell WiMAX mobile phones in 2008 - Yahoo! News

Obfuscating Java code (including Java ME ditto) is critical, as it's otherwise very easy to decompile Java bytecode and that way reverse engineer the application. The core function of obfuscation is to rename all identifiers to something shorter and less obvious, but also other operations are done, in part complementing the optimizer in the compiler.

What's maybe less known is that due to the renaming and general optimization the code also gets much smaller. My applications easily become half the size with the "toughest" Proguard settings activated.

Proguard is included in NetBeans and it's very easy to set different levels of obfuscation, so there's no reason to not use it.

More in the article.

Obfuscating Your MIDlet Suite

From the title this sounds like exactly what all developers need, but it doesn't really provide a solution to the fundamental issue of being able to run the same compiled application on all Java ME / MIDP implementations, something you can do on most other application platforms, Linux excluded due to the different UIs. Yet, the steps described here at least takes you closer to being able to deliver one set of source code per application, with embedded conditions depending on phone model and set of phone features. Finding those conditions out remains though.

E.g. this statement shows where we are at: You'll need a thorough knowledge of the specific behavior of each device model.
That's impossible, even for large developers, as new handsets with even more different behavior and bugs are released each day.

A solution like J2ME Polish helps a bit, but only in terms of the UI.

I try to solve this in the following ways:
* Use MIDP 1.0 functionality if that's acceptable for a certain desired functionality. MIDP 2.0 implementations are clearly more buggy than MIDP 1.0 ditto, and MIDP 2.0 phones also support 1.0, broadening the scope of the application.
* If that's not possible (e.g. if MIDP 2.0 features or a newer JSR are required for the fundamental functionality of the application): auto-sense that the feature exists and if not give a self-explaining message to the user or try to work around the feature lack. The default error reporting simply sucks: Messages like "can't install", "can't run" etc are completely useless for both the user and the developer, so it's better to catch and report possible issues in the application.
* Test on a good spread of phones, and be prepared to handle issues from customers that try out the application on phones you haven't tested on.
* If nothing else helps, use conditional compilation. That's better than having separate source codes for different phones, as that will completely wreck later maintenance.

To get this straight in the future there has to be much tighter testing of KVMs and KVM integrations. The best way for a manufacturer to do this is to standardize on one KVM provider and use the same application platform on as many phones as possible. Many manufacturers bring in more than one KVM provider for the sake of price/feature competition, but from a technical point-of-view it's detrimental.

Also, as I've mentioned in earlier posts, the best would be if Sun took over the delivery of KVMs. That would fix one major issue with Java ME / MIDP: different interpretations of specifications and different bugs. If there's only one implementation, there's also only one set of interpretations and bugs.

Automate Your J2ME Application Porting with Preprocessing

Not about mobile, but all the same earth-shattering news.

YouTube is not profitable, is one of several services providing video uploads and rating, has lots of copyright issues, but it's the clearly most popular such service, and the latter seems to be value enough for Google.

Some call it an eBay/Skype-like acquisition. In the case of Skype, eBay could have acquired a more low-cost company with a VoIP solution (Net2Phone?) if it was only about adding value to the trading solution. At first look it seems eBay paid a huge over-price, yet as the buying companies arguably have more money than creativity and time, acquisitions still can make a lot of sense, provided the acquisition cost is within reason. Both Cisco and Microsoft are to a large extent based on acquisitions, yet typically paying a way lower price for tech companies that otherwise would die a slow death due to lack of business competence. If anything, new Web companies seem to have a lot of business and marketing sense, at least when it comes to being acquired.

You may read Web 2.0 on overdrive for some of my general thoughts on the matter, written before the acquisition was known.

BBC NEWS | Business | Has the dotcom boom returned?

BBC NEWS | Technology | Blogosphere probes 'GooTube' deal

Helen Keegan at Musings of a mobile marketeer provides this week's Carnival of the Mobilists with the strange and wonderful from the world of blogging about mobile.

Musings of a mobile marketer: Carnival of the Mobilists No 48

In the UK (and also worldwide) traditional ringtones (monophonic and polyphonic) are declining in popularity. Verisign recently sold 51% of Jamba (a leader in ringtones) to News Corp, which also indicates the heydays are over at least in mature mobile markets.

icCheshireOnline - The days of Crazy Frog and Co are numbered

As there's a Web 2.0 there has to be a Mobile Web 2.0 right? At least that's what many think, so I of course need to provide some mind-numbingly ingenious views on this topic as well.

First off, I don't think so much in terms of the traditional Web, that to me means "services accessed via web browsers", as a mobile phone has many other means to communicate and present information. Therefor let's start with removing the "Web" part, so we have Mobile 2.0.

Of course media and analysts are all over these kinds of terms, as they seem to explain a lot, but they only mean what they contain, and what they will contain is based on what becomes used, not what's being standardized or what's the "best" (fastest, least code, most hard to pronounce) technical solution.

Hence, below I try to focus on things I believe will become used a lot in the era of Mobile 2.0. A rough thought-umbrella for Mobile 2.0 is "When information services became broadly used on mobile phones". Everything before this has been experimentation and very often misdirected and consumer-ignoring such.

Mobile phone: voice device --> also information and multimedia device
Applications: embedded --> downloaded or bundled (games, messaging, utility etc)
Applications: standards-based --> market-driven (and often tied to services)
Idle screen: wallpaper --> information access
Browsing: WAP --> Normal/Full Web
Messaging: SMS --> IM, Email
Messaging: no use of MMS --> MMS for media sharing
Messaging: no IM --> full access to popular Internet services
Camera: for wallpaper --> for media sharing
Operator: service provider --> transparent bit-pipe
Operator: walled garden / operator portals --> access to the full Internet
Payments: SMS (phone bill) --> Online (phone bill and account)
Payments: whatever --> non-paid service registration (membership) and pay-as-you-go or monthly flatrate
Phones: new phones for new services --> use installed base for new services (see Applications above)
Location: not used --> used for maps, directions, local information
Subscriptions: per-minute/megabyte --> flatrate

Also, of course the user-generated and widget-related aspects of Web 2.0 will move to mobile phones, and requires no new technology and no new phones. It's already all there. You already see it in the shape of ShoZu, mojungle etc.

In my previous posts Web 2.0 on overdrive and Has OMA lost its mojo, it's painfully clear the traditional telecom model of going through a multi-year process to standardize new phone features has to go. Nokia's Wibree effort shows that even the players themselves are fed up with over-specified misdirected solutions, and instead go for what's useful now (and not years from now). 3's adoption of a Java client for MSN points in the same direction, etc.

Update: For a possibility to prove me completely wrong you can visit the Mobile 2.0 conference in San Francisco. The conference is inexpensive ($45), but stay away from the hotel's special conference (read: extra expensive) rate.

Update 20061008: Comments on the as yet rudimentary definition of Mobile (Web) 2.0 at Wikipedia:

a) Harnessing collective intelligence through restricted devices i.e. a two way flow where people carrying devices become reporters rather than mere consumers

Could also be said like: Web (2.0) services accessible via mobile phones, making use of the additional functionality of mobile phones, like multimedia recording, always-on, real push etc. The collective intelligence bit I consider arguable. There's no so stupid a thing as a crowd. Also, we need to be careful about saying mobile phones are restricted. Mobile phones are actually much better at multimedia recording than PCs. A device's capabilities is not just reflected by the UI.

b) Driven by the web backbone – but not necessarily based on the web protocols end to end

There's no such thing as a "web backbone", only the Internet. If you don't even use web protocols (read: HTTP) then you are clearly on the pure Internet. Not that it matters. The key thing is to make useful services.

c) Use of the PC as a local cache/configuration mechanism where the service will be selected and configured

Seen worldwide, many more people have their own mobile phone than a PC, and even more so when we talk younger people, so it's obvious that configuration should be possible via the phone as well. Also, it's only temporary that we have to use a PC as a download/cache device, due to the huge difference in traffic costs between broadband and mobile networks, but that will have to change.

At many places I've read about a term called Voice over Instant Messaging (VoIM). VoIM in practice means "VoIP used in the context of an IM service". It's definitely still VoIP.

Let's go through some basics:

VoIP = Voice over Internet Protocol = transferring voice (or rather digitized audio) over IP-based networks, one-way or both ways

As Internet Protocol is the most used network protocol, on the Internet and in corporations, in homes etc, VoIP can be transferred pretty much on all networks in existence. That leads to a superior interoperability without a need to convert when moving from the Internet or WAN to LAN, LAN to WLAN etc. Of course you need to convert when moving to the normal telephony network, but that will hopefully go away in a few years (or millenia).

That's what Skype, Yahoo!, Net2Phone, MSN, broadband ISPs etc are doing.

Within corporations an older protocol called ITU H.323 is sometimes still used for VoIP, but the standard protocol for the future is clearly Session Initiation Protocol (SIP), that's also been adopted for triple-play within the IP Multimedia Subsystem (IMS) standardization. Similar to how you set up a call on a normal phone SIP takes care of the calling functions. The audio is then transferred as packets via Real Time Protocol (RTP).

Skype uses parts of the above, but as the traffic is encrypted outsiders can't actually see what's going on inside the network packets. This serves two main purposes:
* Providing a secure framework for voice, video, chat etc, minimizing the risk of eavesdropping etc.
* Providing a walled garden, leading to a virtual network where only Skype technology can be used. E.g. to make a phone that houses its own Skype client you need licensed information and technology from Skype.

SIP is likely to overthrow Skype and similar proprietary solutions over time, not because of some rosy notion that standards need to win, but simply because everyone else will do SIP, including telecom. The interop gains are that great.

VoIM will of course stay (simple terms always stay, like digital audio players are still called MP3 players, even if they support much more than MP3 that's not even a proper term), but I hopefully gave you a different angle on the subject.

This is one of those "my friend's cousin's dog told me" reference entries.

Juniper Research has issued a new report on mobile gaming.

Casual and quick-to-learn games rule, and the spread in different age and gender groups are increasingly evened out.

Quotes:
[Mobile games] are no longer the poor relations of console and PC games. They are a different family of entertainment products with its own family characteristics.
over the next three to five years mobile games offer almost as much revenue earning potential for service providers as mobile music and mobile TV.

QuicklyBored » Blog Archive » Casual And Female Gamers Drive Market

As this was a give-away at the Java conference 1998 it might not be seen as anything serious, but the design of the Java Ring, that's based on an enclosed MPU/CPU called iButton, running software compatible with Java Card 2.0 it's actually a good start for better and more secure banking, authentication etc.

If banks would use Java Rings or smartcards maybe we would be less hazzled by phishing attacks. Latest news in Sweden is that banks will take increased action against phishing ... by not paying out money to those that has lost any. Their defence is that customers might start faking phishing attacks and get paid money they shouldn't have. The banks won't actually mend what needs to be mended. Thanks banks!

Mobile phones use smartcards and could be used as secure identification devices, yet we still use cards with magnetic stripe for our financial services. Can anyone explain the logic in that? Is it just that banks are conservative? Banks trust banking via HTTP/TLS, so when will we see fully-featured mobile banking and payments?

(via CEO's Mobility Weblog)

Update 20061005: Found this older story on the same subject. It's still quite valid.
Opinion: Instant Messaging vs SMS/MMS

Paul Golding at Wireless Wonders ponders on whether Mobile IM will fly and if not why not. I wrote a comment that might not get published, so here it is (me quoting myself). What I try to bring across is: Does it matter if Mobile IM is not as convenient as PC IM as long as it's a generally more convenient way of communicating from a phone?

I'm not sure your arguments matter if you consider that the users are much more likely to be beside a mobile phone than a PC, hence can be contacted anytime. The end-user results should be respected of course, but the reasons might be different from the obvious ones.

What I don't understand is why mobile IM would be worse than SMS:
* messages don't fill up any inbox
* you write and read messages from the same UI
* IM can add functionality like sending photos, files etc
Hence this can be a matter of adoption time. SMS took a long time to be adopted too.

Also, I don't think the UI limitations are that bad as SMS has the same issues with a crappy keypad and lack of real estate for reading messages. I wish more phones came with alphanumeric keypads and had a landscape display (good also for videos and photos), even in mass market phones.

We tend to repeat the same mistakes in this industry when talking new phenomena:
* We compare with ourselves, yet we are not in the key demographic.
* Adoption takes time. SMS took a very long time to become broadly adopted, so why do we expect mobile IM to be so over-night?

It doesn't really matter if 3 fails in its pitching of MSN, as the promotion can be considered general ("we stick out, so get a sub at 3, rather than at X") and they acquired a "plug-n-play" solution from OZ. Sure, the server must have cost some, but that's nothing compared to the possible increased revenue they can get from long-time subscribers.

Wireless Wonders: Mobile IM - is it really IM?

This article is about ways to use SMS as a means for an improved banking experience, for providing feedback to the bank, check account balance, authenticate the user, be alerted when things happen etc.

Most banks don't even support sending feedback to the bank via SMS.

The banks that have used SMS for authentication have experienced that the ROI is quick, as the amount of fraud has decreased considerably.

There's not much said about mobile banking via WAP or similar.

It's interesting, and disillusioning, how slow the adoption of mobile technology still is in certain areas, while Web technology is "everywhere" including for banking, despite mobile phones being much more prevalent than PCs, and a mobile phone is always with you while a PC is not, etc.

160Characters Association

Web 2.0 is about user-generated content and information mash-up (via widgets). That means there's very little for the service provider to do except get the service up and somehow get users interested in posting on the site and/or use the mash-up widgets. For this to succeed being first is required, as those that come a bit late with the same idea are lost, unless they provide an edge that others don't provide. The benefit for the service provider is of course that the cost over time is very small. Media is very interested in writing about such services, so there's no advertizing cost for the services that are first. The drawback is that the later "me-too's" get no media coverage at all.

Here are a few examples of recent services that are already hugely popular. The lead time from inception to mass popularity is very short for the most popular services. We are talking months, not years, so if you are even a month late with your service you might lose the game.

As most such services don't use advertizing there's a question how they will get any revenue over time. In the beginning I'm sure investors are very interested in this, as Web 2.0 is the hottest topic around, but they might get a bit cranky later if hard cash doesn't show up.

WidgetBox provides lots of free Widgets for inclusion on web sites. Widgets are provided by users.

Google will do the same according to this announcement.

Ning provides ready-to-go social network services. Will a Ning-based service become as popular as YouTube etc? Of course not, as tons of other sites will use the Ning (or similar) service.

Digg aggregates news tips from users, hence is not really a news service in itself. Users can vote for the best news. Interestingly you can use WidgetBox to aggregate Digg and other news.

All in all, the most important thing that counts for Web 2.0 services is speed, and adaptation over time. As the content itself is the users' responsibility, the company behind the service can spend all time and money on the service "engine", which is inexpensive compared to having a staff of news editors etc.

I sense we are heading for a new "IT bubble", unless investors can push such services to provide means for getting revenue.

The alternative is to become acquired by a more traditional company that needs to spice up its offerings (see e.g. News Corp and Jamba/Jamster), which has the benefits of not requiring any profit before or after the acquisition, yet lots of money for the founders.

The mobile spin on this is of course that this will also be available via mobile-adapted sites. Meanwhile you can check news via wap.abiro.com / Mobile News.

I actually had planned to launch my own widget aggregation site (also with my own widgets, and for mobiles too) before I heard about WidgetBox etc, but that doesn't sound like the best thing to do right now.

Update 20061009: The second part of the interview with David Gosen is now up, so here are direct links to both parts:
I-play's David Gosen - Part 1 - Interview /// MobileIndustry.biz
I-play's David Gosen - Part 2 - Interview /// MobileIndustry.biz


David Gosen is CEO at I-Play, a major provider of mobile games.

Quote: Over the last 25 years, 250 million consoles and handheld devices have been sold, but every year, 800 million mobile phones get sold.
Of course that doesn't mean there are 800M new people using phones every year, but that the market potential is huge for mobile games, and the technology advances fast. Very fast all mobile phones become gaming-enabled (read: support Java ME).

Hopefully the UI of future phones will be better adapted to gaming needs (analog joystick etc), yet still remain optimized for telephony and music.

Mobile must not make same mistakes as consoles, warns Gosen - News /// MobileIndustry.biz

QuicklyBored » Blog Archive » David Gosen On Making Mobile Games

For those with a strong brand, or the ambition to build one, there's another possible route: Sharewire.net. Sharewire is about providing a shopping window on your own site. I sense Sharewire have more buying options than clickapps etc.

I've signed up to providing clickapps via my site, which has the added benefit of also offering tons of other applications as well as my own.

J2ME Forums has a list of distributors. This list is updated by forum users.

See also Venues for selling Java ME applications.

I did it: I got tricked into getting a new subscription via a telemarketer. I still wonder how I could be so stupid, as I normally hang up very quickly on such calls.

They recorded my voice and then mean that’s a binding contract. I still haven’t got a clear answer from a lawyer whether that’s actually true. The only response I’ve received is that what’s agreed to is binding. Of course the telemarketer didn’t mention anything about a grace period, so seemingly there’s none. A consumer automatically gets a grace period of 14 days in my country, but not so for companies.

What made matters worse is that the guy I spoke to completely misunderstood my requirements: I needed an account with free SMSs and MMSs and a low rate on data. I instead got a subscription with very expensive SMS, MMS and data, simply because that was what he offered, but he explained it as if it was in compliance with my requirements. Voice I didn’t care about, as the sub and the phone were intended for testing Java applications. Despite this they can’t accept to cancel the subscription, and of course my specification was never part of the voice recording, so it doesn’t help to refer to that.

They will cancel my previous subscription, which means I will have to pay the remainder of that subscription, adding to the cost. Still, without getting anything beneficial to me.

They can’t be contacted for a discussion: The operator refers to the telemarketing company, the sales guy refers to customer support, and customer support refers to a binding contract. Even though the subscription is in my name, the operator doesn’t allow me to cancel the subscription. Also, the telemarketing company never responds to e-mail. Probably because that could be used as evidence.

I will pay roughly $1700 in total for a subscription and a phone I don’t need. That’s not the worst part (even though $1700 for nothing sucks). The worst is my lack of judgment in this case. That still gives me cold sweat.

When I added up the cost for the phone over time I will actually pay full price for that, despite I get a binding subscription for 24 months. The nightmare continues.

A few conclusions:
* Telemarketers are ruthless, and their incompetence hits back on you.
* Companies have no implicit cancelling rights when buying things.
* Signing up to a new subscription via the phone is a way too complex thing to do. Misunderstandings are mandatory.
* The only sensible response is “Thanks, but no thanks” and hang up the phone, ALWAYS.

After so many years of fuzzy specifications, non-working implementations etc I kind of feel Bluetooth should get some credit, but it doesn't seem Nokia and its partners want it that way.

Wibree is like Bluetooth a shortrange radio technology for primarily device accessories. It's said to complement Bluetooth, which is a nice way of saying "is intended to replace it over time", as the range and data rate are the same, yet Wibree is less power (10 times) and space consuming. It can use the Bluetooth antenna etc. Of course, phones need to support both for backwards compatibility reasons, but not necessarily peripherals.

Quote: Wibree technology would eventually add a few cents on top of current prices for Bluetooth chips

Quote: Bluetooth has inherent power limitations because it includes a fixed packet-size and frequency-hopping technology

Even though not said, of course headsets would also gain from Wibree, to increase the time between charging.

Zigbee is similar to Wibree and also wants a piece of the accessory connectivity pie.

Nokia Announces Wibree Wireless for Smaller Devices (MobileBurn)

Nokia Develops New Short-Range Wireless Technology - Yahoo! News

Digital Media Europe: News - Nokia introduces Wibree

Nokia unveils Bluetooth rival - Yahoo! News

'WiBree' Standard To Challenge Bluetooth - Yahoo! News

Sun's version is not very detailed (compare with the one at J2ME Polish) and the filter setting is uncomfortably unsorted, but could still be useful as a possibly more updated second opinion to J2ME Polish.

C. Enrique Ortiz indicates this list was recently updated. It must be updated daily or at least weekly to be accurate, so maybe it's not so up-to-date after all. Also, I didn't find any way to download it as an XML file or similar, which would have made it practically useful.

I've posted proposals for improvements.

Jave ME Device Table

(via CEO's Mobility Weblog)