Amazon Tech Support

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Thursday, 13 November 2008

The need for end-user forums to start specifiying handsets

Posted on 00:42 by Unknown
There are already a number of organisations that capture operators' requirements for handsets and feed them back to the OEMs. The OMTP is probably the most obvious, along with the OMA and some of the activities of the GSMA and CDG and WiMAX Forum. Standards groups like 3GPP also are clearly important in defining the standards for "UE" (user equipment) behaviour.

These groups do sterling work in a lot of areas - from making sensible decisions about standard screen sizes & power connectors, through to defining APIs for browsers, and certification mechanisms for radios. They put out reams of documentation stating that manufacturers MUST do this, or SHALL do that, or OPTIONALLY MAY do the other.

But there's something missing.

As far as I know, there are no consumer advocacy groups defining what the end user wants to get from their phones, and how they expect them to behave. There's no group setting desirable specifications that "average" people want, such as "It SHALL be possible to delete useless apps like videotelephony from the homescreen", or "There MUST be a highly-visible indicator of monthly data usage, configurable in X, Y & Z fashion"

Particularly as handset subsidies fall - or handsets become cheap enough for normal people to buy "vanilla" - it shouldn't be just the mobile operators that get to define features & behaviour. Yes, they might be the handset producers' main direct customers, but it's about time that the people paying at the end of the value chain started to throw their weight around.

The only reason that people have to "put up with" hobbled Bluetooth, annoying operator-branded UIs, locked-down operating systems and so on is because they aren't organised enough to try to change it. Complaining on web forums doesn't cut it. But if a delegation from a "Phone Users' Forum" representing 100 million people turned up in Helsinki or Seoul with a list of demands, I suspect they'd get a good hearing. (Although probably not in Cupertino, California....).

There is already precedent for this in the enterprise world. Organisations like the EVUA represent powerful groups of telecom and IT-using multinationals, that collectively exert leverage on their technology suppliers.

Perhaps the starting point for mobile handsets is also in the enterprise space. Although the volumes are lower, there is a greater bias towards smartphones and "vanilla" devices. There are various organisations like systems integrators and unified communications vendors that also have a lot of pull here. Collectively, the business community needs to make sure that the phone manufacturers continue to enable "over the top" applications in the best way possible. An influential group articulating & defining that requirement in concrete terms would be hugely beneficial.

A particular point of future contention might be around the IMS RCS client, which if pre-installed on handsets could become the "default" IM and presence application, hooking them into operator IMS cores. This clearly needs to be delete-able from devices used as part of enterprise-controlled unified communications solutions. There need to be variants of handsets available that are optimised for server/PBX-anchored corporate alternatives.

Over time, there may be parallel consumer advocacy initiatives, but I suspect they be more difficult to organise, especially internationally. But I can see great benefit in mandatory requirements for easy sideloading / backup of content and contacts, for example, and better information about costs and balances. The best way for end users to avoid future "lock in" by their operators is to specify workarounds to the handset manufacturers upfront. Make them remember who the real customers are.

The bottom line is that the billion or so handset purchasers need to play the system better. Otherwise, the system will continue to play them.
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Posted in | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • The Number 1 problem for "seamless" models of WiFi offload / network selection
    I frequently argue against the assumption that "seamless" connection to WiFi is practical or desirable, especially for the general...
  • Mobile social networking - how I'll know when it's going mainstream....
    This falls into the category of "amusing personal anecdotes" rather than "rigorous industry analysis". But it also refle...
  • Part of Nokia's problem - making Ovi compelling
    I've got a Nokia Ovi account somewhere. Signed up for it ages ago, to play around with the Ovi Store when I had an N97 to play with, ba...
  • Putting a value on customer data with reference to offload
    There continues to be a ferocious discussion about AT&T's new data plans - and also, as I commented a couple of weeks ago, about the...
  • Android - the retail experience
    I just stopped off at my local branch of Carphone Warehouse on a whim, to have a quick look at what's being sold and how. (By coincidenc...
  • For telcos, "Monetising OTT" is about distribution partnerships & revshare, not QoS or termination fees
    A couple of years ago, I moderated a panel session at a conference on broadband business models and "traffic management". It was o...
  • BT WiFi smartphone application
    I've just seen BT's announcement of its new iPhone and Android app, offering free WiFi access at its Openzone and FON hotspots to i...
  • An update on @DApremium - the world's first paid Twitter channel. Now available with quarterly or annual subscriptions
    It's now been six weeks since I announced the launch of @DApremium , my second Twitter stream - one which is available only to paid subs...
  • The Novatel MiFi - possibilities for new mobile broadband business models
    OK, I realise that I've been a bit grumpy and critical of some things recently. But before everyone assumes I'm getting more cantank...
  • There really needs to be a "User tariff API" for developers
    Generally speaking, app developers and website owners know what device you've got, what OS, and what browser. Furthermore, they know wha...

