Archive for May, 2006

Mobile Banking has Finally Arrived

Sunday, May 28th, 2006

Coins

Is mobile banking finally here (I mean, in the U.S.)? It has taken financial institutions a long time to understand and feel comfortable with the technologies behind mobile banking, as well as understanding the implications to the financial institutions and to the end-users, as well as how to make money from the service. Remember the old security "WAP gap"? A lot of paranoia back then. Today, end-to-end security from the handset to the server has removed the security gap concerns, and financial institutions have figured out that money is going to be made indirectly, by offering new conveniences, vs. directly by charging for the service.

And while mobile banking hasn't really picked up here in the United States, it is huge in other countries, for example, in Korea where “more than a million Koreans now do their banking via 3G cellphones, according to March 2005 CNN report“. A search on Google for “mobile banking” confirms that mobile banking is almost non-existent in the United States, with few companies offering such solution. The trend graph below from Google trend on “mobile banking” shows not much activity, with activity starting end of last year (2005):


Google Trend - Mobile Banking

A Forrester 2003 report recommended back then that banks should stick to "simple banking activities on mobile phones, such as SMS alerts and account balance checking.",  but there is so much more to mobile banking than just balance checking and alerts… I find interesting that banking alerts is what the mobile banking TV commercial from Chase is promoting… but again there is better functionality, as I recently experienced.

Mobile banking is finally here…  TV commercials promoting mobile banking are starting to appear, and in two recent occasions I've used mobile banking for balance checking and for money transfers – very useful and convenient, much better than using Interactive Voice Response (IVR). The application offered by my bank, which was written by MShift, works very well on my Treo 650, with same functionality as the PC/web-based version, and a tabbed-based layout/navigation that simplifies the application usage.

I used to think twice about (mobile) banking from my handset, but today I am sold.

ceo

The "Web 2.0" Service Mark Debacle

Sunday, May 28th, 2006

“Do as I say not as I do!”

The Web 2.0 is supposed to be about the open, collective, community-based use and evolution of the Web, so what happened here when O’Reilly trademarks “Web 2.0″ and sets lawyers on IT@Cork?

This recent trademark (or service mark) debacle is such a great example of what I've been talking about on “theory vs. practice”… If you follow my blog, you have seen my recent writings on The Web 2.0 from a Practical Perspective, and theory vs. practice.

Just the thought of trade/service marking “Web 2.0″ is totally against the spirit of the Web and the Internet, AND against the new wave of community, collective use, and evolution of the Web.

I have to admit that I am a bit confused here, and that this debacle doesn't feel like “Tim”, and maybe it is the “evil corporate side” of CMP/O'Reilly that did this…

See:

ceo

Theory vs. Practice

Saturday, May 27th, 2006

Theory

  • “a well-substantiated explanation of some aspect of the natural world; an organized system of accepted knowledge that applies in a variety of circumstances to explain a specific set of phenomena; “theories can incorporate facts and laws and tested hypotheses”; “true in fact and theory”
  • “a comprehensive explanation of a given set of data that has been repeatedly confirmed by observation and experimentation and has gained general acceptance within the scientific community but has not yet been decisively proven”
  • “an abstract formulation of the constant relations between entities… A theory may be true or false. A valid theory attempts to eliminate all contradictions in the application of cause and effect to a given specific situation or set of conditions. The aim of a theory is always success in action”

Practice

  • “translating an idea into action”
  • “a customary way of operation or behavior”

Theory vs. Practice

  • “the distance between theory and practice is always so much smaller in theory than in practice”
  • “in theory, there is no difference between theory and practice; In practice, there is”

ceo

Sources:

    Definitions – web searches on “Theory”, “Practice”, “Theory vs. Practice”

Carnival of the Mobilists # 29 at Open Gardens

Friday, May 26th, 2006


CoMs

This week's Carnival of the Mobilists is at Ajit Jaokar’s Open Gardens weblog… Visit the Carnival to read this week’s best writing pieces about mobile from mobility bloggers around the blogosphere.

