Skip to main content

iPhone: Distinctive and Inviting

My friend Tamara got an iPhone over the weekend, and I got a chance to play with it Sunday. After watching her use it, listening to her comments, and trying it for myself, I concluded that the iPhone is distinctive and inviting.

The iPhone is distinctive in the sense that I have never seen another phone that simultaneously is sleek, has a large and bright screen, and has a fingerable touch screen. My 8525 has a fairly large screen and a stylus touch screen, and it is more powerful, but it is by no means sleek. It looks clunky in comparison to an iPhone.

The iPhone is inviting in the sense that, while not necessarily easier to use than many other phones, the phone's user interface is innovative and stylish. You want to hold the phone and use it if just because it looks so "neat".

That said, aside from its distinctive and inviting look, I see little reason to buy an iPhone. And it still remains to be seen whether the iPhone will be a success in the long run.

Comments

Mauricio said…
Hi Roger, I'm a Sr Executive recruiter and would love to talk to you about professional opportunities.

Feel free to contact me at mauriciop@avature.net to hear more.

Thanks!
free2choose said…
Hi Roger

I'm impressed that you actually shorted Apple stock in January considering the hype about the iPhone's success and the best part is you made money.

Looking at Apple's price today, I am thinking of shorting Apple for one main reason, the glass touch screen cracks too easily when dropped and given that phones tend to end up in all sorts of unexpected places, people are going to find that they bought a $600 test tube which needs to be handled with too much care.
Reports of cracked units being replaced in the 1st week for free will help to minimise negative publicity for now but what if it results in a massive recall? That could spell disaster till Apple finds a more durable screen and we could make a killing!!

I can't believe that Steve Jobs would actually make the IPhone screen with glass when even my spectacles are already made of high quality plastics!

Let me know as I intend to buy some puts at the current price!

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