Posts Tagged ‘Google’

The new way to purchase a consumer phone: Google.com/phone

Tuesday, January 5th, 2010

Well then, this is another day to remember. It’s the day Google got stuck into mobile merchandising and nailed the mobile operator to the wall.

That’s it: Thank you for coming, mobile operators, thank you for coming. You did your best. But now you’ve been ‘owned’. Well.. not yet. But do look out for the big G.

With the Nexus One, Google has ushered in an entirely new way of buying a consumer handset: From their website in 6 clicks.

Shit!

Is it that simple? Yes.

You visit Google.com/phone and select your financing option. You either buy your phone outright, or you get it financed by a bankmobile operator that also supplies your voice and data connection.

If you’d like a Nexus One — Google’s newest device — they’re shipping right now. You buy it from Google. Not from your operator.

Your operator is an also-ran. The operator has been relegated to bit-part status in the new Google process. It’s like choosing whether you want to pay with MasterCard or Visa. It doesn’t make much difference. Indeed you can never remember if your Capital One is Visa or MasterCard… pull it out your wallet — oh, it’s Visa — right then, Visa it is.

It won’t be long until I’ll just pay Google. I mean, what is the sodding point messing around choosing operators when Google just sorts it out.

Yes, we’ve had decades and billions of marketing dollars spent making sure we ‘care’ what operator we select. But, again — like any commodity, the reality is there isn’t much difference between operators. Who do you buy your electricity from? In the UK, the market has been opened to competition so instead of one supplier for an area, you can actually choose to pay a whole array of different suppliers. Most people stick with what’s easiest.

When it comes to google.com/phone, that’s what a lot of consumers will do.

I think it’ll be a little while before consumers — the normobs, the Great Unwashed — descend on and begin relying upon Google.com/phone for their telecommunications needs.

You can see it happening though.

You can see the strategy.

If you, as an operator, are not on the Google.com/phone page, then you’ve got a problem. 100% of people buying through this mechanism will never, ever choose you.

And Vodafone’s done the European deal, it seems.

Soon you’ll be able to buy all manner of handsets through Google.com/phone. All through a nice slick 6-step interface and powered by your Google Checkout account.

There are pitfalls of course. Your average mobile operator is — by now — pretty good at dealing with fulfilment. If I phone 3 at 11am on Monday and arrange for a new handset, provided it’s in stock, it’ll be at my door by 9am on Tuesday. Operators also have the rest of the fulfilment stream managed reasonably well. How will Google handle returns? Can I phone Google and complain about lack of T-Mobile signal? Where does my relationship lie with the transaction?

The overriding issue with Google is that they don’t give a stuff about the mobile operator. The mobile operators are standing in Google’s way. Google’s focus is — as commented via the Gizmodo coverage of the live event today — mobile advertising revenue. They are making a small margin on unit sales, but, “making sure people get access to Google services and get online is their #1 priority.”

To put this in perspective, here’s another quote from today’s event:

People search the web 30x more on an Android phone than they do on a feature phone.

The concept is not surprising. A shitfeature phone is rubbish for searching online. Oh the browser can handle displaying Google, but when it comes to anything else — and in particular, browsing search results featuring Google Ads — the devices are useless.

The fact Google report 30x more searches is quite surprising. Yet I can believe that figure. And goodness me when you start counting the billions of dollars of mobile ad revenue to be had over the next 5-10 years, yeah… Google definitely needed to wade into the existing marketplace more or less hampered by the operators.

Putting Google as the search engine of choice on the operator portal has been useful, no doubt. But I can certainly understand this strategy. If anything it points to the commercial imperative Google feels as they analyse the growth and potential of the mobile world.

Fascinating times.

If you’d like to read Google’s viewpoint, the team over at the Official Google Blog have prepared an overview of today’s announcement. It really does make interesting reading, especially when you read between the lines. Here it is: Our new approach to buying a mobile phone.

The Nexus One won’t tempt me away from the iPhone

Tuesday, December 15th, 2009

It’s Jonathan Mulholland here once again!

Like most mobile geeks, I’m really enjoying all the Google Nexus One news; it’s starting to sound like a very nice device, and it’s obviously a very interesting move by Google. Seeing their vision of what a modern mobile device should be — and how far Google feel they can push their services into our pockets will be fascinating to see.

