Described by many as a "cluster", Apple's rollout of MobileMe may have been one of the most public IT disasters ever staged by homo sapiens. What Apple seems NOT to know about internet services is a lot.
In response to this very public humiliation, Eddy Cue, Apple's VP of iTunes, is now Apple's VP of Internet Services — reporting directly to Steve Jobs, CEO. I think this is a brilliant move, and here's why:
iTunes is a brilliant, proprietary web browser that is streamlined to perform a discreet set of tasks. That's what the MM apps should be. Architecturally streamlined.
Hopefully, Eddy boy will get the team to see things from a web services point of view. Instead of trying to be the best web app on the planet, MM should just try and be the best mail app, cal app, etc. — ignoring the fact that it's on the web.
My guess is that the front end appearance of the MM apps won't change all that much; but, the back end will change dramatically to handle and balance the load better, and serve up app modules into browser memory more efficiently in the re-coded front end. Non-web-browser thinking is definitely required here.
Databases holding the raw data of emails and calendar events need to be clustered with the best technology money can buy; not the cheapest. There's a reason that Squarespace is kicking so much butt with its hosted web services: they have the best load balancing, most optimized database clustering, and fastest connection to the internet trunk available.
A complex UI with drag and drop — as well as very demanding record and list views — needs to work hand-in-glove with its back end architecture. This level of integration and cooperation is a work of art, not computer science — and certainly not mere information systems work.
If Apple had consulted me on this, I would have suggested using an iTunes type of app and back end for MobileMe, rather than an open source web app framework on a general purpose web browser with an obviously lackluster back end. Maybe Eddy will feel the same after a couple weeks.
Comments [0]
Read how Guy Kawasaki built a Web app on the cheap.
Comments [0]
There's a though-provoking post in the Signal vs Noise blog by 37signals that John Gruber of Daring Fireball pointed out today. Here's a quote:
Click the image above to read the whole article on SVN and discover what makes a feature easy or hard to implement before you send your next request for a wouldn't-it-be-great-if feature to your team, your contractor, or yourself.
I would further recommend John Gruber's article on Copy and Paste on the iPhone, which really points out the non-trivial aspects of implementing a seemingly trivial feature on not just an application but an application platform (like the iPhone).
Comments [0]
Simple-to-complex examples of writing internet applications. Part 1 of 5 parts.
Comments [0]
Simple-to-complex examples of writing internet applications. Part 2 of 5 parts.
Comments [0]
Simple-to-complex examples of writing internet applications. Part 3 of 5 parts.
Comments [0]
Simple-to-complex examples of writing internet applications. Part 4 of 5 parts.
Comments [0]
Simple-to-complex examples of writing internet applications. Part 5 of 5 parts.
Comments [0]
As a business-to-business marketing platform, Twitter has legs. Some 56% of Twitter users say they use the online social communication site for business-related purposes, according to Rodney Rumford, a social-media guru and CEO at Gravitational Media. This stat, based on a survey of 700 Twitter users, suggests the service's business value, alongside its emerging utility for consumer marketing.
Click the link above for entire story.
Comments [0]
Comments [1]