I recently moderated the “Go to Market” panel at Mobile 2.0 last week. I took the path of pretending to be a developer and asking my panelists what I should do.
I started by asking the panel what platform should I build for 1st, 2nd and 3rd. I was expecting a very rationale answer based on either monetization or distribution (eg If your want high volume, choose platform X, if you want monetization, choose platform Y, if you want in-app…).
To my surprise, the answers were quite different:
1. Peter at AngryBirds chose iPhone first because they felt that if they couldn’t win on iPhone, then they wouldn’t on any other platform? Basically, they wanted to start in the most competitive marketplace.
2. An audience member chose Android first because he wanted to learn Java (but another said they chose Android first because they knew Java). It’s been so long since I have developed that I forgot how much of choosing a first framework or environment is starting with what you know or the opportunity to learn a new language.
3. Surprisingly or not surprisingly, the majority of the audience hadn’t built an app for a 2nd platform. They built for their initial platform and then of course planned to build and/or port to a 2nd platform but they haven’t yet done so. And this brings up an interesting point, most long-tail developers don’t have the resources to build and maintain for two platforms so the first platform they build for will likely be the platform they will stay with (and this was the case with even a Symbian developer in the audience)
4. This should be obvious but a fair number of folks in the audience chose their first platform based on which phones they own. I’ve been spoiled by living in the Bay Area and do not normally think of access to phone to being the inhibitor but with the broader long-tail, this is absolutely a factor.
5. Most surprising, it was me who mentioned choosing a platform based on monetization and distribution which seemed most rationale to the business person but not necessarily to the long-tail developer community (and psychology).
What criteria do you use to choose your first platform?
Follow This Blog Via Email
- SXSW 2016: Messaging Bots
- Reflecting on the Productivity Category
- Tech Discrimination
- Daily Active Users Don’t Matter!
- IOT: The Competition for Attention
- How Google and Others Are Using Data Science to Speed Up Productivity
- Why I’m Excited About Google Glass?
- Context Is a Layer and Not a Category
- Sales 2.0: The Bottoms-Up Sales Model
- Is UX Going to be Commoditized Next?
- To Win Enterprise, Target the Consumer
- Using a Chromebook for a Week
- Android (and the Tab!) in the Enterprise
- Ad Learnings from Recipe Search
- CPA Advertising on Mobile
- Enterprise Mobile Is Hot!
- Network Responsibility
- In-Door Mapping
- The Social Network
- Using a Mobile Phone to Drive Behavior Change
- Apps vs. Web Apps
- Understanding Developer Psychology
- Are Batteries Improving?
- Over the Air and Emerging Markets
- Are Platform Game Lobbies the Next Social Graph?
- Are Plugins (and Flash) Going Away?
- Lessons Learned in Monetization
- Understanding the Emerging Market
- OEMs, Please Choose
- Understanding PDE (Positional Determining Entity)
- Has the Power Shifted Back to Operators?
- Is the Killer App the App Store?
- Navigating the Mobile Content Landscape
- Wholesale Application Community
- Sharing Overload?
- The Ad Ballot
- Device Patent Wars
- Is Apple Making a Mobile Wallet Play?
- Top 6 Reasons Why Nokia Doesn’t Have a Capacitive Touch Screen
- Mobile Trends 2020
- Mobile Taking a Cue From the Travel Industry
- CTIA Party Analysis
- Measuring AT&Ts Network
- Mobile Cloud Computing
- Mobile Beyond & NARIP
- Mobile 2.0 Advertising Notes
- Carnival of the Mobilists #193
- The Broken Subscription Model
- The Mobile Reserve
- The Fragmented Web
- Got to Love the Music Industry
- What Platforms Should I Build For?
- To Operator or to Not to Operator
- What Do Bankers Do?
- My Older Posts