I’ve already pretty much decided that I’m going to give the Nexus One / HTC Passion — or whatever it ends up being called — a miss though. Not because I’m a total Apple fanboy, or because I’m one of those crazies worried about giving Google too much access to my data – I’m a very heavy user of all of Google’s services, and have been ever since I opened my first Gmail account back in 2005.

Why the reluctance then?  Android has many positives – mobile Gmail is great, Google Maps on Android is better than on iPhone, multitasking rocks and Android’s notification system is just plain brilliant.  But at the end of the day – from my experience (G1, HTC Magic and HTC Hero) – Android is actually a pretty sucky phone.

I think Ewan hit the nail on the head yesterday:

My biggest concern with Google is their apparent inability to bring anything to market that is actually ready for consumers to use. I’m talking, of course, about the perennial ‘beta’ labels that populate their technology. This beta policy makes a ton of sense — and I think the majority of geeks like me are thoroughly delighted to see the company make frequent updates to their services. I wonder, then, how they’re reacting to delivering a physical product that can’t be changed.

To say that the Android phone experience is a bit unpolished (even when tarted up by HTC) would be a massive complement; take the iPhone away from your ear to “press option 3 to speak to an advisor” and the screen lights up ready for use – easy!  Try the same trick with an HTC Hero and the screen will have locked.  Go to press the phones usual screen unlock key and you’ll often have killed the call.   It’s this kind of thoughtfulness that I think Android phones will always lack, mainly because Android devs don’t have a maniacal Steve Jobs standing over them yelling – “not good enough, do it again.”

The iPhone might have limitations — and the App approval process does appear to make some rather perverse decisions — but Apple’s rigid control of the platform undoubtedly makes it slicker.  We had to wait far too long for ‘copy and paste’ to appear, but when it did it was perfect.  Does any other device honestly have this feature implemented as well as the iPhone?

I’m also rather dubious about one of the Nexus One’s really big selling points — availability as a carrier unlocked device.  If this is true I really applaud the move, it could be a watershed moment for the telco industry, but I’m just not sure Google will be able to pull this off.  They don’t have consumer goods distribution experience; I suppose they could rely on HTC’s sales channels, but this would be a really big ask.   Google has previously given away unlocked Android devices to developers only, could they be dong the same with the Nexus One, planning to release the device to the public via one of the carriers (my money would be on T-Mobile)?

Then there is my final nagging doubt; good as the Nexus One may be, in my mind it’s really a second generation future mobile device (1st gen = iPhone, 2nd gen = iPhone 3G/3GS).   I’m sure it will stack up well against the iPhone 3GS, Palm Pre etc, but really we’re still watching Android play catch-up.

I still predict that the really big mobile news of 2010 will be the major update Apple announces to the iPhone platform in June, so for the meantime I’m sticking with Apple.

My Google Latitude is now live to the world

Wednesday, May 20th, 2009

People I know from London keep asking me, “Are you in San Francisco?” and, people from San Francisco keep asking if I’m in London.

The where-are-you question is very, very relevant in the context of business so I’ve been trying to solve that with the use of a Where Am I function on my personal site, Ewan.net.

I was previously using BlogLoc for this function… but it was getting a little bit annoying having to manually update every time I remembered.

So instead I’ve decided to try out Google’s Latitude facility. Latitude allows you to see the locations of your friends on a Google Map (either on your phone or online) and it works pretty well.

Recently the Google Latitude team announced that they’ve added a public ‘badge’ facility that you can place anywhere on the web to show off your current location. This definitely isn’t for everyone, especially if you’re a little bit suspicious or concerned about your privacy. But I like the concept myself and I thought it was worth a try. Google have been particularly direct with their warnings — which I heeded — so I haven’t displayed by actual street level GPS location. Instead I’ve displayed my general ‘city level’ location.

Here’s what it looks like on the blog:

Nifty.

If you’d like to do the same, get your Google Latitude Public Location Badge here.

Originally published on Ewan.net and automatically republished here on Mobile Industry Review. View the original post.

Vodafone’s ‘App Store’: Mobile developers respond

Tuesday, May 12th, 2009

I just published Vodafone’s news regarding their ‘app store’ initiative — and I’m already getting questions and reaction in from developers.

