About Mobility

So Motorola invested in Scanbuy.

SCHAUMBURG, Ill. and NEW YORK - February 2, 2010 - Motorola, Inc. (NYSE: MOT), through its strategic investment arm, Motorola Ventures, today announced an investment in Scanbuy, Inc., a leader in mobile barcode solutions. Motorola acted as lead investor and was joined by Masthead Venture Partners, Hudson Ventures and select private investors. Financial terms of the investment were not disclosed.

This event says a whole lot about the importance of being product/customer-driven (i.e. Scanbuy) vs. being a patent troll (i.e. NeoMedia).

[To NeoMedia: Told you guys, people (investors) dislike patent trolls and like real businesses - focus on real products that satisfy real customer needs]

The NeoMedia investors I’m sure are going ballistic about their “IP” and how come this event was not them, and about the “agreement” between Scanbuy and NeoMedia (that settled all litigation between the companies and granted non-exclusive patent licenses to each other), and most them are clueless about what just hit them…

Congrats Scanbuy!

ceo

My good friend Michael Yuan (Ringful Health) put together a quick survey on BlackBerry to better understand popular BlackBerry versions and help them prioritize their product road-map. The survey results are public so everyone can benefit from this survey:

So, while we are working on BlackBerry versions of our apps, we are really interested in finding out where the “common denominator” is. Is it sufficient for us to target BlackBerry OS 4.6 and above? Or, do we really need to go all the way to OS 4.2 or even OS 4.0? Do we need to release a seperate app for touch screen BlackBerry devices? Can we rely on the BlackBerry AppWorld to distribute our app?

Read more about the BlackBerry survey and participate….

ceo

Rudy De Waele (@mtrends) has put together a collaborative outlook of the mobile trends for the next 10 years:

Update: Mobile Trends 2020 has been updated to include views from Russell Buckley, Tomi Ahonen, Yuri van Geest, Kelly Goto, Raj Singh, David Harper, Marc Davis, Loic LeMeur…

