Posts in Linked

Apple Cyclicality

Benedict Evans:

For the first two cycles Apple launched the new iPad in the June quarter and sales then rose in the September quarter (back to school?) and again in the Christmas quarter (presents) before falling in March (old product, new one coming). But then in 2012, iPad Mini rumours led to sales falling in September and then Apple launched the Mini and a 4th gen model in the December quarter. So sales shot up in the December quarter, held up well in March (newer product plus Chinese new year) and then slipped this quarter as it’s now a nine month old product.

Some solid analysis of yesterday’s Q3 results. The first chart really shows the seasonality of Apple products, and the inevitable decline of the iPod.

Permalink

Patrick Welker’s AppleScript and Keyboard Maestro Workflows for Lists

This is an amazing collection of workflows and tips by Patrick Welker, who explains how he automates list creation and management using AppleScript and Keyboard Maestro. The post also contains a modification of my recent Mail workflow to automate senders and signatures.

The hidden gem in the article, however, is the following sentence:

Since I’m deeply in love with Keyboard Maestro and want to preserve the just fallen in love kind of feeling in our relationship for as long as possible, I created a one-action macro to trigger the TextExpander snippet

The things you do for the apps you love.

Permalink

Google’s Document On Data Compression In Chrome For iOS

Last week, I wondered whether Google’s new data compression feature for Chrome for iOS was partially motivated by the inability to use the Nitro engine to speed up page load times. Today, I have stumbled upon the technical document that details how the data-saving process actually works – in short, it uses Google’s proxy to optimize web traffic sent by Chrome.

The proxy server receives the request initiated on the mobile device, initiates a request for the required resource on your behalf, and then optimizes each asset before delivering it back to the client. The content optimization is performed by our open-source PageSpeed libraries, which are specifically tuned for the Chrome Mobile browser. The rendering of the page, and all JavaScript execution, is performed by the client’s browser.

Of note, the transcoding of images from JPEG and PNG to WebP:

Over 60% of the transferred bytes, for an average page, are images. Hence, the proxy takes great care to optimize and transcode all images to the WebP format, which requires fewer bytes than other popular formats, such as JPEG and PNG. The proxy supports the new WebP lossless format for certain images, and also optimizes the perceptual quality of each image based on device screen resolution and pixel density of your device.

I’ve never been a fan of speed optimization through proxies personally, but I’m curious to try out Google’s implementation. The feature is still rolling out for Chrome users on iOS.

Permalink

‘How strange is Apple’s iMessage? The strangest.’

Craig Mod has a few suggestions that would go a long way towards improving iMessage. He talks about conflicting IDs, unsynced histories (and someone else had to make an app to fix how terrible searching history is on the Mac), and the lack of proper profiles for the people you’re conversing with.

The biggest problem I have with iMessage is that it’s capable of but really poor at handling group conversations. Our issues revolved around the “Send and Receive” settings. For a group chat to really work, everyone has to be sending from the same address. More often than not, this was different between a Mac and iOS devices. If someone in the group was sending a message on their iPhone, the default was likely a phone number. If someone in the group was sending a message on their Mac, the default was probably an email address. Linking helps, but keeping track of all these settings is difficult. If one person in the group was sending from a different address, it would cause a new conversation to appear in iMessage (thus “splitting the thread”) for the receivers. For the sender, everything would appear to be the same. With a big group of people this became a daily annoyance because it became difficult to follow conversations when different instances or pieces of it showed up in different places. It’s a hard problem to describe, especially when receivers can opt to receive messages at multiple email addresses (and if the same person you’re conversing with decides to send you something to an alternative address, I believe the message should show up in the same conversation). The reality is that the settings are kind of a mess and talking about this stuff caused a lot of frustration and we eventually gave up.

And we won’t even get into the problems that the iMessage for Mac app has. But that was a mess for a whole different reason, the main problem being that it would lock up our Macs when they awoke from sleep as hundreds of messages were downloaded. This is why our team fled to Google Hangouts once those apps became available on iOS (more on that in a minute).

iMessage is fine for its intended use, as an SMS replacement for talking to friends or family one-on-one, but people are treating it as the next Aol. instant messenger. And can you blame people? Our expectations are measured by how fast iMessage is at sending messages. Today’s virtual keyboards allow us to rapid fire messages and hold conversations a lot longer than our T9 phones did years ago. The days of traditional slow texting are over.

Google Hangouts has its own problems. The iOS apps in particular aren’t terrible aesthetically, but they slow down and I get frustrated waiting for messages to be sent and received a lot. I’m mostly happy with the Chrome extension, except when I play video in the background and the app gets bogged down because of something intensive happening in the browser. The good thing is that we haven’t had a problem following conversations and Google’s history (especially for images) is fantastic. The bad news is that it’s the opposite of iMessage: Hangouts fixes the history and contact stuff, but isn’t very good with the sending and receiving part on mobile. It has a desktop app (Chrome extension) that works but mobile apps that struggle. Ugh!

Permalink

The Menu Bar, Episode 015

The peerless Federico Viticci visits the bar to chat naming your band/blog, the allure of Apple, Microsoft’s thick cake of middle-managers, the lovechild of Automator & Sublime Text, and making things that don’t suck.

I was invited on one of my favorite podcasts and we had a great discussion about Apple’s culture, the topics we pick for MacStories, and more. We also talked about my favorite upcoming app, Editorial.

Listen to the episode here.

Permalink

Apple Announces 1 Billion Podcast Subscriptions

Apple has today announced that they reached 1 billion podcast subscriptions in iTunes:

From comedy to hard news to sports to innovative educational content and so much more, podcasting has transformed the global media landscape. Podcasts on iTunes launched in the summer of 2005 and since then, we’ve seen countless episodes downloaded and streamed. But the heart of podcasting is finding your favorite voices in this exciting field and subscribing to the best ones. To celebrate 1 billion podcast subscriptions, we’re highlighting some of the most popular podcasts of all times, as well as a collection of captivating new shows.

Apple is celebrating the milestone with a custom iTunes page that features podcasts under Classics, What’s Hot, and New & Noteworthy. The Classics include This Week in Tech, This American Life, and Stuff You Should Know, among others.

Apple also gave additional numbers to Macworld, providing more insight into available episodes and podcast subscriptions.

Permalink

Bugshot 1.1

In my review of Bugshot 1.0, I mentioned the app’s poor scrolling on iOS 6 devices and lack of Open In menu to send annotated images to other apps.

Version 1.1 is out today on the App Store, and it brings performance improvements, Open In support, and a Blur tool to pixelate sensitive information. I didn’t think about a Blur tool when I first covered the app, but it is indeed a great addition to Bugshot (with a cool implementation).

Bugshot is $0.99 on the App Store.

Permalink

Comparing T-Mobile’s, AT&T’s, and Verizon’s Early Upgrade Plans

Dante D’Orazio of The Verge compares the Jump, Next, and Edge plans across the United States’ three biggest carriers. The costs of these plans are broken down into tidy charts that explain what’s happening when you opt into these plans.

T-Mobile’s made a lot of news lately thanks to their outspoken CEO and marketing campaigns around becoming the “un-carrier.” T-Mobile’s greatest strength is that they have the most transparent plans in the industry and flexible options for those who bring their own phones to the carrier. Last week T-Mobile announced Jump, a plan that’s supposed to help people upgrade to a new phone earlier. AT&T and Verizon followed with Next and Edge, but their plans aren’t really that good of a deal. Dante has a couple breakdowns for those who want to upgrade every year and every six months. T-Mobile has the most affordable plans, but in the end none of them are that great.

Ultimately, most everyone is better served by sticking with their traditional cell phone plan and buying a phone at full cost when you can’t take that old smartphone any longer. It’s best, then, to think of these “upgrade plans” as extended payment plans that take advantage of customers who want the newest phones and want to pay little up-front by charging them massive fees as the months roll by. No deal.

I don’t think these plans are necessarily geniune attempts to help customers who want to upgrade early, but they do at least ease the pain of upgrading. Maybe people might find it easier to break up the cost of their next phone into chunks rather than paying for an expensive phone outright. Personally I’d rather just budget and buy the phone if I really wanted to do this, selling the old one afterwards, even though it’d be a bit of a hassle.

And these plans definitely make more sense for those who want the latest Android phones, since iPhones are (so far) on an iterative update cycle with major updates occurring every two years. For the iPhone it’s not the next phone that’s substantially better than the one you have now, it’s the one after that. If you have the iPhone 5 you’ll want next year’s. If you have the 4S you’ll want this year’s. Etc. etc. Things could change, but I think in the United States, the two year contract cycle is the way to go for most people. Today’s phones are powerful enough that the latest can stay relevant for a long time. You couldn’t say that in 2010, but you can say that now if you’re buying a flagship phone.

Permalink

On The Surface RT and Impatience

Nick Bilton of the New York Times writes:

Today’s consumers don’t want options. They are impatient. They want to tear their new shiny gadget from the box and immediately start using it. They don’t have time to think about SD cards or USB drives or pens or flip stands.

The surface RT didn’t allow that. Customers had to think about it.

The Surface RT had a lot of things that didn’t bode well for it. For one the name. The other was Windows RT, which I think is an even better example of what Nick Bilton is describing as far as options go.

I don’t think the Surface’s hardware ever really got in the way. An SD card slot or an available USB port don’t really interfere with what someone will do with a tablet. The kickstand and keyboard accessories are sort of the Surface’s cherry on top. The things that the Surface has on the hardware side are incentives. But I think Windows RT itself wasn’t what customers were looking for in a tablet.

On top of good hardware is an operating system that’s buggy and clumsy, getting in the way of the things people want to do. Windows RT is this cut down version of Windows that doesn’t let you install traditional desktop applications and wasn’t completely optimized for your fingers, and I think customers got fed up with this idea relatively quickly. I get what Microsoft is aiming for, the idea that you can have a tablet for both work and play that gives you a lot of choice in how you use it, but that point didn’t come across in their marketing and Microsoft’s implementation of it (like switching to the Desktop through a tile) ended up confusing people.

Microsoft said, “You can have the best of both worlds!” The result is a product that sends mixed messages about what it wants to do and what it’s really capable of. Surface RT feels like a product that had to hit some arbitrary deadline, was then rushed onto store shelves, and it shows.

The Surface RT doesn’t solve any pain points, which is the kicker. Things like the iPad take away a lot of the stuff that people don’t like about computers. People use their iPads because it instantly turns on, has great battery life, and doesn’t behave like a traditional computer. People generally don’t have to worry about maintaining their iPads. You don’t have to restart it to install updates every week, download the latest virus definitions, or run a cleaner to magically improve the computer’s performance. It’s a worry free device. The Surface RT was supposed to be Microsoft’s answer to these things — a product that sheds all of the legacy components Windows held onto for so long that would make the computer safer and easier to use — but ultimately Microsoft decided people wanted their desktops on their tablets so they could use Office, forgetting that that’s the thing people wanted to get away from. The irony is that the tablet that was supposed to offer more choice than the iPad ended being the compromised experience. That’s why it failed.

Permalink