HOME     SITEMAP     RSS     TWITTER     EMAIL    
Search:   

FollowSteph Follow Steph as he posts Blog Blazer Friday
 

Strike One. Strike Two. Strike Three. What You're Not Out?

iTouch

Recently Apple release version 2 of it’s wildly successful iPhone with great dismay. So many people flocked to the stores to buy this latest new offering that it killed their networked. This ended up causing a lot of phones to become “bricked” (aka as useful a phone as a brick). Strike 1. Well maybe not strike one, we’ll pretend they just forgot to bring their bat to the game.

Having quickly brought back their network from the dead within a day or so, people were able to activate their new iPhones (or upgrade their older iPhones to the latest software). All seemed well and rosy again.

Then within no time reports started to come out that the phones were continually crashing. That synching your phone could take hours, many hours. Daily reboots. And much worse. Basically the community came to conclusion that version 2.0.0 of the iPhone should really have been called version 2.0.0 beta (maybe even version 2.0.0 alpha depending on who you talk to).

Strike One!

Then release 2.0.1 came out. It was suppose to fix some bugs. Maybe it did, who really knows for sure. For me personally the phone was just as unstable. I think rather than 2.0.1 it should be called 2.0.0 alpha 2. In any case, at best it only seems to have resolved some superficial issues.

Strike Two!

Looks like Apple just released version 2.0.2 with even more issues. Apparently they fixed some bugs, but also introduced others. I haven’t yet upgraded myself, but if it’s anything like what’s described on this recent post on iPhone Atlas, I’m not going to either! To quote the post: “This problem is generally accompanied by another in which music and other media are erased from the iPhone.” You should see the fix to resolve this issue!

Strike Three!

What? Not out yet? Apparently not. They have enough pre-built goodwill to keep going. But for how long? No company has infinite goodwill. Eventually they’ll lose all their credibility. The “it just works” won’t apply anymore.

And it’s not like they haven’t had any time to fix these issues. It’s been what, a month? Maybe two? Yet all we seem to be getting are basic bug fixes that don’t resolve any real issues. Not only that but they seem to be causing more issues. It just works, I don’t think so.

If Apple doesn’t watch out, they’ll lose all their credibility and brand value before they know it!



 
Like this article?

No comments yet. Be the first.

Write a reply:





 
FollowSteph RSS
FOLLOWSTEPH'S
RSS FEED!


SOFTWARE AND BOOKS BY STEPHANE GRENIER:

LandlordMax Property Management Software

LandlordMax is the EASIEST
Property Management
Software available!
Try it for free!

Real Estate Pigeon

Real Estate Pigeon
The place to ask and answer
all your real estate questions

Blog Blazers: 40 Top Bloggers Share Their Secrets to Creating a High-Profile, High-Traffic, and High-Profit Blog!

Blog Blazers is a book that
features secrets from the
Top 40 Bloggers on the web

How to Generate Traffic to Your Website ebook

How to Generate Traffic to
Your Website
is an ebook for
to you achieve success


 

FollowSteph
More resources from Stephane Grenier:
PUBLICATIONS
For people who work on the web
Blog Blazers
How to Generate Traffic to Your Website
 
SOFTWARE
The EASIEST Property Management Software available!
LandlordMax


Copyright @2003-2013
LandlordMax Property Management Software

Disclaimer: This is a personal blog about my thoughts, experiences and ideas. The contents of this blog are for informational purposes only. No content should be construed as financial, business, personal, or any other type of advice. Commenters, advertisers and linked sites are entirely responsible for their own content and do not represent the views of myself. All decisions involve risks and results are not guaranteed. Always do your own research, due diligence, and consult your own professional advisors before making any decision. This blog (including myself) assumes no liability with regard to results based on use of information from this blog. If this blog contains any errors, misrepresentations, or omissions, please contact me or leave a comment to have the content corrected.