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!
Tue Jul 03, 02:41:00 PM 2007
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!
Wed Jul 04, 10:28:00 AM 2007
Post a Comment

Popular posts from this blog

What Product Managers Can Learn from the Apple iPod

The Story When Apple unveiled its iPod digital music player back in October 2001, I dismissed it as a  parity product . I already owned the Cowon iAUDIO CW100 MP3 player, loaded with my favorite tunes. There was Apple, generating great hype over the iPod as if it were a breakthrough product. The idea of a portable digital music player was nothing new. The first mass-produced MP3 players came out in 1998. In late 2001, the concept may have been new to a lot of Apple customers, but it wasn't new to me. I proudly showed my MP3 player to friends when they gushed about the iPod. Thus Apple's iPod was not an innovative product in and of itself. Years later, however, I realized the significance of ecosystem of which the iPod was a part. Apple had released iTunes (with technology purchased from  SoundJam MP ) and created the iTunes Store for finding and downloading music. Unlike Napster , it was a safe and legal way of distributing and acquiring music. The prior way of playing
2 comments
Read more

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
32 comments
Read more

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware
8 comments
Read more