(You can find my contribution to Mobile Trends 2020 on slide #40)

:
To this end I have been writing down my predictions in mobile & wireless for a couple of years now. This year I thought it was the time to move on and do something different, so I asked some of my personal heroes in mobile to write down their five most significant trends for the coming decade.
:

For background information on how this came about see Rudy’s blog Mobile Trends 2020.

I am honored to be part of this collaborative effort one full of vision of the things possible during the next decade on mobile, together with an awesome/top group of Mobilists such as:

Howard Rheingold, Douglas Rushkoff, Marshall Kirkpatrick, Gerd Leonhard, Timo Arnall, Carlo Longino, Katrin Verclas, Atau Tanaka, Alan Moore, Marek Pawloski, Ajit Jaokar, Nicolas Nova, Inma Martinez, Tony Fish, Jonathan MacDonald, Willem Boijens, Carlos Domingo, Russ McGuire, Raimo van der Klein, Michael Breidenbruecker, Robert Rice, Steve O’Hear, Ted Morgan, Martin Duval, Andreas Constantinou, Fabien Girardin, Matthäus Krzykowski, Rich Wong, Andy Abramson, Ilja Laurs, David Wood, Stefan Constantinescu, Henri Moissinac, Kevin C. Tofel, Felix Petersen, Tom Hume, and yours truly.

Below is the Slideshare which you can also download.

(You can find my contribution to Mobile Trends 2020 on slide #40)

Enjoy!

ceo

Ajit wrote an interesting post titled Mobile Cloud Computing - the silver lining for Operators, where he explores Cloud Computing from an Operator perspective and discusses the synergies and opportunities for Carriers. He quotes an ABI Research report that states that cloud computing will become a “disruptive force in the mobile world: first is simply the number of users the technology has the power to reach: far more than the number of smartphone users alone. The second reason has to do with how applications are distributed today. Currently, mobile applications are tied to a carrier.”

Yes, cloud computing has in theory a great potential to reach great number of users because of the complex ecosystem that it involves - it is not only about end-users, but all the intermediaries as well, reaching all, working together.

The statement that mobile applications are tied to a carrier is a “yes and no” answer — if I’ve application A running on Android and iPhone, is that the same app ported to two platforms, or two different apps? There is no single answer as you may decide to track it as a single application on two platforms, or track each platform as its own application. And if I have a mobile web app, is that tied to a specified network provider? The answer is no.

One thing that caught my eye on Ajit’s essay was “the phrase ‘Mobile Cloud Computing’ itself has meaning only from an access standpoint. For instance, the ‘backup’ could work for any server (fixed or mobile).” But there are different views to (mobile) cloud computing in general and to better understand and rationalize (mobile) cloud computing in general — its benefits, drivers and economics, we must look at all its angles. Below I take a short stab at it, where we have:

1. Applications vs. Services or the combination.
2. The network of Constituents:
   • The PROVIDER of cloud computing infrastructure

     Provides hardware (HW) and software (SW) infrastructure, or applications and services, and/or all the above. Example are Amazon and Google and Rackspace, where latter is more on the HW side of the infrastructure while Amazon is both. Providers absorb most of the Capex behind powering (mobile) cloud computing.

     From the provider perspective it is about being competitive and win the business by offering pricing models that makes it attractive to their consumers. Attractive to customers is cheaper but reliable, and this is possible via hosted/SaaS/cloud-based approaches by deploying their own infrastructure or leveraging others.

   • The APPLICATION/SERVICES PROVIDER or (1st tier consumer) of cloud computing

     Are typically businesses consumers of cloud computing infrastructure and providers of applications and/or services. Examples like Google are both providers of cloud computing infrastructure and of applications and services. But the majority are providers of apps and services running on top of infrastructure provided by others (see PROVIDER above).

     From this tier-1 customer perspective is about minimizing IT Capex by moving such Capex costs to Opex. These customers look for pricing models based on number of seats and/or devices while minimizing their investment on expensive hardware and software and even IT operational investments; it helps them minimize risk ($) with respect to unknowns. They drive the Providers with requirements on scalability, high availability, multi-tenancy and security, to mention a few.

   • The DEVELOPER (2nd tier consumer) of cloud computing

     Are developers of applications and services. These applications are typically hosted on the cloud (see Provider above). Even client-based applications are increasingly consuming services on the cloud.Developers look to leverage the services which are hard to build but easier and cheaper to consume that gives them richness for their apps, with examples that include Maps and location, photos and storage. These developers offer their applications and services on the web via SaaS models running on other’s HW and SW infrastructure (see above).

   • The END-USER (3rd tier consumer) of cloud computing

     Are the typical end-users of applications. They don’t consumer services directly, but consume applications that in turn consume services on the cloud. These level of consumers really don’t care if the app is hosted or not. They only care that the app works WELL when needed with things such as security and high-availability and well usage experiences and etc, all being part of the package.

The following illustrates an example of this complex network of and between cloud computing participants:

Different constituents drive the requirements on different parts of cloud computing and in different ways. But at the end, cloud computing is mainly about economics and driven by providers and their Tier-1 customers, the application/services providers who in turn are driven by end-users and developers. At the end it is a network of application/services providers consuming other application/services providers via many infrastructure providers, and levels of providers and end-users and developers. SLAs are so important in this “new” world and Service Level Agreements (SLAs) are probably one of the most important aspects to make all this work; does SLA equal trust?

From the Mobile Network Operator (MNO) cloud-based / hosting is becoming increasingly important, especially when doing initial deployments of new technologies as it helps them minimize risk with respect to unknowns. From the developer’s perspective their dependencies on services on the web continues to increase (i.e. connected apps); even their local/native connected applications are big users of services on the web.

From the mobile perspective, consumption of centralized applications (mobile web) and services (both mobile web and local apps) will continue to be the trend i.e. consumption of software and services as a service on the web/cloud. The idea of mobile handsets as “servers” or provider of services is a very interesting one indeed, but we are not there yet and it will take longer to get there.

ceo

Will RIM adopt Android? A very interesting thought indeed. But why or not would RIM do such a thing? Some thoughts below:

Why this would be unlikely?

• “Not built here” mentality — this is probably the biggest hurdle for them. There will be internal people resistant to the change, resistant to drastic changes and “throwing away” all legacy work, but sometimes, this must be done;
• “Why promote a competitor” mentality — this would be a weak argument, due to the “pros” - see below.

Why this would be likely?

• Deliver more value while reducing overall investments/expenses;
• Overall reduced Build of Materials (BOM) costs — reduced R&D related to OS; reduce OS team size that instead can focus on value for end-users (apps) and developers. No need to re-invent App Stores. Leverage Google infrastructure (such as Maps which will be an expected feature by end-users) while adding own differentiators on top;
• Android OS is advanced and customizable, and open — OSes are complicated and expensive handset elements. Android is based on Linux which is stable, which is open, and which is proven. The Android APIs are robust. The whole environment is open. And is community-based. Able to add own differentiators on top;
• Java-based satisfies current developer base — no new programming languages to learn or adapt to. Tons of tools that already exists, from UI to IDEs;
• Provides migration path — RIM can decide to continue exposing existing BB Java-based APIs and application life-cycles as needed on top of Android as a migration path;
• IDE tools already in place — Eclipse is a very good IDE. There is NetBeans too. Both are open and community based and very complete. There would be no need for their own BlackBerry-specific Java-IDE and that t team can instead focus on BlackBerry-specific extensions to Eclipse, NetBeans and/or other - in other words, a much cheaper route to developer tools than developing or maintaining developer tools from the ground up;
• Business models provided by Google — such as search, Maps, other and provide additional revenue streams for RIM.

As you can see, there are a number of positives for going the Android path; let’s see what will happen.

BTW, the above also applies to Nokia, but let’s see if they end up buying Palm instead…

CEO

BONDI 1.1 is now in Candidate Release and it is open to public for feedback.

Note that this phase will close on the 2nd of December so you’ll need to get your comments in before then.

See OMTP and BONDI at the betavine website.

What is BONDI?

In short BONDI is a set of specifications, reference implementation and compliance criteria for the creation of mobile web apps based on Widgets.

This means that BONDI widgets rely on the web-runtimes or browser as its execution environment. BONDI defines a set of APIs that provides BONDI widgets with access to the handset functionality such as access to camera, contacts and location information.

The BONDI official website contains all the information you need to learn more.

From the BONDI website:

During 2007 and 2008, it became increasingly apparent that the future direction and success of the mobile web could be harmed without a concerted effort to drive a standardized approach to how web applications access the key local capabilities on the mobile device.

If web applications had to use different APIs (for the same capability) on different devices and platforms, then development of web applications which work on any mobile device would not happen. On top of this, the risk of malicious web applications having free access to local mobile capabilities is unacceptable. Therefore, a need to create some form of security layer to protect the user from harm was essential.

It is with this background that OMTP launched its BONDI project with the aim of acting as a catalyst to drive the standardization of a small set of key interfaces from web services to mobile devices and also to put in place a well understood and user controlled security policy with which to protect the user.

BONDI consists of several activities, each of which interacts and as a whole builds towards the aim defined above.

Interface Requirements — A high level definition of the BONDI interfaces which include a dynamic API which is remotely updateable once the device is in the field

Security and Architecture requirements — Requirements for BONDI architectural constraints and for the security policy which protects the user from harm

API specifications — A set of Doxygen generated HTML pages that define the syntax and semantics of the BONDI APIs

Security Policy DTD — An interoperable XML description of the security policy which defines the access that a particular web application and widget will have to the BONDI APIs.

Reference Implementation (RI) — The RI is a real concrete example (using Windows Mobile as the platform) of how the interfaces and security specifications should be implemented. The RI SDK contains API documentation and example code.

Compliance Criteria — A set of criteria which may be used to judge compliance of implementation against the defined standard and RI.

The BONDI Reference Implementation has been created as an Open Source project. This enables both OMTP Members and Participants as well as non members to collaborate on the creation of a rapidly iterating and testable implementation in a public arena. The use of real code in a RI ensures that other implementations for different devices and platforms can be tested and declared compliant against well defined criteria.

ceo

It almost is the end of 2009. And where does near-field proximity communication-based applications stand? From mobile marketing, to customer loyalty, payments and authentication, to information exchange, transportation and health-care. Well, it still stands very far from its full potential.

Regardless of its potential and benefits to consumers (which is about convenience) and the real business models that exist, NFC have had major adoption (growing) pains. Pilots have said again and again that consumers do like the convenience, but it is the enablement problem what has basically prevented its adoption. It took Bluetooth more than 10 years and it will take NFC the same.

If we wanted to deliver the convenience benefits of proximity-interactions today, what is the answer? Will it be RFID or NFC the one that stands up at the end? Will it be embedded chip-sets, USB or microSD, or plain RFID stickers?

While not the perfect vision the NFC Forum members had, sticker (RFID) are the short-term solution for this today. Some call it an interim solution, but we will see.

From Blaze Mobile (to whom I provided my services to back when they were called MobileCandyDish), to Giesecke & Devrient, Alcatel-Lucent (my current employer), Oberthur Technologies, MasterCard, First Data, and Tetherball, they all are dealing with the realities of NFC and while waiting for it have decided to follow the “RFID sticker” route. Blaze Mobile was one of the first one years ago.

Stickers. But RFID stickers are very limiting as they are limited to “one function”. How many stickers can you fit, or want to fit, on the back of your phone? Yet stickers bring NFC close to reality. Expect branded and colorful RFID stickers of all kinds.

When I saw ViVOTech (a leader on NFC and contactless in general) recently announce their ViVOtag product; in other words, even ViVOtech has submitted to the realities of NFC, I said to myself, “NFC is dead, long live NFC” - this time is the sticker way. Yuck. See ViVOtech Launches ViVOtag.

There are other vendors going the route of USB or microSD NFC devices such as Tyfone, Giesecke & Devrient and DeviceFidelity. Another example is Sony — see Sony’s next generation Memory Stick which might potentially be integrated with NFC.

In the meantime Gemalto Boosts Rollout of SIM-Based Mobile Contactless Services and touchatag, an Alcatel-Lucent venture and Clear2Pay partner on technology for contactless payments.

And as I wrote before, Will the iPhone trigger the Mobile RFID/NFC revolution?

So there is lots of interest, noise and activity related to mobile NFC/RFID. It is a matter of time, I’m convinced. But the ideal solution is NOT stickers, yet stickers are the fastest and cheaper way to get there, and because of that, the best way to validate the applications and models. And once that happens, I hope that for the sake of the consumers themselves that we move on to a solution that allows for MULTIPLE applications such as smart-cards or handset-based (which includes USB or microSD-based) approaches.

Now, last but probably the top deployment reason why proximity interactions based on NFC/RFID are extremely important: to work around that pesky patent on barcode interactions (i.e. nn-ee-oo-mm-ee-dd-ii-aa); with the NFC/RFID path there is clear and well documented (including in the NFC standards) prior-art.

It is time for operators and device manufacturers to push for NFC. Yes, enabling NFC require investment but pilots already provided good results. Go sticker in the interim to validate, and remember that it is about the applications and usability. No need to wait on Apple, again, to define the path. (The exception to all this is Nokia who has been forward looking since day one, with the handsets, APIs, documentation and toolkit to make this happen.)

ceo

Will history repeat itself?

There was/is the 12 keys keypad cellphone.
And few care about Touch.
Then came the iPhone.
Now everyone loves Touch.

There was the operator Deck.
Everyone hated the Deck.
Then came Apple.
And created the App Store.
Now everyone loves the App Stores.
And everyone still hates the Deck.

There was RFID. Then came NFC.
With clear use-cases and business-models.
Yet it has taken forever to deploy this.
Pilots and more pilots, when it is going to end?
Embedded chip-sets or stickers.
But few seem get it. (Nokia does!)
Who is going to take the first big step?
Operators don’t get it. Or do they?
And stuck with pilots they are.
“Hey, this is great!”, the pilots say.
Enablement is expensive! That is what they say.
But guess what?
Proximity support, the iPhone will have.
And all of the sudden, “RFID/NFC on the go” everyone will want.

And I say, if the iPhone introduces support for proximity, it will trigger the mobile RFID/NFC revolution… Wanna bet?

Here, some rumors via the NFC World Blog:

NFC specialist Narian Technologies and who runs the Near Field Communications Group on Linkedin.com, has reported the following:

Had to share this news. A highly reliable source has informed me that Apple has built some prototypes of the next gen iPhone with an RFID reader built in and they have seen it in action. So its not full NFC but its a start for real service discovery and I’m told that the reaction was very positive that we can expect this in the next gen iPhone.

If Apple does it, expect every phone manufacturer and their sister to begin pumping out NFC enabled phones, at least for service discovery and sync.

This just reinforces what we knew based on the two separate patents Apple submitted that had the iPhone enabled to read RFID tags. I’m told that the touch project video and the BT SIG’s specs were all driving forces to push this forward as well as other factors.

Guess I’ll be touching my iPhone to my Mac to link them together to sync iTunes by next year.

Operators have so much infrastructure already in place and it has taken them so many years to take advantage of it in news ways — to leverage such infrastructure for their own benefit and the benefit of the ecosystem, by repackaging and offering this infrastructure as “open” Services: their payment system, their marketing/reach methods, their customer support systems and other…

Recently T-Mobile announced (PC World) that they will start support for on-bill Android App Market purchases; up to this point the only way to buy applications on the Google App Market has been via Google Checkout.

“T-Mobile will let its subscribers pay for Android applications on their monthly mobile bills starting Nov. 17, also introducing its own section of the Android Marketplace that day.”

These news though, I’m surprised, haven’t made much noise within the developer community yet. This announcement is VERY interesting and important. A number of us, including William Volk (Extremepreneur blog) have been advocating this as an important approach to help simplify the app store application purchase (and/or purchase decision) and as a way to better ‘compete’ with Apple who already have a robust, established, recognized and independent (from operators) billing/payment framework.

For developers, this on-bill purchase/payment support means (in theory) that because the process of buying apps is becoming simpler for subscribers (no registration required, one-click buy) the resistance to buy applications should be less than before, and thus we should see an increase on the number of apps being purchased on Android and thus the Android platform should be more attractive to target since again, in theory, the ROI for it should also increase as a result of the introduced app purchase simplicity.

“Brodman characterized T-Mobile’s billing system as a simple, “one-click” purchase method that doesn’t require the user to give credit-card information or personal credentials. So far, Android users generally have had to use Google Checkout to pay for applications, but Google has said it wants a variety of payment choices for the market.”

Is the fact that there hasn’t been much (positive or negative) reaction to this announcement an indication that on-bill purchases don’t matter? Perhaps it is an indication that this is just a no-brainer and was just expected. Time will tell.

T-Mobile has taken the first step into this combined billing approach to app stores. This will set a precedence that will not favor Apple. Little by little and over the years, slowly but surely, operators have been understanding (or forced to understand) and have been learning and adapting. This is the only way operators will regain their position and be recognized within the ecosystem in ways that allows then to compete with companies such as Apple and Google — by themselves becoming part of the ecosystem in positive ways. It will take them years still, but they are learning. We have seen the mobile/wireless industry transforming from 1) being operator-centered, 2) to recently becoming ecosystem-centered where the developer community and users and open systems are at the center and where the operator is not viewed as a positive contributor or partner. But if operators adapt well (and time is of essence for them) we will see 3) an ecosystem where the operator becomes a very important ecosystem partner, which is anyways what they always have wanted, to offer services and be recognized beyond a pure pipe.

