Archive for November, 2006

Is your application CUP'ed?

Thursday, November 30th, 2006

If your application doesn't provide CUP, or
“convenience, utility and productivity”
, then you must go back to the drawing board…

ceo

Daniel on The Three Halves of Seamless Mobility

Thursday, November 30th, 2006

A great piece by Daniel at the Mobile Enterpise Weblog — see The Three Halves of Seamless Mobility

Daniel provides a good historical background, talks about the split we currently have between voice and mobile, and other walls. I would like to add to the list of walls the “enterprise vs. consumer-space” wall; as personal handsets make it into the enterprise world, such wall must also come down…

ceo

Hot Areas in Mobility (to follow and be part of)

Thursday, November 30th, 2006

There are plenty of areas in mobility yet to be developed to its fullest potential. Below is a list of some of the “hot areas in mobility” to follow, or even better, to be part of and make a difference – there is plenty to innovate still:

  1. Mobile advertising (web-based, local/native-based)
  2. Mobile payments (ordering, payments, coupons, SMS-based, contactless, …)
  3. Mobile directories and 411 (local information, merchants, …)
  4. Mobile search (quick access to relevant data, traditional and new ways)
  5. Mobile gaming
  6. Mobile messaging (from IM to email, from text to video)
  7. Mobile-and-Multimedia in general
  8. Location-based Services
  9. Advanced User Interfaces (including voice integration, navigation, and Widgets…)
  10. Content sharing (photos, events, …)
  11. Mobile Social Software (from sharing, to messaging, to virtual communities)
  12. Power! (better sources for power)
  13. Content adaptation (better ways to manage/target/adapt Web content for mobile handsets)
  14. Common/single sign-on (common identification, authentication, authorization across the mobile Internet/Web; see Identity and Mobile)

