And with the mass consumer comes the money, especially when you drive your business like Google does.

Android will attract the mass consumer, because with the Android OS many newcomers and companies in emerging markets have now the chance to produce low end and cheap devices, that are, in most areas, compatible with the high end Android devices.

It’s just the Wintel way of wining the mass market, here you will find the same fragmentation issues today.

The mainstream apps run on every Wintel device, but there are many special apps, that run only on a specific Wintel device (think of games and graphic adapters). But the user doesn’t care, as long as he has his most importants apps and knows, how to run the more sophisticated ones (if he sometimes needs to).

Wintel is cheap, cheaper than anything else (today), as Android will be in the future.

The Apple iPhone is and will probably stay a great phone, but it will never, because of its price structure, extend its market share to the middle and low end of the mass market.

But in the long run Google needs the mass market, as many others do, too, despite Apple .

• Neocore
• Benchmark
• Linpack

And if you want to know, if your Nexus includes a working multitouch functionality, just download this little app.

Point you Android browser to the link above and try to wipe around with two fingers. If the colored cycles will follow your fingers, everything is fine. If not, it isn’t, but don’t be scared too much.

Mine isn’t working either, but when do you really need this?

But since yesterday it even will be become much harder.

The problem of Social Media and Twitter in special: They are, technically seen, build for the end user and are heavily open either (what I like as private person).

These services don’t provide security mechanism old and traditional business units require, before they will rely on something like Twitter.

For Twitter this could mean (for example):

• Special business accounts, where OAuth, the Twitter API and the public access is deactivated
• Business accounts with a special business API, where only a dedicated client (client certificates) is allowed to connect
• Something like a Twitter workflow, where two or more users in an organization work on the same tweet
• Something like a twitter transaction number, where a tweet will only be posted, if you input the correct number
• And some more…

And even if you build some of these requirements into your own Twitter or Social Media client, these services still remain open and insecure, because the general access stays unchanged.

Yes, I know, all these requirements usually don’t fit to the general idea of Social Media or Web 2.0, but, if we want huge and traditional companies to join the ‘Social Media Club’,  then these services have to adapt conventional security and business pattern.

Find out this and more at our next event and register NOW, if you haven’t already done so. Looking forward to seeing you there!

Visit MobileMonday Germany at: http://www.mobile-monday.de

• The agility, the openness and the dynamic of Android produces very fast and often new versions with new and cool functionality. This leads to the fact that just released and basically cool handsets are outdated before they reach the market. Thus manufacturers of these mobiles have difficulties in selling their new products. At the moment everybody wants the Nexus (with 2.1) or at least the Droid (with 2.0.1). The really cool people don’t want to buy an Android  mobile with version 1.5 or 1.6. In countries like Germany (where we don’t have the Nexus yet) this can – maybe – result in a (never ending) wait-and-see attitude of the customer.
• This same agility enforces the handset manufacturers to hire more and more Android specialists to adapt the newest Android versions, especially when they have to migrate proprietary Android extension (e.g. own home screens). This makes Android, although free of charge, maybe more expensive than other operating systems. And the manufacturers can’t use their Android stuff to develop important apps or other services to attract new customers.

The very successful iPhone OS doesn’t have these problems…

AppAware, once installed on your Android device, informs your followers (including Twitter if you like to) about your app usage (“what do I install and deinstall?”).
But AppAware also informs me, and even localized, what other users are doing with their apps on their Android mobile.

For this purpose Android provides an API (via the BroadcastReceiver class) to let any application know whats going up on the user’s handset. With this API your/any app can listen to system intents (a kind of messaging on the Android platform) and react.

Something, I guess ,AppAware has used for it’s new and brilliant service.

And think about what else might be possible, when millions of handsets are collecting data about and broadcasting their behaviour to the cloud…

AppAware can be found and downloaded in the Android Market.

I’ve tested the Nexus now for 12 hours and I never had a smartphone that was so fast, had such a brilliant display, a perfect usability and such a very flexible and modern operating system.
And I had or have them all: iPhone 3G, Magic, Dream, Droid, some Blackberrys and many Nokias.

But yesterday I also tested the connectivity of the Nexus in two large German cities and compared it to the Motorola Droid .
I drove with my car through the streets both handsets connected with the same provider.

And the result was: The Droid often offered HSDPA or 3G while the Nexus was only connected via 3G or EDGE.

Most of the time the Droid operated on one connectivity level better than the Nexus, and I’ve installed the given 3G Nexus Android patch before.

Due to the fact we are talking about smartphones whose nature is being permanently connected to the internet these results are, in my eyes, very important.

But I don’t believe (as the link above documents as well) this issue is related to Android or Google. It’s a hardware issue and thus a problem of HTC (the reason why the Nexus 2 might become Motorola device, who knows?)