Here are some quotes right off the press from some mobile developers. (I have removed names).

- “I’d like to know how much of my revenues they’ll demand.”

- “I like the ease of billing and the potential of micro-payments.”

- “I suspect they’ll take 30% just like Apple / Nokia etc. I hope it’s not more than that.”

- “It’s just another App store – we WILL develop for it, obviously, but only because I’m yet to see which store will capture the minds of consumers.”

- “I very much like the concept. Especially if one SDK works across a number of MNOs. That would be really cool.”

- “Is this too good to be true? It sure looks like it.”

- “If they were REALLY thinking of developers, they’d be finding a way to reduce the amount of work we need to do across the various mobile programming languages. Perhaps they are, I can’t quite work it out yet.”

- “Interesting, interesting… that’s all I have to say until you tell us more, Ewan.”

I’m aiming to have more information soon! If you’ve got a comment or opinion, drop me a note — ewan@mobiledeveloper.tv.

(I regularly tap up people for live reaction — if you’d like to be on that list, add me at ewanmacleod@gmail.com on Google Talk or ewanjmacleod on Skype.)

[Post to Twitter] Tweet This Post 

Share/Save/Bookmark

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

Originally published on Mobile Developer TV and automatically republished here on Mobile Industry Review. View the original post.

Help: Is this a mobile developer FAIL?

Saturday, May 2nd, 2009

Whilst we get busy with the new design and arranging of developer interviews, I need your assistance on this conundrum. I’m not sure whether it’s a complete ‘FAIL’ (as the phrase goes) on the part of the developer, or whether it’s just-one-of-those-things.

I’ve been using my Android G1 a lot since I arrived in America because, conveniently, my US T-Mobile sim works perfectly with it (even though it’s a UK device). I didn’t have to do any configuration since HTC thoughtfully included the T-Mobile US web settings on the device already.

So I’ve been taking pictures.

As you do in a city as nice and as varied as San Francisco.

I’d like to send them directly to Flickr. Since there’s no ShoZu service on Android at the moment (and I haven’t re-installed Pixelpipe yet) I thought I’d have a look around the Marketplace on Android.

Unlike others, I take it upon myself to buy as many applications as possible. I did a certain amount of evaluation on ‘Flickr Upload’ when I came across it. From memory it was $0.99. Or perhaps less.

I scrolled down to the comments.

On the 28th of April, ‘Matthew’ commented:

Works wonderfully. Well integrated.

.. and he gave it five stars.

I suspect Matthew is referring to the share option. When you take a photo on Android, there’s a button that pops up called ‘Share’. Click on that and you get the choice of sharing by Email, by Google Mail or — to Flickr (enabled by this application). Smart. I was warming to the concept.

I noted that it’s had between 100-500 downloads. Ok. Not a brilliant well-trodden path. I continued with the comment review.

On the 21st of April, ‘z0mbix’ commented:

Will not authorise with flickr on t-mobile/G1. Can’t get any reply from the developers em[ail]…

Er.

I’d gone off it right away.

The final comment on the app’s frontpage was a day before z0mbix’s one from Benjamin:

Exactly what I was looking for works perfectly

Hmmm.

Z0mbix’s comment put me right off. But I reasoned there must be a reason, maybe he/she didn’t know what they were doing? Afterall if Benjamin and Matthew each had a good experience, I should be ok?

Right?

As I walked out of the Westfield Mall in downtown San Francisco I spotted an advert I wanted to write about. I decided to download Flickr Upload there and then, configure it and get moving.

I paid the money, the app downloaded and within seconds I’d got to the main prompt, asking me to authorise my Flickr account to work with it. Fair enough.

I typed in my Yahoo account username and password and hit ‘login’.

Nothing happened.

Nothing.

The screen went blank.

Er.

‘I’ve just paid a dollar for this,’ I thought, rather disappointed. I was experiencing the pain of fellow user, z0mbix.

I tried again. Maybe I typed my details wrong?

Again it failed. The app just sat on a blank screen like this:

Rubbish!

I ended up sending the photo to my email account and walked home, rather annoyed with myself.

I was annoyed because I thought I’d obviously got my Yahoo password wrong.

What self respecting developer would allow an application to go live — a chargeable application at that — which doesn’t actually work?