Click on the above Carnival of the Mobilists button to go the Mobilists website and learn more about the Carnival and how you can participate…

ceo

Launch Photography

Wednesday, May 24th, 2006


Discovery by Ben Cooper

I found a very neat web site called Total Eclipse (http://www.launchphotography.com) by photographer Ben Cooper, with photos of current and past
Space Shuttle and other rocket launches, for example, you will find a great collection of new photos of the Shuttle Orbiter Discovery (OV-103)  rollout to the launch pad. Discovery and STS-121 is scheduled to launch on July 1, 2006. Enjoy…

ceo

[Photo: Ben Cooper, http://www.launchphotography.com]

Mobility Blog Star – The Pondering Primate

Friday, May 19th, 2006

The Pondering Primate

Every now and then I like to write about a (mobility) blogger that I really like…

And today, I want to write about The Pondering Primate weblog… And while he is known as the Pondering Primate, his real name is Scott P. Shaffer, CEO and Chief Innovator at Visionary Innovations Inc. Scott is also an Iron Manliterally.

Scott (and his weblog) is a great source of information on mobile marketing and Physical World Connection (PWC).

Scott says: 
"every physical object will allow connection to a designated website and the mobile phone with it's physical world browser will be able to surf the "real world", the physical one"

The Pondering Primate is a great weblog, with great insights, and fun to read.

Past reviewed mobility blog stars:

* Jan Chipchase – Future Perfect

ceo

The Problem with Mobile

Friday, May 19th, 2006

On his blog, Seth Godin asks himself “Why hasn't the whole cell phone industry exploded?“. While Seth's believes it is because "we've been trying to solve the wrong problem.", that is not the true reason…

The problem is twofold – from the technology perspective, the technological capabilities aren't where they could have been by now, and from the end-user perspective, there are no enough compelling services.

And these problems are rooted at the “network (over) control” by the carriers that results in a pretty much closed system. And this control results in slow adoption and deployment of new technologies, and in the “carrier's inner circle”, which is hard to get into. And the end result of all this is lack of compelling services for end-users. One thing leads to another…

There are thousands of very smart developers and product people out there, but not everyone can bootstrap themselves, or go raise and initial $300K-$500K to create an initial demo or product, and get into the "inner circle".

Many years ago I realized that the carrier's network concerns are really historical, and have to do with how the networks have evolved – it all is a direct result of network “overloading” – offering new data capabilities on top of the voice services over the same network, which raises concerns about voice service disruption. Those concerns makes the carriers restrict the kind of services what can be done on their networks. This is in contrast to the Internet in the 80s and 90s and today, that was and is pretty much open, and there were NO restrictions to innovation AND on deploying such innovation. Deployment of technology and services over the carrier's wireless networks have been VERY slow due the aforementioned concerns, including the deployment of the solution to these
problems, the 3G+ networks, have been very slow as well…

We are now getting closer to true 3G, and the added bandwidth will help address some of the carrier's concerns, and we will see new services coming out – I've no doubt. But I am afraid that unfortunately we will continue to see the “carrier inner circle” for the time being, meaning the number people and companies with ideas that get in are fewer, thus the number of great ideas and services that could come out will be less than it could be.

So mobile does have a problem. And the problem is not innovation, or the entrepreneurs, or product people, but the problem is the closed network, the over controlled network, the "carrier's inner circle", that results in slow adoption and minimal services… At this rate, it could be another 5 years until we see a more open and neutral network, but I am afraid it will never be as open as the Internet.

Can product marketing folks help here? Yes, the carrier's product marketing folks can push to open the network, and do developer campaigns such as sponsoring developers, as Russell Buckley writes in his blog, and to push innovation and control to the “edge of the network”, while keeping differentiation, similarly to how the Internet has evolved – it is possible.

Things will get better – I just want them to get better in my lifetime ;-)

ceo

[Via MobHappy]

The Mobile Services Architecture (Proposed) Final Specification

Thursday, May 18th, 2006

The Mobile Services Architecture (JSR-248) or MSA is almost final. The MSA expert group has published the Proposed Final Draft Specification:

"This JSR creates a mobile service architecture and platform definition
for the high volume wireless handsets continuing the work started in
JSR-185 and enhancing the definition with new technologies."

MSA defines what the next generation (short term) Java platform for handsets will be. Recall that MSA is an umbrella JSR, and that there were some concerns when MSA was initially defined – see The Main Issue with MSA for CLDC (JSR 248) and MSA for CLDC Approved – But With Request for Changes.

Today the EG has taken the right approach by defining a subset of the MSA stack – the specification now defines two MSA stacks: 1) a full MSA stack (16 JSRs), and 2) a MSA-subset stack (8 JSRs) as follows:


MSA stacks


Click to enlarge

…With the following JSRs and related clarifications:

    MSA Subset:


  1. J2ME Connected Limited Device Configuration 1.1 (JSR 139)

    - CLDC is the configuration, fundamental component of MSA.


  2. Mobile Information Device Profile 2.1 (JSR 118)

    - MIDP is the profile, a fundamental component of MSA.


  3. PDA Optional Packages for the J2ME platform (JSR 75)

    - access to the file system available on a device, and Personal Information Management functionality.


  4. Java APIS for Bluetooth (JSR 82)

    - access to Bluetooth functionality, and the OBEX protocol (conditionally mandatory).


  5. Mobile Media API (JSR 135)

    - MMAPI provides access media capabilities such as audio and video playback.


  6. Mobile 3D Graphics API (JSR 184)

    - Three dimensional (3D) graphics.


  7. Wireless Messaging API (JSR 205)

    - WMA profiles messaging features such as SMS and MMS.


  8. Scalable 2D Vector Graphics API for J2ME (JSR 226)

    - access to two dimensional (2D) Scalable Vector Graphics.
  9. Rest of Full MSA Stack:


  10. J2ME Web Services (JSR 172)

    - XML parsing and basic web services in a mobile device.


  11. Security and Trust Services API (JSR 177)

    - SATSA provides access to cryptographic services (mandatory), communication with Smart Cards (conditionally mandatory), and access to Public Key Infrastructure services (conditionally mandatory). Note that SATSA-JCRMI is not part of MSA or MSA Subset.


  12. Location API for J2ME (JSR 179)

    - access location information (conditionally mandatory).


  13. SIP API for J2ME (JSR 180)

    - access to Session Initiation Protocol (SIP).


  14. Content Handler API (JSR 211)

    - CHAPI for launching of Java applications based on content type.


  15. Payment API (JSR 229)

    - access to payment mechanisms.


  16. Advanced Multimedia Supplements (JSR 234)

    - extends JSR 135 to provide more advanced multimedia capabilities.


  17. Mobile Internationalization API (JSR 238)

    - enables the development of localized applications.

Go checkout the MSA specification, see what is coming, and get ready for the next generation handsets that will be coming probably starting this year…

ceo

[Via the Java Community Process]


[MSA stack image source: MSA specification]

Gyros on Mobile Handsets – A Very Powerful Tool

Wednesday, May 17th, 2006

InvenSense has released their Integrated Dual-Axis Gyroscope
Very neat, great potential.

More than half a year ago I was immersed in a thinking session, when the idea of using the dimension of space for mobile applications and presence came about – and with this leveraging gyroscopes. But no gyro-enabled handsets existed at the time. Well, now that is going to change. With gyros embedded into handsets we are a step closer to the programmatic use of movement in space over time as a trigger, literally resulting in using new dimensions in our mobile applications – some uses include gestures, orientation-dependent UI, and presence… Just think about… Very powerful indeed. Very exciting…

ceo

[Via The Raw Feed]

[Image source: InvenSense.com]

The Mobile Perimeter

Friday, May 12th, 2006


Perimeter: The distance around a figure.