Blog Archive

  • ►  2013 (31)
    • ►  October (2)
    • ►  September (3)
    • ►  August (1)
    • ►  July (2)
    • ►  June (6)
    • ►  May (5)
    • ►  April (1)
    • ►  March (3)
    • ►  February (3)
    • ►  January (5)
  • ►  2012 (46)
    • ►  December (5)
    • ►  November (4)
    • ►  October (3)
    • ►  September (2)
    • ►  August (4)
    • ►  July (3)
    • ►  June (1)
    • ►  May (6)
    • ►  April (4)
    • ►  March (1)
    • ►  February (9)
    • ►  January (4)
  • ►  2011 (73)
    • ►  December (4)
    • ►  November (10)
    • ►  October (8)
    • ►  September (6)
    • ►  August (3)
    • ►  July (5)
    • ►  June (7)
    • ►  May (9)
    • ►  April (4)
    • ►  March (7)
    • ►  February (6)
    • ►  January (4)
  • ►  2010 (130)
    • ►  December (4)
    • ►  November (10)
    • ►  October (10)
    • ►  September (6)
    • ►  August (9)
    • ►  July (7)
    • ►  June (19)
    • ►  May (19)
    • ►  April (11)
    • ►  March (18)
    • ►  February (7)
    • ►  January (10)
  • ►  2009 (126)
    • ►  December (4)
    • ►  November (14)
    • ►  October (9)
    • ►  September (8)
    • ►  August (9)
    • ►  July (10)
    • ►  June (21)
    • ►  May (14)
    • ►  April (2)
    • ►  March (11)
    • ►  February (15)
    • ►  January (9)
  • ▼  2008 (94)
    • ►  December (24)
    • ▼  November (26)
      • iPhone available with a year's prepaid connectivit...
      • Mobile broadband PCs with embedded 3G - pricing co...
      • Will "iPhone" be used as general slang for "smartp...
      • Nokia gets HSUPA.... blurring the featurephone/sma...
      • When is UMA not UMA? Part 2
      • Assorted interesting tidbits & observations
      • Thoughts on white space spectrum
      • Every time I see the Android pitch, I like it less...
      • GSMA trying to force adoption of NFC in phones
      • Carnival of the Mobilists at Mippin
      • Question: When is UMA not UMA?
      • Next week in SF - Open Mobile Summit & Telecom Cou...
      • The need for end-user forums to start specifiying ...
      • Mobile Broadband - the cracks are starting to show
      • Mobile data revenues more than messaging?
      • Carnival of the Mobilists 149
      • PC vs mobile Internet access - where's the asymptote?
      • ARPU is a lousy metric for tracking mobile broadband
      • Work and personal profiles on a single mobile phone
      • Do you want HSPA modules in device, if you're aggr...
      • Partner conference - Femtocells USA
      • Redefining "Telco Grade" for the Mobile Internet era
      • Swisscom - the worst offender in public WiFi?
      • Mobile broadband - O2 highlights dissatisfaction a...
      • No WiFi in the Vodafone BlackBerry Storm - a serio...
      • Mobile search doesn't exist - a good proof point
    • ►  October (25)
    • ►  September (19)
Powered by Blogger.

About Me

Unknown
View my complete profile