Other:

  1. Smart notifications and reminders (based on user's mobile context)
  2. Backups (keep data safe, off the handset)
  3. Device management (this is key for enterprise adoption: application, access control, licensing management, etc)
  4. Education, translations, tourist-related information, while on the go
  5. Mobile banking
  6. Mobile polls and surveys

Join the bandwagon… Have other hot areas? Leave a comment!

ceo

Open Mobile Terminal Platform (OMTP) Hardware Requirements And Defragmentation, Trusted Environment Spec

Thursday, November 30th, 2006

The Open Mobile Terminal Platform (OMTP) forum, an operator-sponsored forum, has released a set of guidelines for mobile terminals such as PDAs and smartphones. The purpose of the guidelines is to minimize fragmentation across handsets.

The guidelines OMTP Hardware Requirements And Defragmentation, Trusted Environment (PDF), defines a list of requirements for a trusted environment, as defined by the OMTP Hardware Working Group. The document has “a general objective to help in defining terminal requirements and to allow development and deployment of new services as well as de-fragmenting secure requirements offered within terminals”.

From the OMTP Hardware Requirements And Defragmentation, Trusted Environment document:

  • “The User Equipment (UE) is a handheld, battery-powered electronic device that provides voice and/or data communication services to an individual user.
  • The UE may optionally provide data storage and offline information processing capabilities for the user.
  • The UE generally contains one or more microprocessors, volatile RAM and non-volatile storage that are electronically accessible to those microprocessors, and the necessary RF electronics to communicate via a standard wireless telecommunication network such as GSM or UMTS as well as interfaces toward (U)SIM.
  • The UE may also be capable of communicating over RF or IR interfaces that are not part of a standard wireless telecommunication network (e.g.; Bluetooth, IEEE 802.11, IRDA).
  • Typically the UE will incorporate a speaker and microphone that allow a user to conduct voice communications, but these facilities may optionally be provided via wired or wireless interfaces to a separate headphone and microphone.
  • The UE may contain a digital display, a keypad and various other buttons, a slot for removable non-volatile media, a digital interface port, a camera, a GPS unit, or other consumer electronics features.
  • The microprocessors within the UE execute software that implements various features of the UE, usually including the communications protocols appropriate to the wireless telecommunications network.
  • The UE boots up by first executing software resident in non-volatile memory, but may thereafter execute software from volatile RAM.
  • The same microprocessor may execute both telecommunications software and applications software that is not related to telecommunications.”

The document defines requirements for (U)SIM, debug port, mobile device ID, DRM, booing, binding and flash updates.

The OMTP forum currently consists of Cingular Wireless, Hutchison 3G, Orange, SK Telecom, Telecom Italia, Telefónica, Telenor, T-Mobile and Vodafone, AOL, Ericsson, Freescale, Motorola, Nokia, and Spansion, and other participants from all parts of the industry; including Application software, hardware and the OS space. The OMTP is operator driven.

ceo

Mobile data consumption is about access to relevant information

Wednesday, November 29th, 2006

Read via MocoNews that Telephia and ComScore revealed that on mobiles more people like to access weather information, while on the PC it is about searching

Let me tell you why I'm not surprised with these results… and why this validates one of the main usage patterns and characteristics of mobility…

First, the above results revealed that in general, both in mobile and desktop, search is king. The differences are a result of different usage patters, where in mobile people search for specific types of information, vs. on the desktop where it is about search in general.

Besides its main purpose of “communicating with friends and family (and co-workers)”, the mobile handset is about finding relevant information, while “on the go”. As previously mentioned, it is about finding specific snippets of information that is needed “now”, and typically related to an event while on the go. These are data snippets such as “what is the time”, “the local weather”, and “places in your area”, or access to other information related to the person's mobile context.

Consuming information on handsets is not the same as on the desktop or even a laptop, and it is about relevancy. Please note that relevancy is not only about finding specific information of interest but also has an impact on how information is organized and presented to the user.

So kids, the word of the day is relevant, as in relevant based on time, location, and other personal preferences or characteristics “surrounding” the mobile user at a specific point in time.

Note that one of the MIDP3 upcoming features is support for “idle screen”, which is great, and is perfect to bring relevant information to the user while the handset is “idle” – think Widgets…

ceo

Mobile Marketing Association Best Practices Guidelines

Tuesday, November 28th, 2006

The Mobile Marketing Association has released the latest version of their Consumer Best Practices Guidelines for Cross-Carrier Mobile Content Programs (in PDF format). The guidelines include information on:

General Conduct
Advertising and Promotion
Opt-in
  Standard Rate Programs
  Premium Rate Programs
Help
Opt-out
Subscriptions
Chat
Customer Care
  Spending Cap Limits
  Bill Face
Word of Mouth Marketing
Content Specific Guidelines
  Alcohol and Tobacco
  General Content
Glossary

ceo

[Via MocoNews]

Carnival of the Mobilists #55

Tuesday, November 28th, 2006

Checkout Eli Dickinson's Carnival of the Mobilists at FierceDeveloper
Posts by Mobilists including Ajit, StayGoLinks, Russel Buckley, Eli, Mike Rowehl, and many others…

ceo

Sony Ericsson releases package for UIQ 3 based Web Services

Monday, November 27th, 2006

From the Sony Ericsson press release:


“With the new Web Services for UIQ 3 package released today, Sony Ericsson gives developers an easy solution including guidance on how to access remote services over the internet on UIQ 3 phones using an open XML (eXtensible Mark-up Language) protocol called SOAP (Simple Access Object Protocol). By combining the open-source gSOAP toolkit with a new developer tutorial and code samples from Sony Ericsson Developer World, developers are provided with a simple API that enables them to concentrate on the application-essential logic instead of protocol specifics.”

Download the Web Services for UIQ 3 tutorial package, from the Sony Ericsson Developer World portal and click on Docs & Tools -> Tutorials.

ceo

The 10 principles of Assembly Java

Monday, November 27th, 2006

A good compilation of tips by Mihai Preda's of the The anatomy of a project weblog. These are tips to consider to help keep your Java ME code small. I have used many of them, and some of these tips and others can be found on Chapter 10 – Techniques for Writing Better MIDP Applications on my MIDP 1.0 book.

BTW, I recently got the green light from the publisher of my book Wiley & Sons, and I will be making parts of my MIDP 1.0 book (with updates) available for download for free soon… Well, when I get to it… Very busy times for me these days, even to keep up with my blog — but it is all good; stay tuned.

See – The 10 principles of Assembly Java.

ceo

Ten reasons why every programmer should learn C

Sunday, November 26th, 2006

The C Language is probably the most important programming language; it is fast, compact, and pervasive, and it exposes programmers to very important skills and concepts; you can't be sloppy when using C.

The C Language is the language of choice for building operating systems, other programming languages, and embedded and real-time applications. Anything truly hardcore and close to the OS is built in C.

Learning the C Language is a requirement for anyone who is serious about computer science and engineering…

The C programming Language has been a very important tool throughout my career.

See Ten reasons why every programmer should learn C.

ceo

SMS-based mobile attack by sending invisible and unnoticeable SMS messages

Saturday, November 25th, 2006


“Simply by sending an invisible and unnoticeable SMS message to a particular cell phone, spying on cell phone users has become child's play.”

Note sure the validity of this, but it's important to be aware of this security exposure… I won't be surprised if such over-the-air provisioning backdoor does exist…

This security exposure was found (claimed) by German company SecurStar GmbH.

Read more at:


>> Network Security News


>> SecureCore


>> TechWorld

ceo

Google: mobile operators want to block our apps

Saturday, November 25th, 2006

Jason at the Paxmodept Blog points out an article at ZDNet UK about Google and its struggles with operators who want to block Google applications.

Oh boy… not even Google can be saved from this one… that says a whole lot about the current (and nothing new, and who knows until when) situation between mobile software product companies/developers and carriers.

Chris says: “They're inserting themselves in between you and an application that you want. I think that has scary, scary implications…”

Yes, yes, that's what we have been saying for a while (years) now… Yes, we know (and are hoping) that the carriers will realize sooner rather than later how beneficial it will be for everyone, including themselves, to allow for open access and flat-rates… it is common sense. There are better and more creative ways to “milking the cow”… You know, sometimes, to move forward a very hard thing must be done: “slaughter the cash cow”. This is exactly what has been happening here; carriers just can't get over it, and are afraid of the unknown. It takes guts (as we say back home cojones) to kill the cash cow; a very hard decision to be made by executives it is indeed… Where are the fearless, visionary leaders? Fear not…

ceo

Mike R on "US Carriers Developer Hostility Hits a New High"

Friday, November 24th, 2006

Mike Rowehl writes about something that has me perplexed, upset, and furious – see All traffic to US handsets require a valid short code registered with the different networks.

This is a very big deal. And is no good… Closed systems, over-control by carriers is the top reason mobility is moving so slow here in the U.S.

Coincidentally, yesterday I left a comment on MobHappy on “Daniel Taylor: Let’s Address The Industry’s Failures, Not Ignore Them” (a must read by Daniel). Since what I wrote there and this shortcode debacle are both related, i.e. same root cause, I will include part of that comment here:

There are a number of factors that have contributed to the “failure” – being the top one that the (mobile) network has been a closed system for way too long. It took the Internet and the Web like 15 years to be what it is today: open, accessible, standard, and service-oriented. I am not surprised it has taken and will take much longer on the mobile side.

The second factor is a result of the first one; because it has been a closed system/network, it has been very hard to introduce to our users innovative ways and methods and products – it is just a pain in the neck and expensive to deploy today.

The third factor is also a result of the first one – owning a handset is expensive and too complicated: data-plans, texting, and handsets that don’t work out of the box.

It has been a slow process, slow to mature, too slow for many of us who’ve become frustrated after seeing more of the same for the last 8 years; wow, it has been 8 years for me, and we still are in kind of the same boat.

:

But it is not all bad, we definitely are much better off today than 8 years ago – the networks are opening – we just witnessed 3 making the first move/example. Carriers will finally learn and accept the fact that to realize the vision the network must be decentralized, open, with the flat-rates, and higher-speed networks, and sophisticated handsets, oh, and standards must be adopted. But to tell you the truth, we might be talking here about another 2-5 years.

This shortcode debacle introduces yet another detour on the road to open mobility… I am dead serious when I say we are talking about another 2-5 years of pain here. Note that this kind of pain is taken care of with an influx of money, but the reason this is not good is because it seriously restricts the kind of companies and innovation to just the few who can afford it – and this goes against the whole philosophy that has allowed anyone and everyone, you and me, anywhere around the world to contribute in whatever shape or form to the advancement of the (mobile) Internet/Web.

Now I must research this in detail, and map out the monetary impact of this: hundreds to thousands of dollars a month!

To the network carriers: think forward and long-term… to get there, we must start today… the ecosystem consist of “Big brother-Small brother” relationships to make it work… Let's make it work.

ceo

Carnival of the Mobilists #54

Monday, November 20th, 2006

Visit Judy Breck’s Golden Swamp for this week's Carnival of the Mobilists… A number of great and varied entries by Mobilists from around the world…

I have to admit folks that I totally forgot to submit my entry — I've been heads down writing S/W, and writing a pretty comprehensive technical article on managing PIM data on Java handsets…

Enrique

Java ME GPL Clarification by Terrence Barr, Sun Java Mobile & Embedded Evangelist

Friday, November 17th, 2006

Terrence (and his team?) was kind enough to spend some time clarifying the
concerns related to Java ME and the new GPL licensing model… read
Interpreting Java under GPL — does it force applications to be GPL as well?

Awesome. Terrence's answer is what I was expecting/hoping to get – but it was important to get this clarified…

You can read the Mobile & Embedded Community Interest forum (KVM-INTEREST) thread on this topic.

Thanks Terrence…

ceo

- – - – - – - – -

Enrique,

OK, so let me try and clarify this:

Sun chose GPLv2 without classpath exception for Java ME
because the method of bundling and distributing applications
together with platform implementation code (which is practiced
in the Java SE space) does not apply to Java ME.

We would like to make it absolutely clear that it is our intent
to encourage Java ME developers to freely innovate within the
application space. However, we understand that because of the
different possible interpretations of the copyleft properties
of GPL it is important for Java ME developers to know where Sun
stands in this particular respect.

We believe that any Java ME code which is independent of the
Java ME platform implementation and is distributed separately
from the Java ME platform implementation and merely uses the
functionality of the platform but does not extend or modify the
platform should not be considered a derivative or combined work
of the platform and as such is not impacted by the platform license.

In particular, you should be able to do the following without your
code being considered a derivative or combined work of the platform
implementation:

1. calling of public APIs in the platform

2. implementing interfaces which are part of a public specification
   of the platform

3. accessing and extending classes which are part of a public
   specification of the platform as long as your code does not
   extend or modify the Java ME platform in a general way

Note that integrating your code into the Java ME platform
implementation or installing your code into the device together
with the platform implementation at the time of manufacturing
of the device may trigger the copyleft properties of the GPL.
In such cases it is recommended to contact Sun directly for more
information.

Please let me know if this answers your concerns.

Thanks,

-- Terrence

Terrence Barr
Evangelist, Java Mobile & Embedded Community
Sun Microsystems, Germany
www.mobileandembedded.org
[Message sent by forum member 'terrencebarr' (terrencebarr)]