I decided to conduct an experiment in 2018 and embrace the coming age of the bots. Throughout the year, I culled songs from Spotify’s Discover Weekly1 recommendations, music heard in the wild (thanks Shazam), songs surfaced by Apple Music, and tracks played on local radio (esp. KUTX).
I say that I embraced the coming age of the bots because well over 80% of the ~1,500 - 2,000 songs I listened to (and tracked) during the year were purposefully based on algorithm-generated recommendations. Of these, I saved 228.2 I then filtered for only those songs released in 2018, reducing the count to a reasonably compact 45 (clocking in just under 3 hours of total play time). And in one final nod to letting the computers do the thinking, I sequenced the song order on “shuffle”. I’ve published the final playlist on Apple Music.
It should be noted that I was inspired to share these results by a friend of mine who regularly posts his favorite songs and albums of the year. Interestingly, though a couple of artists (CHVRCHES, Courtney Barnett) found their way on both of our 2018 lists, not a single song was duplicated.
As a point of comparison, I also installed Federico Viticci’s Siri Shortcut Apple Music Wrapped, which attempts to capture for Apple Music customers the spirit of Spotify’s year-end listening trends summary. The 25 songs that comprise my resulting "Wrapped (2018)" playlist are not limited by year of release, as the experiment above, but are selected solely based on play count. As Apple further embraces services, one can hope they will bake-in these kinds of features in the future.
1 Spotify serves up 30 songs a week to “discover” based on an algorithm which assesses your listening habits, saved songs, and, from what I have read, songs others on the network are sharing, saving, and what not.
2 90%+ of the down-selected songs originated with Discover Weekly.
Today, what entranced Joel Meyerowitz about the street is all but dead. “Nobody’s looking at each other. Everybody’s glued to their phones.” But street photography still exists? “It’s thriving but not in the way I used to do it. The best street photographers now show humans dwarfed by ad billboards. The street has lost its savour.”
Is it ethical to read the emails of the dead, or for digital platforms to take away a tool for mourning? Who is entitled to decide what the deceased person wanted to preserve of themselves? And how do social media platforms wield this responsibility?
The Economist weighs in (paywall) on the challenges (future) historians face with preserving our increasingly digitized/digitalized present and avoiding a "404 - Not Found" past.
Below is a sample of designs for this website from very early on. Back then, html was primitive and javascript was in its infancy compared to modern web standards and tools. That said, as has been suggested more eloquently elsewhere, much was accomplished in the face of these limitations. There was a real sense of possibility and experimentation resulting in a wide range of styles and layouts, which gradually became more generic and predictable as major template-based CMS platforms (e.g., Wordpress, Squarespace, etc.) grew in popularity.
With WWDC 2016 upon us and its expected focus on the much-anticipated third-party Siri API, I’d like to reflect on how Apple has been preparing native app developers for a world where the experience of a given application service or brand is multifaceted, continuous across platforms, extensible, and, ironically, as a consequence of increasing reach, also at risk of being fragmented, subsumed, and erased.
Last year while attending WWDC, I had the good fortune to participate in the inaugural Layers conference, which was introduced as a design-oriented complement to the generally developer-focused WWDC “main event” of the week. The conference size, the diversity of its events, the approachability of its speakers, the range of topics covered, and the engagement level of the audience all came together to make Layers a truly inspiring and memorable experience. One presentation from last year in particular has stuck with me as I’ve thought through the changes we are seeing in the way we interact with services and brands on our iPhones.
Neven Mrgan spoke about some of his favorite things, and, loosely, the sometimes unexpected goodness that comes from sharing what you love. Chuck Jones’ seminal Duck Amuckcartoon was one of the beloved things Mrgan shared (@ around 20:00), a rare treasure which I agree is both wildly entertaining and endures as required reading for anyone interested in the art and craft of animation, filmmaking, or storytelling and visual art in general. But what caught my attention that day was Mrgan’s off-handed comment about the sequence near the end of the cartoon where the frame literally begins to close in on poor Daffy, collapsing from all directions. He joked the image reminded him of his time designing responsive web applications.
The analogy was spot on and, as I thought about it more, seemed appropriate not only to web app design but equally reflective if perhaps in a more abstract way of the fundamental changes native mobile apps have witnessed in recent years, especially in light of Apple’s announcements that very week, which included: app “thinning” and targeting application assets for different devices, Siri Proactive and app deep linking, and multitasking and split-screen window management in both OS X and iOS. Through the lens of Duck Amuck, Apple’s announcements could be seen as the latest in a series of operating system enhancements (cf. iOS 8’s share sheets and extensions framework, notification center widgets) designed to deconstruct what it means to be — and what it means to experience — a modern, mobile (iOS) application.
Instagram “Peek” on iPhone 6S running iOS 9
The trend continued with the hardward-specific “peek and pop” feature enabled by 3D Touch announced later in the year as a feature exclusive to the iPhone 6S and 6S Plus. So it wasn’t surprising that many industry commentators began to question the long-term fate of native apps. And given recent investments in messaging and chat bots, major platform players, especially those who have been laggards in mobile, appear anxious to speed the demise of the standalone app (store), instead encouraging companies to deliver their services on their respective “aggregator apps” or “portals” as Ben Evans astutely describes them, such as Facebook Messenger, Microsoft Skype, Kik, Slack, and the most successful to date, WeChat. Even Amazon’s Echo requires a companion mobile app to manage third-party aggregated services through so-called “skills”.
In parallel, responsive web design emerged to address the proliferation of devices accessing the world wide web today, and effectively, with limitations, provide native app-like experience to web apps when accessed by mobile devices. Rather than developing and serving mobile-specific sites (remember WAP?) for mobile devices, the responsive web is built on the idea that a site should be fluid in nature and able to gracefully adapt its content and services to accommodate the way in which that content is accessed and used.
As with responsive web design, native apps will continue to evolve with greater adaptability based on device type and screen size (including no screen at all) and, by extension, their respective interaction models. Traditional graphical UIs will co-exist with conversational voice and text options. The challenge will be how best to maintain context across these interaction models and move users as seamlessly as possible between them when necessary. And users, for their part, should prove equally adaptable as long as expectations are clearly communicated, transitions are consistent and predictable, and transactions are fast, accurate, and add value.
Netscape Navigator was a browser created by a group led by a twenty-four-year-old named Marc Andreessen, who was described in Newsweek as “the über-super-wunder whiz kid of cyberspace.” The company’s I.P.O., on August 9, 1995, was a huge success. Five million shares went on sale on Nasdaq, at twenty-eight dollars a share; they closed the day at $58.25. The Times called it “the best opening day for a stock in Wall Street history for an issue of its size.
A little more than two weeks later, Microsoft released Windows 95, backed by what was reported to be a three-hundred-million-dollar marketing campaign, along with its own browser, Internet Explorer 1.0, and the browser wars were on. Netscape, of course, was quickly and easily outmuscled by Microsoft. In 1998, Netscape was acquired by AOL, and it faded into insignificance.
In the midst of Netscape's I.P.O, which W. Joseph Campbell contends woke the world up to the Internet, I was happily ensconced on campus at The University of Chicago, spending my time reading, attending screenings and workshops, and, on occasion, shivering in the computer lab (curiously reachable only through Harper Library if memory serves) exploring the nascent world wide web, but more likely checking email, the most used "app" by far at the time. Thinking back on the "browser wars," I don't agree that Netscape faded into insignificance so quickly, though I do remember acknowledging their impossible odds. That said, I recall well into 2003 still contending with the vagaries of Netscape and IE while designing and coding (i.e. grappling with javascript) websites. Though, by that point, the seeds of change certainly had been planted. On January 7, 2003, Steve Jobs announced Safari (Apple's fork of KHTML), helping to set the stage for improved cross-browser standardization which is still largely the trend today.
On the eve of Apple's "Spring Forward" event, I thought it would be worthwhile to revisit Robert Cringely's prediction for 2015 as the year "when nothing happened" and, particularly, his take on the significance and reception of the Apple Watch:
The Apple Watch is Cupertino grabbing mindshare and early adopter wallets, nothing else.
Even those who are typically bullish on Apple seem to be restraining their enthusiasm and predictions of massive success for the Apple Watch. All except the stock market itself, with AAPL up over 14% YTD. The naysayers are hedging a bit too. If you widen the view on Cringely's comment, he isn't exactly dismissing the Apple Watch to the dustbin of history, instead pointing to 2016 as the year to watch.
I am hopeful he's wrong. I personally find even the most fanciful aspects of the Apple Watch experience intriguing, at least as they have been described up to this point, and applaud Apple for the tact they have taken as they methodically enter the nascent wearables market. I expect many recent enhancements to the iOS experience like Touch ID and the application extensions framework will be all the more relevant once the Watch is in the wild.
Critically, though, unlike the release of the iPhone in 2007, there isn't an obvious problem begging to be simplified and redefined. We aren't dissatisfied with our time pieces in the same way that so-called smartphones left much to be desired eight years ago. The Apple Watch is a much harder sell because of this; it is trying to extend, and ideally in many situations, replace the iPhone experience itself (which obviously is a bit thorny for Apple, though they have been famously comfortable with product cannibalization before) rather than displace something already taking up space on everyone's wrist.
Will the convenience and attempt at a kind of naturalness by situating tech on your arm rather than in your pocket, be as obvious when we look back on 2015 as portable touch screens appear now, when we reflect on the dark ages of 2006?
It might just come down to the distillation Apple is promising with the interface elements pictured in the photo above: the new pressure-sensitive screen, the much-fetishized Digital Crown, and, simply, the Button. While much has been written recently about the attention Apple is paying to the fashion-related aspects of the Apple Watch (e.g., luxury options, extensive customization compared to previous products), perhaps the obviousness and must-haveness of the device will emerge in its everyday use, where routine things will get done faster and information will be transmitted with less friction and without the encumbrances of even the most modern of smartphone interactions. And that is to say nothing of the integration of Apple's Siri personal assistant and speech recognition tech, which Tim Cook boasts using "all the time." Will Apple Watch be Siri's debutante coming-of-age?
One thing is certain: as my father-in-law reminded me tonight, given Apple's recent history, it would be foolhardy to categorically dismiss anything they aspire to do with the Apple Watch. For perhaps the first time in the company's history, it seems Apple has earned the benefit of the doubt.
We are moving the company’s downtown Chicago offices to a larger space closer to Union Station; both good things. We invited Eastlake Studio to help make the new location awesome and I recently visited their offices in the Chicago Tribune Tower. I’ve walked and driven past the 1920s landmark countless times before but never had the opportunity to go inside.
The above photo is the view from Eastlake's offices looking west-southwest. Not bad, right? How wonderful to have such inspiration just outside your window every day.
A couple of technical notes
1) This capture was taken very quickly with an iPhone 5S. A snapshot. Nonetheless, I am thoroughly impressed with the detail and resolution the 5S pulls off — from street-level sidewalks to the distant top floors of the Willis Tower to the weathered stonework of the Wrigley Building and the shadow detail of IBM Plaza (now AMA Plaza). Perhaps I’ve just grown accustomed to digital aesthetics, and a future print likely will be the true test, but I'm not sure I would have been able to produce anything like this with my 35mm gear, certainly not without preparation.
2) If you peek at the metadata, you will find that I used Adobe Lightroom 5 to post-process the image (monochrome conversion, lens correction, and perspective adjustment). As a long-time Apple Aperture user and evangelist, this marks my first tentative steps toward an all-Adobe workflow. It’s no small decision and part of me is holding out hope that the mere thought of ditching Aperture will have some cosmic effect resulting in the announcement and release of Aperture 4.0 at WWDC next month, delivering all the goodness of Lightroom and more. But I am doubtful. Despite my deep (some would say non-rational) reservations about Adobe generally, for anyone looking to get more serious about photography today, I would be hard-pressed to recommend Aperture. I wish things were different.
Since one cannot easily move one's work and time invested in one tool to the other, perhaps the best choice is to rely on them as little as possible. There are likely alternatives out there which I am not aware of, but it seems to me that photo file management and lightweight image post-processing is an area begging for innovation, including cross-platform support, long-term scalable network storage, and auto-curation beyond map views, face recognition, and “on this day” flashbacks (as provided by the now-defunct Everpix).
The most impressive thing about social media site SoundCloud is its signature feature: to graphically represent in spatial terms what is usually experienced non-graphically in time, the waveform of an uploaded audio clip. By laying out the amplitude of the audio recording, SoundCloud emphasizes duration of experience, pointing to its peaks and valleys, and, most important for my purposes here, allows for the insertion of time-coded feedback.
As consumption of web-based media has evolved over the past decade+, we’ve grown accustomed to eating whole this or that bit and then, when offered the opportunity, provide feedback at the end and participate in a comment thread. Granted, one can excerpt the relevant content (or time stamp in the case of audio or video) for which the comment is addressed but this localization is still displaced temporally. With SoundCloud, we are given the opportunity to attach one’s commentary to a specific moment within the audio stream so that it can be part of the initial experience, as one is “reading” the audio stream. The site provides a visual representation of the referenced clip time stamp, a feature called “timed comments”. It seems pretty simple and obvious in hindsight but I haven’t encountered a precedent.
One risk of this approach is fragmentation, a letting go of the way in which a comment thread as it exists today coheres disparate voices into a kind of dialogue. Perhaps localizing commentary also runs the risk of losing context, of misinterpreting an argument by pressing too hard at the sentence or word level. It also isn’t immediately obvious how best to encapsulate visually a myriad of localized comments within the current blogging paradigm. A blog post could easily be overwhelmed with side notes demanding equal attention. Perhaps for this reason especially, we’ve not yet seen its adoption, SoundCloud notwithstanding. Still, I find the prospect compelling, a means to engage web writing with greater specificity and intimacy.
First, let me say, I hope that Steve Jobs’s no doubt difficult decision to resign as CEO of Apple allows him to focus his energy and strength on a speedy recovery from illness and return to good health. That is job number one. Yesterday’s announcement, delivered by personal letter to the Apple Board and Apple community at large, has generated considerable reaction in the tech and media communities, for good reason I think. Even though we’ve all known about Jobs’s health issues, I think we’ve held out hope that it wouldn’t have to come to this, that it was something that could be willed and managed into permanent remission, part-time. Acknowledging this is not the case, that Steve is human, we all are, is difficult but also liberating.
Much of the talk has circulated around the fate of Apple. After the initial flutter, I think most folks are concluding that the company has a “deep bench” and with Tim Cook at the helm in particular, there is little risk of execution flagging in the wake of Jobs’s transition to Chairman. Cook appears to be cut from the same cloth when it comes to restraint, quality, and attention to detail. We will have to wait and see how cultivated a sense of whimsy and invention he has, the “hacker” pedigree which has also been an important strand of Apple’s DNA under Jobs.
Apple Macintosh (1984)
I basically grew up with Apple gear: Apple II in high school, original Mac 128K in college (nicknamed the MacMelt due to a faulty power supply), my first laptop the Powerbook 140, a Performa(!) desktop during my (lean) days in graduate school, and of course numerous devices over the incredible run during the past decade after a brief Apple-free stint in the late 90s. These things have helped shape my thinking, have helped me express who I am. And for most of that history, Jobs has been a significant part of the buy-in, especially when Macs were dismissed as toys at best. There has been a trust in his vision, his passion, his origins, and a reassurance in knowing that he is dreaming in California of the next thing and sweating the details too. I can try to convince myself that nothing changes much with this announcement, and maybe that is largely true in the immediate day-to-day, but, naturally, I will also have to adjust my attitude about Apple. It isn’t business as usual on a gut level.
That’s not necessarily a bad thing. There is no question that Apple is in the best position it has ever been, and it is a testament to Jobs on down the line that they’ve created a nice cushion to weather this transition. And it just might be a wonderful opportunity, a time to double down on the team that Jobs has assembled and now trusts with his baby. Those same reasons that have kept me loyal, the memories of wonder and amazement when first using Apple computers, have also framed my expectations to some extent. Those are big shoes to fill and a tremendous responsibility, no doubt, but what a prize Cook has been handed! I welcome getting to know him better and seeing where he and the rest of the management team take the company next. And in the meantime, get well Steve and keep us posted.
Hello world! I’ve decided to return joecarey.com to its roots as a personal website, a place to share and promote my photography, recommend articles and other items of interest, and sketch ideas.
It’s been an interesting journey since I shuttered the site three years ago. I tried various hosted, sometimes social, venues (e.g., Facebook notes, MobileMe, Flickr, Posterous, and, most recently, Tumblr) to publish my photos and infrequent notes. In each case, over time these services fell a bit short of my particular requirements, which is not to say they all don’t excel at what they do for their target audience(s). So, I’ve turned to a relative newcomer, Squarespace, in hopes that their approach will strike the right balance between convenience and flexibility. So far, I’ve been impressed with the features and speed of the platform, the company’s close attention to detail, and the obvious thought that has gone into the design of their UI/dashboard. All good stuff.
In migrating the blog archive from previous incarnations (for a good stretch, managed using Movable Type), I’ve spent some time tidying things up (not least, link rot), excising a few entries, and adding or updating supporting material where it seemed useful. The availability of new software tools and APIs, the mass of content available online, and the pervasiveness of the web now in the guise of social media and mobile devices have changed the landscape of options available to experiment with here. Happy to be back.
People will always find a way to annotate electronically," said G. Thomas Tanselle, a former vice president of the John Simon Guggenheim Memorial Foundation and an adjunct professor of English at Columbia University. "But there is the question of how it is going to be preserved. And that is a problem now facing collections libraries.
Hoping for good things from the "Talk to Me" MOMA exhibit opening this summer on the seemingly impossible-to-curate topic: "Communication between people and objects."
It’s not fair — all the United bashing going on around here — but the recent post titled “Don’t Make Me Scream” over at SvN struck a chord, especially since designing and writing speech applications for large enterprises like United is what we do at Versay.
I couldn’t agree more with Matt’s rant. Many speech IVR applications out there are terrible, not just United. Too often I find myself walking down a street on my mobile phone trying to get information, only to be greeted by a cheerful voice asking way too many questions and getting seriously confused by the sounds of trucks and cars and other random background noise. Knowing how these systems are designed makes me an even more demanding user. I know they can do better and it is frustrating that best practices are so infrequently used.
A particular pet peeve is the situation where I navigate through an application, patiently providing things like account information, reservation information, and the like. . . and then when I am transferred to an agent. . . yep. . . I am asked the same questions all over again. Unacceptable. As a client of ours once remarked (when describing our shared golden rule about the hand-off between automated and live customer service): “If you ask it, pass it”. Granted it’s not always the easiest feature to implement, but for my money it is essential.
So, Matt, I hear you loud and clear and I can assure you that we are working with our clients every day to improve their UIs and to re-think high-quality, yet cost-effective customer service.
Update (4/11/07): Two Tellme executives head for Y!.
It’s been a Google kind of week here. Google Labs has just released their much-anticipated and long-speculated speech-enabled free 411 service. This comes on the heels of Tellme’s recent Business Search beta, offered behind their 800-555-TELL (8355) service.Some early and incomplete observations:
Tellme’s Business Search is very. . . well. . . Tellme, including the usual navigational audio clicks and swooshes to mark list items and returning to the beginning, as well as transitional music and service announcements. These things when not used judiciously tend to slow down the call unnecessarily and also betray Tellme’s entertainment industry pedigree.
Google’s service has tell-tale old school Nuance VUI elements for things like error handling, contextual help, and offering options like “details” just before the call is transferred.
Unlike Tellme, the Google app appears to be music-free and lacks earcons, although they do play a humorous “thinking” sound no doubt mocking the typical cue for system processing. This is in keeping with Google’s overall stripped down approach to interface design.
Tellme entertains and then optionally texts you a listing but does not connect the call (yet). Google connects you (and optionally texts if that is preferred). Which do you think is the better experience?
Google has an interesting back-off strategy and allows callers to enter requests using their dial pad. This is a nice feature for noisy environments or simply when speech recognition is having a tough go of it.
Google’s text-to-speech sounds signficantly better to these ears, although this improvement creates another interesting challenge. The synthesized speech at times is almost too close but not close enough to recorded human speech, evoking an uncanny valley experience. It’s creepy at times.
Overall, I’d say the services do a fairly good job of locating what you want as long as you steer clear of uncommon requests. For example, Tellme sent me to a post office in response to my “postcards” request (not really what I wanted) while Google was sure I needed to talk to the coast guard. (To its credit, Google kinda got it right the second time around, recognizing the request properly but then offering to connect me to the Pleasure Chest in Chicago, citing it as a. . . um, “related listing.”)I was much more successful asking for “stationary” on 800-GOOG-411. I was quickly connected with The Paper Source on Armitage Avenue. I’m sorry to report this request was equally perplexing for Tellme though. Granted, I am being a bit unfair, and by no means am I arguing that these systems don’t work well. In most cases, things went smoothly. But with these limit cases, it was interesting to see how each service reacted. It’s one of the most important aspects of the work we do at Versay — designing applications to get callers back on track when things go wrong. These factors are amplified dramatically when you are working with the large number of options required by automated directory assistance.As Om Malik points out, Google’s entry into this space, while no great surprise (do I sense a bit of a yawn, Om?), certainly spells trouble for pure-play providers like 800-FREE-411 (373-3411) and 800-411-SAVE (411-7283). And no doubt Yahoo is just around the corner. On the other hand, it is a definitive vote of confidence in the viability of large-scale speech application deployments and one hopes a sign of further innovation to come.
Last year, I posted about the “next Google” phenomenon sweeping the nation, specifically comparisons between 37signals and the search giant. This year, the landscape hasn’t changed all that much. Companies are still hotly competing to get a piece of the search market, start-ups and established technology firms (e.g., Microsoft and Yahoo) alike.
37signals are still going strong and have released their CRM-lite application, newly named Highrise. I personally think it is their best release yet and could potentially absorb/cannibalize some of their other offerings. While I get why they prefer to keep project management separate from contact management, there is enough overlap between services so that some core data elements should be shared. Just as Apple engineers have resisted the all-in-one approach of Microsoft Outlook, instead offering siloed apps like Address Book, Mail and iCal, they nonetheless enable sharing of elements common between these applications. It’s proven to be a successful strategy in balancing usability and functionality.
Interestingly, if one were to ignore the numerous and obvious differences between the two companies, it could be argued that Google and 37signals have actually moved closer to one another in terms of service offering over the past year. With the Google Apps launch, they too want to provide the tools to help you manage your business in a hosted, web-based model. And why not? Google already provides services for email (Gmail), calendaring (Google Calendar), and instant messaging and VoIP (Google Talk) not to mention “Microsoft Office killers” Docs & Spreadsheets and Page Creator. The Google Apps offering rolls these services up into a complete package in three flavors: small business, enterprise and education. And from a technical perspective, most importantly both companies have embraced APIs, enabling third-parties to deliver “mash-ups” of theirs and other services. This is almost a given in today’s 2.0 world and arguably one of the key drivers behind the success of hosted services.
Google’s move signals a couple of things.
First, hosted application services for business and not just the consumer space have arrived in a very big way and definitely threaten Microsoft’s desktop dominance. If nothing else, both the live.com initiative and recent Tellme acquisition confirm this. This is not to say that hurdles don’t still exist. While bandwidth and availability concerns have largely been overcome by large capital investments in infrastructure, other factors such as data portability, privacy policies, and security still remain stubborn obstacles for hosted solutions. With Google in particular, given its transparent goal and not-so-transparent methods to index the world, there is still a strong distrust of the company’s motivations and a nagging fear around the vulnerability of hosted (implicitly shared) corporate data.
Second, as Miquel Helft points out in his January 1st article for The New York Times, in its effort to go after communication and collaboration, be it for small to medium-sized businesses or large enterprises, Google risks losing ground in the search arena. No doubt just as AltaVista and Webcrawler were once default, now abandoned search options, so too Google’s reign is constantly threatened by innovation just a click and a bookmark away. That is, of course, unless the search business has changed so dramatically in the past seven years so that new barriers to entry will thwart a dramatic shift in market share.
Given the current climate, one wonders how steep of a climb a start-up like Powerset (one of the latest entrants in the “next Google” sweepstakes) will have, or if search is in fact the fastest way to claim the title for keeps, as last year’s front-runner, Wikipedia, seems to believe.
After the initial wow factor of Apple’s announcement of Boot Camp and support for Windows on their new Intel-based hardware, I’m now a little less enamored with the idea. The two things that I haven’t missed about life with Windows XP is the less than stellar plug-and-play experience with peripherals and the inevitable sluggishness and disk churn caused by Windows caching and file system fragmentation. I went through two hard drives on my previous WinTel laptop and I’m convinced (evidence be damned) it’s in part due to the stress the OS puts on the hard drive. Now, I know with Boot Camp everything is neatly sandboxed and partitioned, but I can’t help thinking how will Windows behave with the physical hardware? Will drives die faster? And, back to plug-and-play, will I have to cross my fingers every time I plug in a USB thingamajig?
Some folks I’ve talked to think that when Windows users get their hands on a Mac, their introduction to Mac OS X will result in a ready-made Switch campaign. Maybe. Maybe not. But I wonder if rather than a rising tide lifting all boats to meet the excellence of OS X, we may instead see Mac hardware flake out just as badly as the Dells and HPs out there. I mean, let’s face it, we aren’t talking about the most rugged platform (my original Mac 128K will forever be known as the MacMelt, thanks to a burned out power supply).
The question boils down to: what kind of company does Apple want to be? Hardware? Software? Entertainment? Platform? Applications? Lifestyle? And how strategic or reactionary is the Boot Camp move? Is it a clever way to accelerate migration from G4/G5? A way to quiet the gamers? And what is the fate of Microsoft software for OS X like Office and Remote Desktop? Time will tell.
If there is any doubt that 37signals, purveyors of fine application services such as Basecamp and Backpack, has jumped the shark, Information Week has sealed the deal with a recent fluff piece headline: “Is 37signals the new Google?”
Don’t get me wrong — I am a long-standing supporter of the 37signals crew since we first approached them to design a site back in 1999, and a true believer when it comes to their unwavering dedication to clarity in design, and “less is more” approach to business management. I also can’t help but be impressed with their evolution over the years, growing from a usability and user experience-oriented design shop to a blog-powered, seminar-driven marketing machine (in the best sense of the word). And, while I don’t “live” in their software as some of their biggest fans do, I would agree that they are among a handful of companies designing very good software today. I eagerly await their entry into the hosted CRM market. SalesForce could use a serious wake-up call.
But the next Google? Back to the headline.
Jason Fried, master of ceremonies at 37signals, shared news of the article with his Signal v Noise blog readers, generating a typically active discussion (41 comments as of this post).
Which got me thinking: what other companies have been suggested as the next big thing in the age of Google?
A Google search for the phrase “the next Google” produces 90,300 results (though Google cuts you off at 440 claiming the rest are similar). Among the top hits, you will find:
It will be interesting to see where these companies, Google included, rank a year from now, 5 years from now and beyond. I wish Jason and the 37signals team the best.
Fall 2005 was a blur. So much so that I decided to take the blog portion of the site down. Too much going on. But now, with a new year ahead, and in response to several requests, I’ve brought the blog back online and couldn’t resist the opportunity to restructure content a bit.
As I’ve noted before, I use Movable Type to manage content. I’m a big fan and have convinced others to use it for more than just blogging. Even with WordPress growing in popularity, I find MT’s balance of structure and flexibility to be a good fit. For example, I use a single MT weblog to manage different types of content, from blog entries like this to the various static photo series to my photoblog. It’s probably not the most elegant way to go about things, but by customizing MT’s standard templates combined with a handful of plug-ins, the site dynamically responds to different media types and the structures they require, in both human and machine-readable formats (e.g, the feed for this blog).
So it was with considerable curiosity and excitement that I found the Structured Blogging site by way of Paul Kedrosky via Dick Hardt. I have to agree with Mr. Hardt — it just makes sense for this type of innovation, especially the ability to produce microcontent-specific feeds. By baking in much of the customization I’ve hand-rolled, MT will be that much more powerful out of the box.
In his recent Slate article, “Self-Storage Nation”, one-time Baffler regular, Tom Vanderbilt, describes America’s healthy appetite for space to store stuff.
As Vanderbilt hints, the recent growth in self-storage is evidence of a larger trend that stretches well beyond those ubiquitous sheds one finds scattered along the outskirts of town. Companies like Container Store, publications like Real Simple and books like David Allen’s Getting Things Done all seek to answer the growing demand to organize, simplify, and store the things that make up this modern life.
And it doesn’t just end with thing things. The same could be said online: Google’s Gmail offers 2GBs of free storage (easily hacked to store and serve files rather than email) and various services like Xdrive and sephoneSAFE offer the safe and convenient storage of one’s growing digital media files (e.g., .mp3, .flac, .jpg, .raw). Even the software I use for this website, Movable Type, can be thought of as a content management tool, a means to produce, organize and store stuff.
In most cases, this content is saved on hard drives in web hosting facilities that we will never see, never visit, never really give more than a passing thought. In fact, these places tend to resemble those impersonal sheds on the edge of town. Is it just a matter of time before Public Storage goes digital?
