Skip to main content

"Laptop" of the Future

Being an avid user of laptop computers and "smartphones", I have come to the conclusion that the technologies will soon merge.

A "smartphone" is a mobile phone with PDA capabilities. Smartphones have become so advanced that they perform many of the same functions as laptop computers. Phones that run the Windows Mobile operating system, for example, run Microsoft Outlook, Internet Explorer, connect to wi-fi hotspots, play music and video, and run many other applications.

The only things that separate smartphones from laptop computers are
  • Screen size
  • Storage capacity
  • Keyboard
I predict the laptop computer of the future will be a mobile phone to which you can attach a portable but external high-resolution monitor and full QWERTY keyboard.

Comments

Brandon said…
Hmm... Someone posted a link about how "product categories tend to diverge." Who was that :)

http://cauvin.blogspot.com/2005/07/convergence-article-by-al-ries.html

Personally, I think size keeps these products for merging. Maybe a new product will come out that lets you doc you smartphone into a large form factor when you have extra space... Who knows.
Roger L. Cauvin said…
Good catch, Brandon. But I think this case is an example of the distinction between convergence of technology versus convergence of categories.

http://cauvin.blogspot.com/2005/07/convergence-of-technology.html

A product category exists in the mind. Technologies can converge without the product categories converging. In other words, marketing this product as a combination laptop/phone will not be effective. Companies will have to choose either one (laptop), the other (phone), or create a new category.
Nils said…
This is something I've thought about a bit - but I wonder what you see/envision as the nature of the "external high resolution monitor" and full-size qwerty keyboard?

I mean, do you actually think those will arrive (and become successful in the converged world) with anything like their current form factors? If not, what kind of form factor do you imagine we'll be seeing?
Roger L. Cauvin said…
Nils, I think you raise a good point about keyboards and monitors taking a different, more portable, shape in the future. I urge readers to check out the entry on your blog for more details.

I do think, however, that part of the key to the obsolescence of the traditional laptop computer will be the ability to attach standard keyboards and monitors to phones, even if more portable versions of these peripherals begin to take hold.

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Use Case as a Black Box

Consider the following use case: Purchase Items Actor: Purchaser Precondition: Purchaser types at least thirty words per minute and has a web navigation efficiency rating of at least 40. Postcondition: For the average Purchaser acting at full efficiency, the number of seconds elapsed is no more than 30 + 20 * n, where n is the number of items purchased. The name of the use case represents a functional requirement. What does the product do, or enable the user to do? Purchase items. What are we to make of the preconditions and postconditions? What relationship do they have to the requirements for the product? Answer: the preconditions and postconditions are the nonfunctional requirements attached to the functional requirement . Another way of expressing the nonfunctional requirement would be as an attribute and associated constraint: Usability: For a Purchaser who types at least thirty words per minute and has a web navigation efficiency rating of at least 40, it shall take no

Henry Ford's "Faster Horse" Quote

You may have heard the ( apocryphal ) Henry Ford quote: If I'd asked customers what they wanted, they would have said "a faster horse". Over at the On Product Management blog , Saeed gives his take on this infamous quote. He "hates" it, and gives some compelling reasons. Saeed is spot on in his explanations. Personally, I think the quote is great, but it's a matter of interpretation. The valid point of the quote is not that it's a bad idea to facilitate a conversation with your market to better understand it. The valid points are: You must ask the right questions to get valuable answers. You must interpret the answers thoughtfully - often outside their direct meaning - to glean reliable information. Asking questions is not always the best way to "listen" to your market. (E.g., sometimes pure observational studies are more reliable.) Nonetheless, I find the quote is helpful to combat "armchair product management" in the