Drop support, but leave old versions around

Handpicked

In a recent post called Dropping Support for Older OS Releases, Brent Simmons suggests that developers drop support for older OS releases as a way to optimise resources and keep making quality apps. From a developer’s standpoint, he’s certainly right. From a user’s standpoint, there are some observations to be made here. He gives three main reasons to drop support:

There’s almost no barrier to OS updates these days. They’re free and easy to install.

True. Unless your Mac doesn’t support the latest version of Mac OS X.

People who don’t upgrade their OS are also the kind of people who don’t buy apps.

If I may, this is a rather superficial assessment. There are at least a couple of reasons behind not upgrading to the latest OS release:

  1. Not everyone owns a new Mac, and not everyone purchases a new Mac every year or so. There are still a lot of perfectly good Macs in use that cannot be upgraded past Mac OS X 10.7.5 (MacBooks from 2007 and 2008, the original MacBook Air, some older MacBook Pros, etc.)
  2. There are people still on Mac OS X 10.6.8 (Snow Leopard) because they find it to be a better performer and a more stable version than Mac OS X 10.7 Lion on their machines. And if they also own one of the aforementioned Macs which can’t even be upgraded to 10.8 Mountain Lion, I perfectly understand why they’d want to stay on Snow Leopard. I recently helped a friend configure his home network, and he still owns an early 2007 MacBook Pro with Snow Leopard installed. While using his MacBook Pro, I noticed how snappier it felt than mine, which is almost three years newer and runs Mavericks. And while the ‘performance feel’ of a Mac might be subjective, things like Wi-Fi stability are not. Using my friend’s older MacBook Pro reminded me of how generally bad Wi-Fi performance has been in OS X from Lion onward.

In both these cases, I don’t see any correlation between not upgrading and not buying apps. On the contrary, I know people who would love to buy more apps for their older Macs, but with OS X 10.8 Mountain Lion as a minimum requirement, they simply can’t.

An app succeeds based on quality, not breadth of OS support. You can make a better app by using newer APIs. You can make a better app by not having to spend coding and testing resources supporting older versions of the OS.

Nothing to argue here.

Brent adds:

Yes, you will leave some small number of people behind. It’s worth the trade-off, though, because it’s your job to make the very best app you can make.

Well, I don’t know about that small number, especially outside the North American tech bubble. Anyway, I have a humble suggestion to add to Brent’s overall very agreeable point of view: developers willing to drop support for older OS releases should keep older versions of their apps available for those users who don’t own the latest Macs and/or can’t upgrade. For example, if version 1.2 of an app is the last version supporting OS X 10.6 Snow Leopard; 1.5 is the last version supporting OS X 10.7 Lion; and now the app at version 2.0 only supports OS X 10.8 Mountain Lion and above, then they should leave those previous versions available on their site (since it’s not possible on the Mac App Store), clearly indicating that support is only available for the latest version. This way, even users on Snow Leopard and Lion can enjoy that app, even if it may lack features introduced at a later date. 

Many (Mac) developers don’t seem to do so, instead they maintain very streamlined websites showcasing only the latest version of their app. I don’t see any significant downsides in leaving older versions available for download. They can focus on perfecting their app for the most up-to-date audience, while leaving virtually no one behind.

Why the WordPress iOS app is useless to me

Briefly

The WordPress iOS app has indeed improved over time, especially for writing a blog post, but still not enough to be a solid official client, in my opinion. I don’t know you, but the main reason I installed this app on my iOS devices was to manage my blogs, rather than using it as an on-the-go solution to write on them, or to ‘interact’ with other WordPress blogs in the same way one does with Tumblr, for example.

Therefore, in its current state, and for my current needs, the WordPress app is of no real use to me. There are a few little annoying things, interface-wise, which have led me to get rid of it.

 

#alttext#

1. The mildest peeve is visible in the figure above: the default section when you open the app is Reader. Since I’m not following any blogs, I keep getting this screen. It would make more sense that the app defaulted to the Me section, wouldn’t it?

 

