There's only one possible addendum I'd make: API API API API API API.
Mobile is ridiculously important, and a great way to go mobile is to build a solid API and then consume it with your mobile app. If you do a half-decent job of this you'll have all sorts of flexibility.
That said, I don't want to take anything away from the first few paragraphs of MG Siegler's post. They're dead on.
Mobile is a clear choice for apps targeted at the consumer market.
However, there is still huge opportunities in the B2B and enterprise market. It depends on the problem you're solving, but in most cases the desktop is still the natural place to start if you're going after business users. Examples: Basecamp, Salesforce, Kissmetrics.
This is dreadfully wrong. There's a bunch of activity in the healthcare space, which is currently heavily reliant on pen and paper. They will soon transition to PC's, many institutions already have, and the results will be dramatic. Mobile will play an important role, but most likely in conjunction with desktop based devices that people work from, because of the extent of typing that remains involved.
There's something called target customer segmentation. If building for consumers, do a website and/or mobile which are great for consumption (hence the name consumers). If building a "creation" app for businesses (ie. payroll mgmt, Photoshop, etc.) then do a desktop and/or website with perhaps a simplified companion mobile app.
Seems like his market research is purely based upon himself. To expand the control group to 2, I have a smartphone but only use it secondarily when I dont have access to my laptop - to me poking around on a 4 inch screen is usually an inferior experience in many cases.
Smart phones and tablets are decent for consumption but their main limitation is screen real estate and efficient user input (which usually refers to typing). It really is a case by case basis (whats the product, who are your users, etc) and usually the answer is that you're going to want to be well represented across all typical client types.
6 comments
[ 3.0 ms ] story [ 19.2 ms ] threadMobile is ridiculously important, and a great way to go mobile is to build a solid API and then consume it with your mobile app. If you do a half-decent job of this you'll have all sorts of flexibility.
That said, I don't want to take anything away from the first few paragraphs of MG Siegler's post. They're dead on.
--
Sent from my mobile device.
Mobile is a clear choice for apps targeted at the consumer market.
However, there is still huge opportunities in the B2B and enterprise market. It depends on the problem you're solving, but in most cases the desktop is still the natural place to start if you're going after business users. Examples: Basecamp, Salesforce, Kissmetrics.
There will always be workstations with big screens.
A physically bigger computer will always have more power and the appetite for power is unlimited. Good enough, satisfies most, but not the nerds.
I don't like little computers, in the same way Americans don't like little cars.
I hope to be lucky enough to always program on and for a workstation.
Smart phones and tablets are decent for consumption but their main limitation is screen real estate and efficient user input (which usually refers to typing). It really is a case by case basis (whats the product, who are your users, etc) and usually the answer is that you're going to want to be well represented across all typical client types.