The other day I read via Textually/Ringtonia about a fight that broke out in the Iraqi parliament after a mobile phone ringtone played a Shia Muslim chant – see Shia ringtone sparks scuffle in Iraqi parliament. Later on Ringtonia reported about the controversy caused by another ringtone, “La Migra” (short for Immigration), where Hispanics were offended by the ringtone – see Ringtone Company Sorry for Lyrics Satire.

But, what I find of interest about these two scenarios is the study of usability and something that I've been spending a lot of time formally studying, understanding and defining, and this is the mobile context. The two cases above are concrete examples of one of the elements that comprise the mobile context, and this element is the mobile perimeter, which is the distance between the mobile user and the people around him or her.

The mobile perimeter is a shared space, where intentional and unintentional interactions with others may occur. Of interest is the use of media while in this space. Not all media have the same effect on others sharing this space, and not all media have the same reach or distance, or perimeter effect – if the media doesn't violate other's perimeters, everyone is happy. Talking loud on the phone, ringtones, and other media that crosses boundaries violate other people's spaces. Visual or texting media are not as much of a problem since the mobile perimeter is pretty much contained and thus it doesn't violate other people's spaces. We all know the solution to this problem — courtesy and consideration towards others that are roaming through your mobile space.

But besides the obvious, it also is an interesting and important area of study in usability design of mobile handsets and media.

ceo

DISCLAIMER – HANDSET AND HANDSET USAGE WARNING

Sunday, May 7th, 2006

Due to recent circumstances, we have been forced to write the following disclaimer…

DISCLAIMER – HANDSET AND HANDSET USAGE WARNING -

Handsets and its software can be unpredictable and unsafe. Handsets can be dangerous. It has been reported all around the Internet about these dangers, and there's no way we can list them all here. Read the news.

Handsets and its software may have hidden design holes – these can create frustrations, get you distracted, you can loose your data, time and money. We do not inspect, supervise or maintain handsets or all its software.

The network can go down, batteries can drain, data can be unintentionally deleted by the user, the wrong key input can be entered when cycling through the hard to use T9 keyboard, the keyboard design can be unnatural, batteries can explode, the OK or CANCEL button can be reverse, all resulting in data loss, frustrations, or personal injury.

Real dangers are present from daily handset use – you can get a brain tumor. Using hands-off devices with Bluetooth is no guarantee and can increase the risk of tumor by having 2.6 2.4 GHz wireless frequency right onto your brain.

Weather can be dangerous, regardless of the forecast. When using your handset, be prepared with rain gear. Electrocution, short circuit, loss of network connectivity, loss of power, can all result in data loss, and frustration. This frustration may get you disoriented and lost. Carry food, water and first aid supplies at all times. Rain can turn a typical day into a deathtrap.

Handsets can be used to track your whereabouts with or without your knowledge or permission – beware, your spouse, significant other, employer, or stalker can be tracking you right now.

You can go broke if using data-plans and/or messaging (SMS, MMS, IM) – this is especially true if you have teenagers.

Handset use can create distractions – you can get into a car accident, fall, be injured or die. Or you can run over a pedestrian.

Handsets can fall from the sky – beware. This can happen naturally by accident, or be caused by people in higher grounds when throwing their handsets out the window, frustrated with their handsets. Use of helmets is advised for anyone approaching business areas with high buildings, as the force of handsets falling increases with altitude – this can kill you. Helmets won't necessarily save you if you get hit by something big, but nevertheless you should use a helmet in such situations. Please note that handsets can be of all sizes – massive first generation handsets, or smaller new generation. Don't think it can't happen.

We take no responsibility. The other handset users, including other visitors, our employees, agents, and guests, and anyone else who might sneak in, may be stupid, reckless, or otherwise dangerous. They may be mentally ill, criminally insane, drunk, using illegal drugs and/or armed with deadly weapons (such as the handset itself) and ready to use them (i.e. throw the handset). We aren't necessarily going to do anything about it.