#alttext#

2. When you get a notification, and you go and act on it, the action buttons have no feedback. In the example above, I received a comment which I need to mark as spam. When I tap on the flag icon, nowhere in the interface I get a confirmation that my action was registered, and I’m left with the doubt whether the app has acted on it or not.

 

#alttext#

3. When I return to the Notification screen, some comments in the moderation queue are marked as Pending, even after dealing with them. At first I didn’t know why this happened, then I remembered that I had handled those comments via the admin interface in the browser on my Mac. Evidently the app doesn’t sync what gets moderated outside the app. The result may be confusing, especially when you tap again those Pending comments, try processing them again, and nothing appears to happen because of the aforementioned ‘no feedback’ problem.

Wherefore art thou, Poster?

In June 2013, Automattic acquired the great Poster, a WordPress iOS client by Tom Witkin. I personally find a bit infuriating that they removed Poster from the App Store, when they could have simply rebranded it and make it the official WordPress client, like Twitter did with Tweetie. Poster had a really nice interface and was definitely more mature an app. Instead, at least for now, we’re left with this rather bland offering.

Unread: the brief review

Software

Unread article list dual

Unread is a new RSS reader for iPhone by Jared Sinclair, also developer of Riposte (an App.Net client) and Whisper (a group messaging app for App.Net).

Jared Sinclair begins his article Designing Unread by stating that at the time he decided to make Unread, he wasn’t using RSS anymore. I had stopped checking and reading my RSS feeds on the iPhone soon after Google shut down Google Reader and my then-favourite RSS app, Reeder, stopped working as a consequence. Then Feedly debuted, and I decided to use that service mainly because it made the transition from my previous Google Reader account very painless. 

But when I resumed reading RSS feeds on iOS, it was only on the iPad, and with the Feedly iOS app itself, which I instantly liked for its Flipboard-style article presentation. On the iPhone, at first I thought about returning to Reeder after its update as Reeder 2, but I admit to not being thrilled by having to pay €4.49 for an app that had essentially regained its ability to synchronise with a RSS service, and not much else. In recent times, an interesting app — My Paper by Harry Works — brought me back to reading RSS feeds on my iPhone. It’s a free app, with a nice iOS 7 design, and there’s much to like about it. But I ultimately knew it was a temporary solution.

As soon as I heard about Jared Sinclair’s project, and read his article The Philosophy of Unread, My Forthcoming RSS App, I was sold. Considering how much I like Riposte, I knew that Unread was going to be an app made with care and attention to those details that really make an app work. I knew I would purchase it as soon as it hit the App Store.

I promised a brief review. Here it is, in the form of a list of personal highlights about Unread.

  1. The choice of typefaces is perfect. Whitney and Whitney Condensed by Hoefler & Co. They make for very pleasant reading (see image above).
  2. Gestures. In a post directed to Sinclair over at App.Net, I wrote: I usually don’t like apps whose navigation relies on gestures a lot (I am a button fan), but your apps are something different — gestures are implemented so thoughtfully it all feels very natural. And I mean every word. Perhaps the reason I like gestures in both Riposte and Unread is well explained in Sinclair’s Designing Unread: “One of the things I learned from people’s positive feelings about Riposte was the importance of using gestures solely for navigation and not mixing navigation gestures with action gestures.”
  3. The bottom bar. You always know where you are.
  4. Article summaries are not truncated.
  5. This: If an article is determined to be a Linked-List style article — i.e. the article’s URL is a link to another site and not the permalink — then the domain of the linked item’s URL is displayed at the bottom of the summary. (I’m quoting again from Sinclair’s article)
  6. The tasteful use of colours. Unread’s basic palette revolves around white, black, red and dark grey. As a result, all icons appearing in menus throughout Unread really pop. I like that.
  7. The easter eggs (hidden colour themes).
  8. Gestures. Again. You don’t have to position your thumb on a particular spot to swipe and navigate inside the app. “This helps make Unread comfortable to use with one hand, no matter what size iPhone you have or how big your hands are.” (Again quoting from Designing Unread)
  9. Unread has character. See this other quote from Sinclair: “I didn’t make it to be a feature-for-feature replacement for an app you may already be using. That would make Unread merely a thin coat of paint on old ideas.”
  10. The bottom bar in Unread’s built-in Web browser. Nothing special, you may say. I say it fits perfectly the app’s fluid navigation.
  11. Unread performs very well on an older device like my iPhone 4.
  12. There are 1.0 apps which, after purchasing them and using them for a bit, get me thinking about which features they lack. You know, when you think It would be cool if (App X) had this and/or could do that…. After purchasing Unread yesterday, I had 395 unread articles in my feeds and spent a good while reading them, enjoying Unread for a good couple hours of continued use. Never for a second did I think something was lacking or needed refinement. To me, Unread is that good. But of course it’s a matter of personal tastes and needs.

