London from up high (Taken with Instagram at The Broadgate Tower)
m.guardian.co.uk
To see in this year, I did two things I’ve been meaning to do for a long time: I challenged myself to put on as many coats as possible at the same time during a lull in a New Year’s Eve party, and I deactivated my Facebook account. The coats…
This guy took distraction-free writing environments to an extreme. And then still managed to distract himself. Just write.
Android Design - Creative Vision
Do they mean flash or Adobe Flash?
Turn On, Code In, Drop Out: Tech Programmers Don’t Need College Diplomas
Erin Biba, good.isDavid King got his start as a professional programmer working odd jobs. He took on small software projects, set up networks, that sort of thing. For fun in his spare time he’d contribute to the open-source operating system FreeBSD—a…
Microsoft Signature
Paul Thurrott, Supersite for Windows, microsoft.comMicrosoft Signature.
Performance tuned,
handcrafted—you’ll love it!Microsoft engineers have spent time carefully tuning your PC to help achieve maximum performance, as well as including software that makes it really fly.…
Surely Microsoft should spend less time promoting ‘Signature’ PCs and just change their OEM license to ban crapware. It won’t affect Microsoft’s licensing fees, and I doubt it would drive OEM’s to Linux. Or maybe 2012 will be ‘The’ year* * As in definite article.
Android Versions
I really don’t get Android and its version naming.
I understand how versioning works. The first number is the major revision number, i.e. 1.0 is a big thing usually (in fact it shipped on the original HTC G1/Dream). Then it indicates a minor revisions and major bug fixes, i.e 1.5 which was Cupcake. The next digits usually refer to minor bug fixes, i.e. 2.3.3, which incidentally is the most used version of Android to date).
So here is Android’s version history.
1.0 - First Release
1.5 - Cupcake
1.6 - Donut
2/2.1 - Eclair
2.2 - Froyo
2.3 - Gingerbread
3.0 - Honeycomb
4.0 - Ice Cream Sandwich
Google have also chased to give amusing food-based code names to their releases. But they don’t seem to know what a big release is. A minor version number, such as 1.6 for Donut was actually a big change, with a new linux kernel (because, you know, its open) and many new features, like begin able to select multiple photos to delete, or voice and text entry search to include bookmarks and contacts. Wow. Big features.
When Android made a fuss about tablets, they released Honeycomb. Android 3.0. Thats a big release. It was big in that it now supported tablet devices, but by all accounts, it was a painful slow experience. Not surprising that it was only ever shipped on two devices. Gingerbread was a bit of a flop even though Google released 3.1, 3.2, 3.2.1 and 3.2.2 for the devices. But unlike earlier versions, these ‘minor updates’ didn’t justify a new clever name.
Finally we saw Android 4.0 get released in October 2011, 5 months after it was previewed at Google I/O. With a major revision number, we get a new name, Ice Cream Sandwich. And a new flagship phone, the Galaxy Nexus (not to be confused with the HTC Nexus One, the second flagship phone).
Contrast this with Apple. Sure they stick with boring numbers, but when they release iOS 5, its a major revision, with major features. You know its a big one. And you know that 4.2.1 is really just a bunch of bug fixes. Reading the wikipedia page for iOS and you get a laundry list of every tweak, change and update. And its clear that 4.2 was minor feature updates, and bug fixes. It makes sense.
Google don’t seem to be able to set a precedent for the next version of Android (Jelly Bean? Jam?). We can’t even guess if it will be 4.1, 4.2, 4.3, 5.0 or something else completely. But whatever version they decide to release next, with its silly food name (which at some point they’ll hit issues with. Q?), I’m sure it too will have a flagship phone, and I’m sure that Jelly Bean won’t get updated on most Gingerbread phones, and even less Froyo phones.
But at least it’s open.
mkdir android ; cd android ; repo init -u git://android.git.kernel.org/platform/manifest.git ; repo sync ; make
Phew.
Neven Mrgan: What iMessage did to my text-messaging usage
Three months into iOS 5, I’m using a trivial quantity of text messages. I currently pay $10/month for up to 1000 messages. Assuming these bill at 20c/message (it varies depending on your plan, I’m told) I could cancel my messaging plan and end up paying less overall, even at that outrageous price.
Neven has posted his SMS usage over the past year or so and you can see how rapid the drop off is when iOS 5 was released.
In the UK, we usually get stupid amounts of inclusive SMS with our mobile phone plans. I have the Three One Plan. I get 5000 free SMS messages a month, 5000 same network voice calls, and unlimited data (yes actual unlimited. I hit 1.8Gb the other month via the inclusive tethering). We also don’t pay to receive messages.
Here is my chart from the same time period.