If you use your handset, you may die or be seriously injured. This is true whether you are experienced or not, trained or not, equipped or not, though training and equipment may help. It's a fact, using your handset is extremely dangerous. If you don't like it, don’t use handsets. You really shouldn't be doing it anyway. There is no substitute to a warm face-to-face conversation. We do not provide supervision or instruction. We are not responsible for, and do not inspect or maintain, handsets or the software in it (including batteries, antennas, browser, Java, BREW or Windows Mobile implementations, Mobile Media API, Graphics API, etc.) As far as we know, any of them can and will fail and may send you plunging into frustration, and possibly your death. There are countless tons of loose handsets ready to be dislodged by frustrated users and fall on you or someone else. There are many extremely and unusually dangerous conditions existing on and around handsets. We may or may not know about any specific hazard, but even if we do, don't expect us to try to warn you. You're on your own.

We don’t provide rescue services. Local rescue squads may not be equipped for or trained in handset injury rescue. If you are lucky enough to have somebody try to rescue you or treat your injuries, they may be incompetent or worse. This includes doctors and hospitals. We assume no responsibility. Also, if you decide to participate in a handset rescue operation of some other unfortunate, that's your choice. Don't do it unless you are willing to assume all risks.

By using your handset you are agreeing that we owe you no duty of care or any other duty. We promise you nothing. We do not and will not even try to keep handsets safe for any purpose. Handsets are not safe for any purpose. This is no joke. We won't even try to warn you about any dangerous or hazardous condition, whether we know about it or not. If we do decide to warn you about something, that doesn't mean we will try to warn you about anything else. If we do make an effort to fix a specific unsafe handset condition, we may not try to correct any others, and we may make matters worse! We and our employees or agents may do things that are unwise and dangerous. Sorry, we're not responsible. We may give you bad advice. Don't listen to us. In short, USE YOUR HANDSET AT YOUR OWN RISK.

Even if you know what you're doing, lots of things can go wrong and you may be injured or die. It happens all the time.

Handsets and/or related software may be negligently constructed or repaired. They are unsafe, period. Live with it or stay away.

The Management

[These guidelines are an adaptation from Nelsons Rock Disclaimer]

Mobile Monday Global Summit and Peer Awards

Friday, May 5th, 2006


MoMo Peer Awards

Mobile Monday Global Summit and Peer Awards – May 8-9, Helsinki, Finland.

We are happy to announce the Mobile Monday Austin nominees for the Global Peer Awards:

Congratulations to the nominees!

Meet the organizers attending the Summit.

Visit Mobile Monday Global Summit and Peer Awards website.

John Carmack on Mobile – He Really Gets It

Thursday, May 4th, 2006

Orcs & Elves

John Carmack of id Software understands what mobile software development is all about…he really does. I am going to quote to pieces from an interview of him by GameSpot titled “Carmack bitten, smitten by mobile bug“, that tells a lot about his understanding of the mobility space…

In the next quote, John is referring to the current state of the mobile/wireless handsets technology:


“It's interesting that this may be a very short-lived window because the hardware, at least, is advancing at just a breathtaking pace, much faster than it did even on the PC space when you look at this. Where upcoming phones that are going to be out by next year, looking at things that have more power than a classic Xbox sitting on a mobile platform.”

In the next quote, John is referring to the design and/or usage pattern of mobile/wireless handsets when compared to PCs:


There are different things that you would look at on a PC or console game. You can design it so the intent is to immerse someone and hold them there for a very long period of time, while the purpose of the cell phone game is something that you can do at short bits of time, where you can pick it up and play for 10 minutes or something, without having to get into something really deep. You need to be able to put it down quickly.

JC gets it… And because of that, I expect some great software coming out of his teams, well designed mobile software that takes into consideration the usage patterns, technologies and characteristics of the mobile platforms and users.

ceo

Attributions:


[Via
Hinkmond Wong's Weblog
]


[Image source: GameSpot
Mobile
]

Mechanical Turks, Answers, and the Attribution Problem

Tuesday, May 2nd, 2006