Launch price: $2.99/€2.69. It’s worth every cent.

Some observations after a typeface hunt

Tech Life

Choosing a typeface today is difficult, simply because one is spoilt for choice now more than ever. Among other things, in the past few days I’ve been busy choosing a couple of typefaces for two different purposes. All in all it was a fun ride in the labyrinthine world of quick brown foxes jumping over lazy dogs. In three occasions I had to declare ‘typeface overdose,’ take a step back, think again about what I was looking for, rest my eyes, and finally resume the hunt. There were moments when I had to remove my type nerd hat and wear the concerned-customer-with-a-tight-budget hat. Moments when I did a bit of role-playing, alternating between the guy who knows what’s behind type design, and the no-nonsense, layman client who’s looking for a Didot/Bodoni alternative and is utterly lost among the seemingly identical variants offered by numerous foundries.

This search process may make you chuckle, but if you’ve ever found yourself in a similar situation, you know things can get boring, repetitive and frustrating rather quickly. This game of switching perspectives turned out to be entertaining during my little typeface hunt, and also useful, I guess, because it got me thinking about a series of things perhaps worth sharing. Now, before I proceed with my scattered observations, I want to stress once again that I’ve accumulated enough experience over the years to understand the work and the process behind type design, and that maybe what I’m saying here has been already discussed ad nauseam in numerous typography forums and circles. But again, it’s also an exercise in different perspectives, so bear with me. I’m also not interested in making specific examples because these are general observations and singling out typefaces, designers and foundries would only be misleading.

Quality and pricing

The layman’s dilemma: This font, offered in its four basic styles (regular, italic, bold, bold italic) costs almost 600 euros. This other font, rather similar to that one, costs 20 euros per style, so a total of 80 euros for the four basic styles. Why this huge difference in price? The cheaper font doesn’t look of a lesser quality to me.

The type designer, the type enthusiast, the type nerd, et similia, are already rolling their eyes and pointing out subtle differences in the execution, in the number of glyphs the two fonts provide, in the number of alphabets they support, in OpenType features, in the licensing options and scope, and so on and so forth. One typeface could be a quick knock-off of a pre-existing specimen made by a team of typography students, the other may be the result of many years of work of a single designer who carefully digitised an 18th Century typeface previously available only in print, making by hand all the necessary corrections to adapt that typeface for display use. I could explain all this to the layman and I’m sure I would still get a baffled look in return. You know, just like when a wine connoisseur is explaining to you the difference in flavour and aftertaste of two different samples of red wine which taste absolutely the same to you.