Apple has iTunes, Google has Checkout and the Operators have a proven robust billing/payment infrastructure (and other infrastructure) already in place for years that now they can extend to app stores. Let’s see if they will take advantage of this new opportunity and let’s see how this will play out.

In conclusion, T-Mobile’s on-bill support will be a great experiment that will help determine if this converged or combined billing/payment approach will be a positive influence on people’s decision to buy mobile applications. Logic dictates that it should…

ceo

Responding to Tomi’s thread on ForumOxford, where he wrote: “The best phone in the world cannot take the mobile phone market, unless there is distribution.”

Yes. Which is exactly why Android seems to me that it will be widely adopted. And it will be widely adopted because for device manufacturers it is cheaper this way to develop a high-end handset — OSes are complicated (and thus expensive) things that are at the center of the handset. I expect handset manufacturers to leverage all that investment and research by Google; then add their touch via the UI.

Then there is buzz which drive sales opportunities. And buzz has a timing-window associated with it. iPhone has buzz. Android has buzz today. It is my impression that Nokia (and Symbian) missed that buzz window of opportunity.

Last, pre-installed apps are so year 2000. App stores are the new deck. As we are witnessing, app stores are very important for all smart-phones (and handsets that run apps). And as users get more educated and thus more sophisticated, users won’t settle for apps they don’t want. (Expect typical apps such as YouTube, Gmail, exchange, camera, etc. to be pre-installed though). And related to this, and something Jason (Paxmodept) wrote on his blog, is the anticipated “new” issue that will pop-up: Crapware — I’m afraid handset manufacturers will force pre-installed apps that are Crapware *and* that can’t be uninstalled unless breaking into the OS.

