After my trip to Google I/O 2013 last year, I wrote about the development of applications on the Google Glass. As a prequel to the review on Google Glass (which I have been recently gotten one unit through a private unit via the glass explorer program and using it for at least a week), I thought it might be good to share this earlier article I have written about how one should think about developing applications. One important thinking is that the development philosophy on the Glass follows closer to web development than native mobile application in either iOS or Android SDK.
Continue reading First Encounters with Google Glass: What I learned about developing apps on the glass
In building a native mobile application either for your startup or corporation, one major question for entrepreneurs and corporate executives is, “Which mobile platform should I build the native mobile application that will further the business objective of my company?” We should be of no delusion that it is now a two horses race between Android and iOS, with the rest being a far distant third. The question now becomes, “Android of iOS first?” I propose a checklist in how one should tackle this question for both start-ups and corporations.
Continue reading Android or iOS first? A definitive guide for startups & corporations
Recently, I made a bet with a good friend (who is currently a CFO of a retail giant in China) on whether Apple needs market share to be successful. Our bet set the timeline about two years from now and the thesis is that Apple does not need market share to have high profit margins against the android operating system onslaught from Google and their original equipment manufacturers (OEMs) and user adoption & retention. Obviously, you know which side I am from. Some analysts often drew their arguments that Apple needs market share to succeed based on the personal computers (PCs) and browser wars from 1980s to 2000s. I am going to draw on the metaphor on why the market share argument do not work in our world today and Apple should be Louis Vuitton and not Zara to be successful.
Continue reading Apple should be a Louis Vuitton and not Zara
It’s a common phenomenon in startups that the hustler or what I called the business guy, typically goes out to search for the technology co-founder. In meeting entrepreneurs via my network fund, they often asked me one common question after the initial pitching of the idea, “I am looking for a technology co-founder who can get this done. Can you help me with this?” Of course, 99% of these startup co-founders whether they are rookies or MBA students have no clue to who they really want to hire. Hence, this article is addressed to people who might want my advice on seeking out technology co-founders.
Continue reading My Advice for Finding Technology Co-Founders
In the past few years, most companies advocate the myth of outsourcing as a way to cut costs on engineering. One myth advocated by people in business strategy and operations to justify why it is better to outsource from an expensive place to a less expensive one is that only the specifications of the product input leading to the outcome of the product matters and not the quality of engineering. The problem with that view is that you pay peanuts to get monkeys, i.e. you pay less to run an engineering team because it affects your profits and loss (P&L) but you end up giving a lower quality software engineering product to your customers. That explains why a lot of companies, particularly in Asia cannot take innovation to the next level. With the evolution of the product manager to lower the quality risk, does that mean that there is no room for in-house engineering? Here are some thoughts on the management myth about in house and outsourced engineering. Continue reading Debunking the Management Myth about In House vs Outsourced Engineering