Then I reasoned that it must be a Yahoo screw-up and spent a good few blocks cursing them in my mind.

I got back to my desktop and immediately changed my Yahoo password to check I had it correct.

Again I tried authorising the app.

Nothing. Nada.

I’ve bought a dud.

I don’t know who is responsible. It COULD be Yahoo, entirely. But one assumes that the two other recent commenters on Android Marketplace aren’t lying and they got it to work.

I’ve tried a few times over the past few days to activate it to no avail.

So I looked up the developer online.

They’re called Macrospecs and they’re a privately-owned startup in the bay area.

Ah hah! They’ll have a GetSatisfaction page, right? Or a forum or something?

No.

Nothing!

It’s a one-page website and — ultra annoyingly — the ‘contact’ page goes straight through to their email address.

Confusingly there is absolutely no reference to the Flickr Upload application on their site.

I then had a look back on the Android Marketplace and saw that the ‘developer site’ is listed as FaceofMobile.com/Flickr. Ah hah!

No, hold your excitement.

This is the entire site:

Yup… it’s one page. It consists of three screenshots and a macrospecs logo, with no link. No contact details. No support option. Nothing.

In fairness to the developer, one wouldn’t expect that many support enquiries from an application that simply sends a photo to a Flickr account. It’s not rocket science and there’s hardly any failure points.

Except the authorisation process.

And, of course, macrospecs don’t control that, Yahoo do.

Tough luck for me and z0mbix, right? If it ain’t working, you can try contacting macrospecs but it’s rather clear they don’t want to know — and are not expecting to support any enquiries.

I hunted around and I found a support forum for macrospecs’ Face of Mobile application, a $1.99 Windows Mobile Facebook app.

I suppose I could try posting there.

But I’m not feeling very welcome — or smart for buying the app. Indeed I’ve paid a dollar for the privilege.

It’s perfectly fine for it to happen to me, I have a good understanding of the trials and tribulations of mobile development — but if this is the experience of your average consumer who’s just picked up a G1 or G2 and is expecting 100% friction-free total quality-assured service from the Android Marketplace, they’re not going to be at all impressed.

Like the ringtone marketplace a few years ago — you’ll pay once and if the experience sucks, you definitely won’t ever pay again.

What’s the right response?

Is this a FAIL on the part of the team at macrospecs? Is it a Yahoo FAIL?

Or is it an Android FAIL?

Would this have happened on an iPhone?

Share/Save/Bookmark

Originally published on Mobile Developer TV and automatically republished here on Mobile Industry Review. View the original post.

Got 60 friends? Spell out a message with Google Latitude

Wednesday, April 15th, 2009

I came across this rather nifty proof-of-concept video from the Google Latitude team.

Latitude, if you’re not familiar with it, is an add-on to Google Maps that (amongst other features) overlays an avatar of your friends on Google Maps. So if you’re out-and-about you can see their location. Or if you’re on your desktop you can see a large Google Map of your friends.

Typically innovative, Google decided to take things to the next level. Wouldn’t it be neat that, if you had sufficient friends each with a T-Mobile G1 (for example), you could position them on the map to spell out a message.

Granted, you’d need to have quite a bit of spare time. But it’s doable, right?

Right.

The Google Latitude team stuck their money where their mouth is and had a bit of fun, thus:

That there is a screenshot of a Google Maps screen spelling out ‘Hi Mom’ across central San Francisco. Each little square you see is an avatar representing a physical Google team member with a phone standing in the corresponding physical location in San Francisco.

The enterprising chaps also made a video documenting the process of setting this up:

There is, I suspect, limited value in spelling out messages using your friends on Google Maps / Latitude. But it’s a super proof-of-concept for the technology.

And a reminder to get on Latitude.

Latitude, of course, isn’t yet available for the iPhone so that’s most of San Francisco ruled out. But for everyone back in Europe sporting your common-or-garden N-Series Nokia device, perhaps it’s time you and your friends spent this Saturday spelling out ‘Hello Your Majesty’ across a map of London.

(You’ll need about 10-12 friends per character.)

Originally published on Ewan.net and automatically republished here on Mobile Industry Review. View the original post.

mjelly.com mobile 2.0 service of the week – signing off with a retrospective

Friday, March 20th, 2009

Hello Hello what’s going on? what’s all this shouting?