Not really a massive correlation, but there is a distinct drop off after October, even so much as dropping my SMS usage by 75%.
Its more than clear to me that iMessage will replace SMS for all my iPhone using friends. And FaceTime has replaced Skype. I’m just waiting for the final piece of the puzzle, voice over 3G data, and then all I need from the carrier is a data pipe.
The Podcasting Challenge
So many issues with this article about how difficult podcasting is.
Clearly as Adam’s figures show, podcasts from the BBC and other radio stations are huge, in part because of the massive push they give their shows and their already huge audiences.
Adam argues that the majority of people make the connection between podcasts and the iPod, and its easy to understand why. When podcasts were being invented, they were initially just short audio attached to an RSS feed, all around 2004. It wasn’t until 2005 when Apple introduced the Podcast store in iTunes and listening to podcasts became more popular.
In today’s modern age, most people who listen to music use an iPod, and there are an estimated 100m-150m iPods in use in the UK according to The Guardian. But today, most of those are propably actually iPhones and iPod Touches, and that adds another component. iTunes is likely the most popular way to get podcasts on your device, which ties you to downloading podcasts on a single computer and syncing them to your device. But with the advent of the App Store, there are now a ton of great podcast clients on your mobile phone.
One of the most popular is Instacast. It has a built in podcast directory, or you can click any podcast link in a web browser to subscribe. The app will download all the new episodes for you, so you’re no longer tethered to one computer. And if you also use an iPod or iPad to listen to podcasts, your subscriptions and current playback positions are synced across devices with iCloud.
To address Adam’s list of ‘fixes’ :
• Apple doesn’t exert any rights over the term podcast. Its here to stay.
• There is a file format already. M4A is an enhanced AAC file that can include chapter markers for shows. But since its still just audio, why change from M4A and MP3. In fact a podcast can be any audio file in existence. You can put video and PDFs in a podcast feed too.
• Syncing podcasts isn’t the issue. Its getting them on your device to start with. See my point on the App Store. Even Google has its own Podcast client, Google Listen. As does BlackBerry
• Subscribe is an appropriate term. You can ‘subscribe’ to an ethos. Subscription doesn’t hold an inherent payment requirement.
• We already have a pcast:// URL scheme that can be used by any application to catch a podcast feed when its clicked. Instacast can use these, as does iTunes, although iTunes also offers an http URL that points to the page in the iTunes Podcast Directory.
Adam also addresses monetization. Ricky Gervais switched to a paid model for his second series of podcasts. For this, he released them as a series of audiobooks. iTunes does support authenticated RSS feeds too, meaning that as a creator, you could have a website signup and provide user details to all subscribers. That way you also get direct knowledge of who is subscribing and can get marketing feedback from it.
Many other creators go down the route of advertising, and that seems to be fine for people. For smaller creators, there is already a cost associated, with purchasing a domain name, web hosting, recording equipment, but it is very possible to do it for cheap, using Tumblr, FeedBurner or a combination of other free file hosting services.
Without going the route of the typical example, my mum, who is somewhat computer literate, was able to download and listen to the Chris Moyles podcasts without needing to call me at all. Which is quite a shock given previous history.
Finally, I don’t understand why he goes on to mention NFC, Near Field Communication, as I can’t see how that could have any relevance to the availability of podcasts to listeners. Unless he is suggesting a podcast purchase terminal you can walk up to and wave your phone at, i don’t see how NFC is relevant at all. Paypal has some relevance. In fact I have just become a member at ShawnBlanc.net, and pay him $3 a month via a Paypal subscription to support him writing full time, and for his podcast. The Mac Observer’s Mac Geek Gab also have an online premium subscription of $25 for 6 months access to their premium shows. All done with existing payment systems.
Realistically, podcast applications on smart phones, which already exist, and perhaps need more awareness, are the key to podcast popularity growing. Since these are often the devices you use to listen, when walking, on your daily commute, in the car, at the gym, that is where we need to see the growth. And you can always listen live to some of the bigger shows.