ceo

While looking for information on how CTIA 2009 in San Diego went, I found an article by Richard Wong (who is a venture capitalist with Accel Partners) titled on “The rise of open mobile (and congratulations Android team)“.

A good article by Richard, he reminisces on how mobility used to be in the early days of apps (i.e. year ~2000) when operators were in total control — I do remember those days very well and all the unnecessary control and FUD that literally pushed innovation back about 10 years. Richard then compares that past with what he observed at CTIA 2009 and the lots of noise related to Android — the shift from an operator-controlled mobile world to “Open Mobile” players such as Android.

I have written about this before, on how “control” have been and will continue to shift from the operator and to the ecosystem — the developer and community where developers create (and add) value via their software innovations in applications, where the ecosystem, open systems and common sense will be the drivers for success, where the new deck is the “deck that is on the cloud” and users drive which application succeed or not via simple “application demand”, ranking, recommendations and comments.

For this shift that we are (finally) getting to see we have to thank Apple and Google, but these are recent players. We must recognize the impact made by the Mobile Web and also what triggered it all back in 1999 — Sun with their mobile Java technologies as well as the good old WAP.

I do believe the Android market is going to explode globally becoming a predominant mobile platform together with the iPhone, and that native/local apps will continue to rule for quite a while.

Update Oct 21: Days after I wrote the above, TechCrunch wrote a piece validating my post above on Android; see Android Avalanche: A Complete List Of The Android Phones So Far.