Google has surprised us with a brilliant idea, but with a bit confusing, instable and heterogeneous clients (especially for the mobile), but Buzz is free for all and available for almost every operation system and mobile.

Google created Android, but in many cases I have the impression Google is still missing the feeling for the mobile business, many things they do in this space (App Store, Nexus, Wave and now Buzz) is, in the beginning, a kind of immature and sluggish business and  technology.

That’s the difference between Apple and Google, I love both companies, and it’s good to see both alive and kicking here on earth. They are so different, but both very successful in how they do things and thus important for our further development.

Get a visionary introduction from this video:

And if you want to book this coming event go here.

Read this related blog post and you know what I mean.

One year back we started with the HTC Android G1, and to be honest, it’s a good phone, but not comparable to the iPhone.
Now, 12 months later, have a look at the Top Five Android phones, and if you own the G1, the Apple iPhone, the Motorola Droid and the HTC Google Nexus, as I do, you will follow my thoughts.

And what has happened the same time in the iPhone space, the last 12 months? Almost nothing!

That’s the difference when things are free and lot of creative people can play around with them…

As globally renowned thought-leaders of the Mobile Internet development we know this to be the time to address You, the Mobile developer community, with our brand new format, which is aimed to go well beyond our regular meetings.

Celebrating this birthday we are delighted to announce that we will be raffling off 3 brand new Nexus One handsets at the first m2d2. The Nexus One showcases the latest innovations of the Android platform, our m2d2 topic!

The Google Nexus is sold online by Google at www.google.com/phone.

Google needs an app store on the client. Not only because Apple has one like iTunes or because it’s sexy today to have one.

Google needs its app store on the client to round up the Android eco system:
The user needs an adequate opportunity to manage its Android handset on his preferred client – to download (buy) apps, music, videos and to synchronize those artefacts whenever he wants to.

Google needs the app store the establish their e-commerce platform on the user’s client machine.

From my point of view neither Google’s mobile e-commerce nor Android will and can survive without something comparable to iTunes.

Why are they waiting?

But, although and technical seen, nearly every app store model is the same, they aren’t at all, if we refer to the debate above.

There are two – totally different – approaches to use the/an app store model.

The first one is the ‘Wallet Garden’ – we know this term from the early mobile internet days. The only way of an app to find its way to the client is through the one and only app store on this device.
This is the Dictator App Store, not only the app store is controlled, the complete device is controlled by one party.

The other app store model is the Federated App Store Model. Individually considered this app store is comparable to the Dictator Model, but it differs in the way, that this model allows the co-existence of several app stores on one device from different independent parties and an app to find the way to its client by-passing the app store.

Now it’s up to you, which platform supports which model!

But besides the fact that the tablet architecture in general isn’t a suitable model for me and my use cases, because if I have the space for a tablet, I prefer my MacBook Air, the iPad seems to be, at this stage, too close for me.

It adapts the closed iPhone app store business model, which is acceptable for me on a smartphone, but if I have something in size like the iPad, I want the freedom of a laptop – I’m used to since years.

If I can only run and install apps, that will come thru the app store powered by only one carrier then I definetly prefer my laptop, where I can choose how to power and how to install apps.

It’s that easy…

We’ve learned the Mobile App can make money and can solve some today’s publisher’s issues either.

And the forecast for 2010 and the following years is even brighter.

But nothing counts, if you do not have a suitable developer eco-system and a vital developer community.

For this reason the worldwide MobileMonday mobile community has started a new event series called m2d2 (= mobilemonday developer day).

This event series will start on the 23rd of February in Dusseldorf Germany, but will be extended all over the world (next m2d2 will take place in Munich in May).

Everything will be free (as usual for the MobileMonday community), so stay tuned for updates as a developer, and if you are somebody, who takes care about developers, come and visit your community here at the m2d2.

As many news already have summarized: 2010 will be the year of Google.

So why shouldn’t we create a new job profile, a new job specialization?

Somebody, who knows all the services and solutions of Google and thus can advice and implement in this broad area of Google. Starting with some kind of SEO, selecting useful Google Apps, building an development environment with the Google App Engine, developing some apps, introducing ChromeOS, Chrome, Mail, Calendar, choosing and selecting helpful Chrome extensions, extending company channels with Android and so on and so forth…

Much more than SEO with Google was in the past – comparable to the SAP consultant or other specialists in similar tech areas.

And if you believe such a new job profile makes sense, then you should also think about professional Google education and consultancies.

I believe, especially for small and mid size companies, it might be an interesting model to rely on the many (cloud) services and solutions of Google and these, of course, need advice how to profit from these.

And last but not least:  Google Consultant somehow sounds sexy…