For laypersons and people who are simply looking for some good typefaces for a project or for their small businesses (I’m not talking about medium and large companies here because usually they have enough resources for these things — meaning people hired to take care of typographic matters, and money to invest in such matters), the world of type can be confusing. I have helped people choose or make informed decisions about typefaces in the past, and I’ve noticed how they approach their search. They tend to apply to typefaces the same evaluation methods they use when shopping for other, more material goods; realise such methods don’t really work; and end up feeling a bit lost. When they shop for clothes and accessories like watches, bags, kitchen utensils, smartphones, computers, and so on, they usually associate high prices with two main reasons (which are not mutually exclusive):

  1. The product is of high quality
  2. The product comes from a popular brand, well known for manufacturing premium products

Sometimes people stumble on an expensive product, but they understand its price tag either because they can immediately appreciate the quality of the product (even when it comes from a company they don’t know), or because they recognise the manufacturer’s brand and they nod and say Of course these trainers cost 300 euros, they’re from Nike. And maybe those trainers aren’t really worth 300 euros but the well-known brand is synonymous with good quality and so that price tag is somewhat justified.

This approach, of course, doesn’t work in the type world largely because:

  • A typeface priced at 40 euros isn’t necessarily of a lesser quality than a typeface priced at 400. There’s an increasing amount of talented indie type foundries and designers producing amazing typefaces, both for print and the Web, at very reasonable prices.
  • While there are prestigious type foundries and type designers producing typefaces of stellar quality, most laypersons have never heard about them.
  • For a layman, assessing the quality of a typeface is not as immediate a process as, say, assessing the build quality of a watch or a smartphone. Some people have learnt to discard ugly free fonts, where the lack of quality is apparent, but once they move to ‘nice-looking fonts’, everything is a blur.

All these factors play a relevant part in the aforementioned layman’s dilemma, and the resulting feeling is that typeface prices are largely set arbitrarily, that certain foundries are simply out of their mind if they expect a single person (as opposed to a business or company) to purchase that typeface family of theirs, priced at 4,500 euros.

Communication

During my typeface hunt, I’ve visited a lot of websites of type foundries (small and large) and independent type designers, and while plenty of them are really well done, presenting typefaces in great visual detail and with luscious effects, I often had the feeling as if I were shopping for devices by only looking at data sheets. In this regard, the best sites I visited were generally those created by small operations and single designers, going the extra mile and trying to communicate something more than typeface characteristics, features, formats supported, licence options, complete lists of glyphs in grid view, and prices. 

They also provide information about how that particular typeface was born, the needs they want to fulfil by providing such typeface, best use cases, and so on. In other words, they are trying to speak to the prospective customer in a language he/she understands. They do not assume that all visitors coming to their site are type nerds or experts who already know what they’re looking for and already have the necessary expertise to appreciate the designer’s work, to instantly recognise the quality of the offering, therefore understanding why certain typefaces are more expensive than others. 

By contrast, I found big type foundries to lack such communication, in general, relying instead on their prestige and have that prestige ‘do the talking’, which might be understandable — you don’t enter a Cartier shop and act surprised at the insanely high prices of the jewellery on display, and Cartier’s salespersons expect you’re entering the shop because you know about the brand’s prestige and can afford to purchase its products, otherwise you would go elsewhere. But the fact is that not everybody is up to speed on the who’s who of typography and type design. What many prospective customers see are austere, nice-looking fonts with prices they can’t immediately justify. The informed customer may know he or she is visiting the website and perusing the catalogue of a famous type foundry with an impressive pedigree. The layperson may not realise this on the spot. 

Of course, when your typeface catalogue consists of hundreds of typefaces produced during decades of operation, it’s impossible to dedicate a lot of room for detailed information about each typeface. Also, many important type foundries may be already satisfied with their business and existing customers that don’t feel the need to be more communicative to sell their products. Still, having some more pages providing essential information to laypersons on how to choose typefaces, how to approach typography both offline and on the Web, how to recognise (and choose) quality products, etc., would only be beneficial to everybody. 