ceo

I’ve updated my page on Physical and Web Interactions…

…where the topic that “Everything around us can be made interactive (and thus is data) and at the center of this is the mobile handset”.

See Physical and Web Interactions.

ceo

A continuation of one of my favorite research topics, the mobile context and the meaning of interactions, below is my latest as presented at the 2009 Demand Analytics conference — this time with focus on real-time demand data, the consumer and businesses. The audience was mainly category and brand managers for big consumer packaged goods (CPG) companies.

See the related presentation Mobility and People’s Context, Interactions and Data, which was originally presented at Design4Mobile 2008.

ceo

Is mobile handset differentiation based on hardware coming to an end?

Back in 2007 I wrote a piece on my blog titled: The future of handset design: from hardware to software. And today this is getting more real (and validated) than ever.

When it comes to mobile handsets the rate of innovation introduced via hardware (HW) vs. sofware (SW) is and will be mainly on the SW side.

Differentiation, especially on common platforms (such as Android), will be primarily driven by SW, this is: Innovation on UIs and interface paradigms (on Android we can see this with the introduction of Moto Blur and HTC Sense), better applications (developer ecosystem adding lots of application that in turn adds to the usefulness of the handset), and better services (some phones will be very good at social things, while others at music, and so on). At the end it is SW what makes the handset more dynamic and useful and different.