James from mjelly here at Mobile Industry Review.

Sadly, this is the last chance for me to do a Mobile 2.0 Service of the Week post on this blog. Good luck to Ewan with the new business model and a massive thanks to him for letting me write this every week – max respects.  Thanks also to Krystal for uploading my early posts.   All is not lost – we’ll be continuing the series over at http://blog.mjelly.com

It was tough trying to decide which mobile site or app to cover for the last mobile 2.0 service of the week – Opera Mini has the most ratings on mjelly of all the downloadable apps, and mjoy is top on the mobile sites front.  So, rather than try and pick one I’m going to list all of the services we have covered over the last few months in case you missed any – listed by category – here it goes:

Communities

Mobamingle – the international version of Mobile Game Town – a Japanese mobile services with $200m in annual revenues

Peperonity – the original mobile 2.0 service and one of the biggest drivers of inventory on admob

Heysan – cool Silicon Valley mobile startup building a nice line in mobile virtual goods

Mocospace – US mobile social network with massive traction and generating big ad revenues

Flirtomatic – the world’s leading mobile dating site and top UK mobile startups

Mxit – South Africa’s massive mobile social networking platform

Media and content

Mippin – the world’s leading mobile news and web service – based in London UK

Cellufun – mobile games community

Search

Taptu – Cambridge-based mobile-focused search engine taking on Google

abphone – the French mobile vertical search engine

Browsers

UCWEB – the Chinese mobile browser that’s been downloaded 60m times

Communications and messaging

Dabr – the no.1 mobile twitter interface

ebuddy - mobile IM service downloaded 11m times

Nimbuzz – unified communication across Skype and IM

Mig33 – mobile voip and messaging app

Trutap – fantastic IM and content app that was unlucky with their investors

Fring – momo award winning VoiP and communications app

Not a bad list really – who would have imagined all of these new services even a few years ago when all mobile had going on was ringtone scams and a load of hype about “mobile TV”?

You can find all these mobile 2.0 services on mjelly which is a directory of mobile sites and free mobile software

Thanks again to Ewan and all at MIR :-)

Reblog this post [with Zemanta]

Google Latitude’s #1 Problem Can’t Be Fixed

Sunday, February 8th, 2009

You can’t fix trust. Not with a click of a button.

Have a read of this:

1 in 3 Australians will snoop in the phones of their partners (according to a Virgin Mobile survey).

60% of them do it when their partner is in the shower. 41% do it with their partner in view.

(quote from Tomi Ahonen’s presentation at Future of Mobile 2008.)

Principally I suspect the ’snooping’ is looking at text messages and recent call lists.

Now if it’s that bad without sticking ‘location’ into the mix, how is it going to be when the masses take a look at Google Latitude?

How many relationships — business and personal — are about to get absolutely nailed by the fact that your friends and partners can *SEE* where you are. Or where you were?

Witness the following frequently used explanations that I often overhear:

Chap: I’m still in the office
Google Latitude: He’s over the other side of London. With friends Graham, Paul. And, er — if you check out that Kate girl’s blog, you’ll see her Latitude puts her within 100m of him.

Chap: I’m just at the shops buying you something in that underwear shop!
Google Latitude: He’s at PC World, about a mile away from any shops that might sell underwear.

Chap: (Text message) I’m just getting on the train.
Google Latitude: He hasn’t left the office.

Chap: NO? I’m not out with the guys. I’m just getting a sandwich then I’m on my way home.
Google Latitude: Before he switched me off, he was sitting next to ‘the guys’. And that bitch girl Kate was heading this year. That was an hour ago. That’s all I know, right?

Chap: Sorry boss, I’m stuck in the snow and I won’t be able to get into work.
Google Latitude: Rubbish! He’s at the leisure park near work — next to the cinema!

Teenager: I’m, er, just going to the shops to get a can of Coke. Back in 20.
Google Latitude: He’s round that Vicky-girl’s house again.

Teenager: Yeah I’m at school. So what, mum?
Google Latitude: He’s not in school. He’s not in the same town actually. Ask him how he got to the next town?

And so on.

Despite the fact that Latitude has bucketloads of privacy goodness, the use of this technology is going to take quite a while to get a hang of…


Powered by Interactive Energy | Sign up to The Application Review newsletter