The permalink for article Mechanical Turks, Answers, and the Attribution Problem has changed to:

http://weblog.cenriqueortiz.com/general/2006/05/01/mechanical-turks-answers-and-the-attribution-problem-2

This was due to change in category from “/” to “General”…

Sorry for the inconvenience – Blojsom doesn't handle category changes that great :-)

Mechanical Turks, Answers, and the Attribution Problem

Monday, May 1st, 2006

Mechanical Turks, Amazon's Mechanical Turk, web services, blog aggregators, web searches, screen scraping, data and information, copyright and attribution… With the rise of “easy access to information” comes a relatively new, still untapped solution vertical: Answers

Amazon offers its Mechanical Turk API, Google and Yahoo! both offer Answer products, which in turn relies on people to find and post the answers. A number of startups such as AskMeNow have emerged in this space as well.

And with these new answer solutions also come concerns related to copyright, attribution and compensation. Let me give you an example. If I hit the web and ask the question “What is an answer?”, I get back:

      To “reply or respond to”, to “give the correct answer or solution to”.

The above are the answers I got back from a Google search.

But who's definition is this? I see no attribution other than “definitions on the web”. Someone spent the time to define and write this information. So why isn't there an attribution? Is that fair use? I am not a lawyer so I can't really say, but as an author I will say that the use of information without attribution is of great concern.

Another example – if the question that is asked is “What is the weather in Austin, Texas”, where do you think the information will be coming from? I will tell you: NOAA, or Yahoo! Weather, or Weather.com, or similar providers. And I am certain they would also like the source of the information to be attributed. Weather.com terms of use contains the following: “the contents of the site are copyrighted under the United States copyright laws. You may not modify, publish, transmit, display, participate in the transfer or sale, create derivative works, or in any way exploit, any of the content, in whole or in part.”

Content is king. And creating good and accurate content is not only hard, but it is expensive in many ways. And the web provides a shortcut to ask and find information and answers. And I am afraid the attribution problem will get worst with the new wave of Answer products that are coming out…

The following diagram shows the elements of a possible Answers engine:

Answers


Click to enlarge

Where… we have the source for most of the information/answers: the Web. The diagram also illustrates possible ways to extract information from the web: screen scraping, web searches, Mechanical Turks… Some “answer engines” may even implement a cache for performance purposes. You can see how information can easily be extracted from the web – without proper attribution and compensation. The local cache may even store this information without permission. This is a huge problem, because authors may be relying in users visiting their websites for generating revenue through advertising.

Everyone is affected… from bloggers, to authors of books and technical papers, to Wikipedia… to anyone who provides content. The end-user benefits from this, as well as the answers companies and the people behind the mturks who research (Googles) the information and delivers it. But to whose expense? To the authors and the content providers expense. Bloggers and other content providers already have to battle blog aggregators and others that cannibalize without any respect. The next battlefront might be against the answers companies.

Fair use is follow the terms of use, and provide proper attribution and fair compensation as appropriate.

Since I don't have an answer to how to enforce attribution and compensation, I will be modifying my weblog's legal terms to not allow the extraction of information by Mechanical Turks, or screen scraping, or blog aggregators, or any other method that extracts information without proper attribution and compensation.

If answers companies don't follow terms of use and don't provide proper attribution and compensation on the information they use, then they have become nothing more than sophisticated (possibly illegal) “screen scrapers”.

Web 2.0 is about collective use and collaboration… And referring to is not the same as extracting and cannibalizing from… Answers companies that uses other people's content, directly or indirectly, must do the fair thing: follow term of use, give proper attribution and show the money! :-)

Easy, fast, and now access to answers has great revenue generating potential. And it is of great benefit to end-users. In mobile handsets we need such solution; a cheaper solution that competes against the expensive (carrier-based) 411. All I ask is for fair use of information on the web.

ceo

Attributions:
* [Mechanical Turk Image source: Wikipedia]
* [Elements of an Answer Aggregator Image source: C. Enrique Ortiz]