Today is a great time for those doing R&D in the areas of Human-Computer Interactions (HCI).

Differentiation is necessary. But typically differentiation drives fragmentation. So the follow-up big question is on the fragmentation introduced by the different UI paradigms. Will applications need to be adapted to each new paradigm (i.e. as in many versions?). Yes, very likely.

Developers writing SW for the iPhone only have one paradigm to worry about. On the Android though, as expected we are seeing different UI paradigms (with related APIs) but fortunately the rest of the platform should remain consistent across manufacturers so fragmentation is hopefully localized to the UI only. For mobile Java (beyond Android) fragmentation is yet to be solved. For mobile web and widgets, the same although I am seeing a lot of noise around the JIL Widget SDK.

Fragmentation across platforms will continue. Fragmentation within a single platform shall be localized to the user interface (or the user interactions). Allowing for the UI to be redefined/reconfigured allows for incredible innovation on human to machine interactions which basically redefines the perception for a given handset. The next best thing is re-configurable software and hardware, but for that you will have to go play with platforms such as Bug Labs (which BTW is an extremely cool platform).

ceo

(Images sources: PopSci, Nokia, HTC Phones, Benzinga)

Mike Rowehl and Gregory Gorman are putting together the 4th Annual Mobile 2.0 Silicon Valley on October 15-16, 2009:

Day One:

• Business Day: Oct 15, 2009, 08:30am - 07:30pm
• Grand Hyatt San Francisco, San Francisco, CA, USA

Day Two:

• Developer Day: Oct 16, 2009, 8:30 - 5:30pm
• Microsoft Conference Center, Mountain View, CA, USA

MOBILE 2.0 Silicon Valley 2009 is a two-day event on October 15th (Business Day) and October 16th (Developer Day) 2009, focusing on Mobile Applications and Services, Mobile Ecosystems, and Disruptive Mobile Innovation, as well as providing a deep dive into technology platforms from a Developer’s perspective.

Mobile 2.0 Silicon Valley is all about giving our audience the opportunity to learn, network and voice their views. Our Event does not talk at you — you are the Mobile Community and we strive to create an atmosphere that challenges your business assumptions and provides you with hands-on understanding of mobile platforms.

Also see About Mobile 2.0.

Discount for MobileMonday Members

MondayMonday members can receive a discount of $70.00 on the business day registration fee and a discount of $20.00 on the Developer Day. Please contact us at info@mobile2event.com for the discount codes.

ceo