The world of typography and type design is amazing, and the more you know about it, the more amazing it gets. I still find places on the Web where, instead of useful advice and information, one gets a good dose of elitism in return. Certain type experts should drop the attitude and have a more educational approach with laypersons who manifest even a tiny bit of interest towards typography. Many complain about the generally mediocre conditions of typography on the Web, but the fact is that the Web is full of personal sites and blogs of people who don’t have a clue about what good typography is, and don’t have a clue as to how they could improve their bland or eye-straining websites, type-wise. There should be more initiatives like Matthew Butterick’s Practical Typography, which has become the first reference I tend to suggest when someone asks me for a good, handy starting point on typography.

The more informed the audience, the better choices they make, because they can appreciate type design, see typefaces in a whole different way, and better understand how to look for quality products when they need them.

Celebrating 30 years of the Mac

Tech Life

In case you didn’t notice, the Mac turns 30 today. Apple has created a fantastic mini-site to celebrate this milestone. I wanted to celebrate in my own way, going down memory lane with a bunch of photos of the Macs in my collection, the majority of which still work today. 

My first Macs

My first Mac wasn’t a Mac I owned, but a Mac I worked on while apprenticing in a small ad agency in 1989. It was a Macintosh SE FDHD (so called because it had a 1.44MB floppy drive and a hard drive, instead of two 800K floppy drives), with 4MB RAM and a 40MB hard drive. The other part of my first Mac workstation was a LaserWriter IINT printer connected to that Macintosh SE. I spent a lot of time working in Quark XPress 2.1. That’s how I got introduced to Desktop Publishing. 

My first personal Mac was a Macintosh Classic, with 4MB RAM and a 40MB hard drive, purchased second-hand in late 1990. I still have it, and it still works. A few years later I got my first Mac laptop — a PowerBook 150 (16MB RAM, 250MB hard drive), purchased second-hand in 1995 with an external 2x SCSI CD-ROM drive. It’s probably one of the most underrated Macs due to its limited expandability (it notably lacked an external ADB port and a video out port, and had only 1 serial port and a SCSI port), but I really liked its screen and it was a little workhorse overall. It also had one of the most reliable floppy drives I’ve ever seen on any Mac I’ve owned. It’s also one of the very few Macs I sold. On the one hand, I regret selling that particular Mac, on the other it helped me raise funds to purchase a PowerBook Duo 280c with an external 14-inch Apple Color Monitor and DuoDock II unit for a complete Duo workstation. The DuoDock broke down in 2005, sadly, but both the PowerBook Duo and the monitor still work today.

My Mac collection

At present, these are the Macs I own. An asterisk after the name means the unit is not currently working.

Desktops and towers:
  • Macintosh 128K *
  • Macintosh SE FDHD
  • Macintosh SE/30
  • Macintosh Classic
  • Macintosh Colour Classic
  • Macintosh LCII
  • Macintosh Performa 630CD
  • Macintosh Quadra 950
  • Power Macintosh 9500/132
  • Power Mac G4 Cube
Laptops:
  • PowerBook 100 *
  • PowerBook Duo 280c
  • PowerBook 5300ce
  • PowerBook G3/400 Lombard
  • iBook G3/300 blueberry
  • iBook G3/466 SE graphite (FireWire)
  • PowerBook G4/400 Titanium
  • PowerBook G4/500 Titanium
  • PowerBook G4 12″ Aluminium (1 GHz DVI)
  • PowerBook G4 17″ Aluminium (1.33 GHz)
  • MacBook Pro 15″ (Mid-2009, Core 2 Duo 2.66 GHz)
Newtons:
  • Original MessagePad
  • MessagePad 2000
  • MessagePad 2100
  • eMate 300
Other Macs I have owned:
  • PowerBook 150
  • Macintosh Quadra 700
  • iMac G3/350 blueberry

Memories in photos

Five compact Macs
My compact Macs — on top: Original Mac 128K. Middle row: Macintosh SE FDHD and Macintosh Classic. On the floor: Macintosh Colour Classic and Macintosh SE/30. Also visible: my blueberry iBook G3/300. This photo was taken on April 2010. Save for the 128K, which needs some repairs, all these Macs are still working. (See also this article on my System Folder blog.)

 

At the old flat
Photo taken at my old flat. This was my studio in October 2004. Zig-zagging from top to bottom you can see a Macintosh Colour Classic, the Duo workstation mentioned above, a Macintosh Quadra 950, a clamshell iBook G3/466 FireWire SE, a PowerBook G4 12″, a PowerBook 5300ce and a PowerBook Duo 280c. (See more photos from the old flat in Past setups, another article over at System Folder).

 

Mac SE30 and Colour Classic
Passing some data between a Macintosh SE/30 and a Colour Classic connected via serial cable.

 

PowerBook and Newtons
PowerBook 5300ce, Newton MessagePad 2100 (in a 2000 case) (top), Original Newton MessagePad (bottom).

 

PowerBooks and Newton
The PowerBook G4 Titanium (right) connects to the Internet and downloads software for the Newton. The PowerBook 5300 (left) connects to the TiBook via Ethernet and installs the Newton packages on the Original MessagePad (center) via serial cable.

 

iBook and eMate
Another Newton connection: the eMate 300 (left) connects to the iBook G3/466 (right), again via serial cable and a Keyspan Twin Serial Adapter.

 

DSCN4073
PowerBook Duo 280c.

 

DSCN4101
Power Mac G4 Cube connected to a 22″ acrylic Apple Cinema Display.

 

DSCN4244
My studio in April 2010. Visible from left to right: PowerBook G4 12″, PowerBook Titanium G4/500, Power Mac G4 Cube connected to the Apple Cinema Display, and a MacBook Pro (mid-2009) connected to a 20″ Belinea display.

 

DSCN4507s
This was a fun thing I did one afternoon: connecting my iBook G3/466 to my 42″ Sony TV using the Apple A/V Cable I got when I purchased the iBook in 2002.

 

IMG 5780
Left: Macintosh SE FDHD connected to a Maxoptix SCSI Magneto-optical drive; right: PowerBook Duo 280c.

 

IMG 5783
Left: PowerBook Titanium G4/400; right: PowerBook G4 17″ (1.33GHz).

 

17 and 12
Left: PowerBook G4 17″; right: PowerBook G4 12″.

 

IMG 2911
After a writing session on my PowerBook G3 Lombard at a Starbucks.

 

IMG 0720
iBook G3/300 and a borrowed copy of the seminal AppleDesign book.

 

DSCN0162
Detail of the original Mac 128K motherboard.

 

DSCN0163
The Motorola 68000 at 8 MHz of the original Mac 128K. (See other photos of my Original Mac 128K in this post over at System Folder).

 

DSCN0046
A detail of one of my AppleDesign Powered Speakers II, that were released in May 1994 in beige and black colour variants. They still work, still sound great, and are part of my main Mac setup. (See a beautiful gallery of the black speakers at Shrine of Apple).

 

DSCN1557
Left to right: Original Newton MessagePad, original Macintosh manual, Commodore VIC-20 Programmer’s Reference Guide.

 

DSCN3606
Left to right: PowerBook G4 Titanium, Mid-2009 MacBook Pro.

 

DSCN4117
iMac G3 Accessory Kit box: it contained the keyboard, mouse, power cable and documentation. Sadly, that iMac died in 2003, but I still own the box and all the accessories.

 IMG 3186

Another photo of one of my favourite Macs of all time, the Macintosh Colour Classic.

 

DSCN0116
My beloved iMac G3/350 blueberry, with matching Iomega Zip 100 drive and CD-RW burner.

 

iPod Mini
iPod mini 4GB (introduced in 2004).

 


 

If you want to see more photos of this kind, I have a couple of Mac-oriented Flickr photosets: On Macs and men and The setup.
On my System Folder blog I also collected a few Apple vintage Italian brochures (here and here) and other brochures from the 1990s. Enjoy.