Apple

Turning an iPhone into an Apple ][

Tuesday, February 24th, 2009

200902241840.jpg
What I see when I power-up my iPhone. Below this should hopefully be an embedded QuickTime player set to play my Apple ][ disk drive ringtone.

A couple of weeks ago I met up with my friend Ben and we transferred a bunch of old apple II disks across a serial cable into a Linux box and saved them as disk images. Now I can once again run the programs I wrote in 3rd grade, in an emulator. While we transferred the disks, I was struck by the sound of the apple floppy drives and by the fantastic graphic design on the disk sleeves.

I snapped a photo of the disk sleeve and recorded the sounds of the disk drives with my iPhone. I took the disk drive noises and edited them into a ringtone, and set the disk sleeve image as my iPhone home screen background image.

The ringtone begins with the Apple II’s boot sequence and then transitions to a repeating sequence of disk head recalibration sounds. If you ever had an Apple II, you’ll recognize all of these noises. I installed the ringtone by double-clicking it (which loaded it into iTunes) and then syncing my iPhone to install the ringtone. It was then available in General Preferences > Sounds.

In case anyone else would also like to use this ringtone, I’ve added it to this post as an attachment. I have also attached the disk sleeve background image.

Download Apple ][ ringtone

Download Apple ][ disk sleeve image

Palm Pre Thoughts — a bit of perspective

Monday, February 23rd, 2009
I want to talk a bit about the upcoming and wildly anticipated smartphone from Palm, the “Palm Pre“. The Palm Pre is the latest in a long line of hyped iPhone killers. Tech journalists have declared,”The Palm Pre has it all, making the iPhone look almost like — dare we say it — a version 1.0 device” and that it is,”maybe the most important handset to be announced in two years” 1.

I think the Palm Pre is a very nice piece of hardware, with a set of supplied applications that look very nice, but this smartphone is massively overhyped and has a huge, gaping problem: The lack of an SDK that allows the compilation of native applications –incidentally this is the same problem that initially kept me from considering the purchase of an iPhone.

The iPhone was roundly criticized for the same defect, but the makers of the Palm Pre have been shockingly successful at that which Apple failed to do: to give a positive spin to this policy/design-defect. In the case of the iPhone, Apple was able to recant their initial position and fix the issue, leveraging technologies they had been developing for years 2. Palm will not be able to issue so seamless a fix, as the Palm Pre’s OS is brand new, and I doubt Palm has very robust development tools or frameworks they can prepare quickly and distribute to the eager developers who will gather as soon as Palm Pre users tire of applications that are glorified web sites and want to do things with their phones that simply can’t be done using javascript and html.

To gain a bit of perspective on the Palm Pre, I think it is necessary to take…

Iphone Apps

…A look back at developer response to the initial iPhone announcement

When Apple first announced the iPhone, they announced there would be no way for developers to compile native binaries that run on the device, but instead announced that developers could create wonderfabulous web 2.0 applications that would run on the phone:
Developers can create Web 2.0 applications which look and behave just like the applications built into iPhone, and which can seamlessly access iPhone’s services, including making a phone call, sending an email and displaying a location in Google Maps

The response from grateful, would-be iPhone app developers? Try this google search for “iPhone no SDK”. A couple of choice quotes from the results:

Apple took a ton of heat from developers and users for their initial decision, and eventually did release an SDK to allow developers to write native applications for the iPhone. The iPhone runs OS X as its operating system, and Apple has a long history of creating and distributing tools for OS X development as well as Frameworks to simplify the creation of rich applications 3. Not only are these tools and frameworks feature-rich, mature, reasonably well-known, and stable, they are also the same tools and frameworks used by Apple to build the operating system and the applications they supply on the iPhone.

Most of the third-party apps I frequently run on my iPhone (most prominently: Beatmaker, Evernote, Fring, Brushes, and iTalk) would not be possible to create as web apps with Ajax and Javascript. Those that could possibly be programmed in javascript, such as the iPhone OmniFocus app, probably shouldn’t be. They’re complicated enough that it would be difficult to design them as web apps that have good performance 4 and manageable code.

My final rant

As far as I can tell, there’s no native development environment for the Palm Pre, nor is there one that will be popping up soon. Would-be developers face the same silly web-app-only idea for which Apple was roundly criticized when they first launched the iPhone. It’s actually the same silly web-app-only idea which has probably contributed to the lack of applications for the Sony Mylo devices 5.

Unless the built-in applications are spectacular and completely fill the needs of most smartphone consumers, real third-party applications will be necessary for the Palm Pre to make more than an initial blip in the smartphone market. I don’t expect there’ll be many interesting apps available for the Pre until they give developers a bunch of useful frameworks and the ability to compile binaries for the device. The iPhone has a huge advantage here in that iPhone developers get to develop and compile apps for a mature platform based on an OS and frameworks that have been around for years.

As a long-time Palm user and advocate, I’m glad they’re back in the game, and I look forward to being proven wrong on all counts.

Notably ommitted from this analysis because I tired of thinking and typing: Windows Mobile, Nokia 6, Android, OpenMoko.

  1. An endorsement that is simultaneously breathless AND wishy-washy. ↩︎
  2. Some of the OS X development technologies are approximately 20 years old, having been born at NeXT. ↩︎
  3. See previous footnote. ↩︎
  4. Web apps are slow enough when running in web browsers on multi-gigaherz multi-core computers, let alone puny 600Mhz power-saving mobile processors with limited ram. ↩︎
  5. And this lack of apps might be part of the reason nobody’s ever heard of the Mylo, which like the Palm Pre has decent hardware ↩︎
  6. Nokia sells way more smartphones than any other player, more than twice as many as Apple. It does seem odd sometimes that the question is “What’s to be the iPhone killer”. ↩︎

Visitors from up North

Friday, February 20th, 2009

I’m having coffee with former Apple coworkers Mark and Enrique over at Fred Segal before catching a film at the New Beverly. And I figured I’d use this as an opportunity to try the iPhone wordpress app.

Nice Deal: Shure i2c in-ear monitors (earbuds)

Tuesday, November 4th, 2008


“Shure I2C-MP Stereo Earphones / Headset (iPhone Compatible)” $39.69 at Amazon.com

I previously owned a pair of Shure e2c earphones, which were very nice. When used with the foam earpieces, they isolate from ambient noise and produce a very detailed sound with a decent amount of bass. I ended up listening through them at a much lower volume than I would have with less isolating headphones.

Shure makes a set of earbuds called the i2c, which are simply their e2c earbuds with the addition of thicker cables, an inline microphone, and an iPod connector (looks like a standard 3.5″ stereo jack except it has one extra conductor for the mic). As an iPhone headset, the i2c has faced some criticism due to the fact that it lacks an inline answer/hangup button. Perhaps because of this minor inconvenience, Amazon.com has recently dropped the price of the i2c headsets from $119 to about $39.

I don’t care about the button, or the mic, since I don’t have an iPhone. For a nice pair of earbuds, that price happens to be a great deal. I placed my order last week thinking that if the iphone plug wasn’t compatible with my ipods that I’d cut it off and solder a standard miniplug in its place (ignoring the mic wire). It turns out that the iPhone connector works fine in both my 1st-gen iPod Nano and 1st-gen iPod Touch. Right and left channels nicely separate, and the sound is good. The mic connector on the plug doesn’t seem to short or otherwise interfere with the contacts for the audio outputs –your mileage may vary. It’s working for me (I suspect the connector was designed to work in both iPhone and standard mini-stereo jacks, but don’t quote me on that).

If you buy a pair of i2c‘s (or any in-ear monitors really) I’d recommend tossing the silicone sleeves they ship with (with extreme prejudice) and instead using compressible foam tips so that the earbuds really make a nice seal in your ear. The sound quality will be much improved, and the bass presence and detail will increase. Shure sells orange foams that works well, many on the net tout Shure’s tapered black “olive” foam sleeves for greater comfort and cleanability, and I’ve heard good things about the Comply viscoelastic polyurethane memory foam tips.

I ‘m happy to now have a nice pair of earbuds to use for running (My Future Sonics FS1’s finally died, and I don’t want to subject my FS Atrios to the same abuse). Yay. If you’ve been thinking of replacing your iPod earbuds with something better, this here’s a very good deal (on something much much better).

bulletin: iPhone USB adapter recalled. How Palin’s email was cracked.

Friday, September 19th, 2008
Apple Usb Power Supply
If ye power supply be featurin a dot most viridescent, drink up me hearty. That be the safe, new replacement adapterr. If ye adapter be flying a blood red jolly roger, beware. Ye be in great peril. Arr. 儿.
Two notes of note:

  • Apple has recalled the Ultracompact (sic) USB Power Adapter that they provided with the iPhone 3G. It is not that the device will burst into flame or do anything so catastrophic; The problem is simply that the metal prongs aren’t perfectly anchored in that delicious little white plastic cube, and “under certain conditions” the prongs break off and remain in the electrical outlet when the adapter is unplugged. As anyone who has ever before seen two shiny and arcing bits of metal sticking out of an electrical socket can tell you, it is humanly impossible to resist immediately grabbing barehandedly at such conductors. Y’all iPhone cult members can get your USB Power Adapters exchanged for free from Apple.
  • Some (insult deleted as I don’t want to be hacked) college student cracked open Alaska Governor, Republican Vice Presidential candidate, and former Miss Wasilla Sarah Palin’s yahoo email account 1 and posted its contents online.
    Img 5517 2
    3/o2d399Jp says "arrf"
    According to the cracker’s 1st person account, he simply reset her yahoo email password by guessing his way through the security questions that are part of the “I forgot my password” process on Yahoo and on many other sites. I long ago realized the vulnerability of such identity verification processes which use simplistic questions like “What is your pet’s name?”. This is why for years I’ve been using a “strong password generator” application to make sure my pets’ names all are of sufficient length and contain enough symbols and numbers to be difficult to guess. You should do the same.

That is all .

  1. Yes, I think there ought to be a law restricting public servants from using private email servers for government business simply to evade scrutiny, and yes I think it sounds like possible evidence tampering that her emails have conveniently been deleted given that there are ongoing investigations that have subpoenaed Gov. Palin’s email messages, but I still think it is sick and wrong that someone has cracked her account and posted the information online. ↩︎

Testing the iphone wordpress blogging app

Wednesday, July 30th, 2008

One of the free apps in Apple’s new “app store” for iPhone and iPod touch is “wordpress”. Looks like it is not only free, but nice.

Without me ever telling them my idea, they’ve set it up to post a mostly blank blog entry, and then snarf in the entry to extract the blog’s template. The app then uses the captured template to generate an accurate wysiwyg preview so you can evaluate your post before submitting. Nice.

I guess I don’t have to write my own iPhone blogging client now. This one will likely do.

Finally, Chinese handwriting recognition for iPhone!

Wednesday, April 16th, 2008

If you’re an iPhone or iPod Touch user who would like to be able to input Chinese characters using handwriting recognition, today is your lucky day:

200804162008
A screenshot of me using the HWPen input method to write one of the more important Chinese phrases in my iPod Touch’s “Notes” application.



It would appear that someone has ported the excellent HanWang Chinese handwriting recognition engine to the iPhone. This software can also do English handwriting recognition, but that doesn’t work nearly as well as the Chinese recognition. Details on how to install and use the software can be found on Gizmodo.

I have this installed and living just fine side-by-side with a Chinese pinyin input method, and it’s very easy to switch between pinyin, handwriting recognition, and the standard English keyboard.

Technorati Tags: , , , , , , , ,

Here come the iPod Touch clones from China

Tuesday, April 1st, 2008
N1467180119 30024079 6986-1
An iPod Touch clone advertised on Facebook’s China network

Aesthetically, this clone of an Apple iPod Touch, advertised on Facebook’s China network, looks like the closest match yet, though its dimensions are not listed so it’d be tough to say for sure.

Other notable iPod Touch clones are the Optimus Touch, the Tsinghua Tongfang PMC-V560 (apparently only costs $52), the Portronics/Onda VX858, and the Meizu M7.

Of course, these are all just lookalikes, I’d expect they lack the features that make the iPod Touch so appealing –great multitouch interface, high resolution, robust Unix OS, great email application, great web browser, etc. But it’s amusing to me to watch the number of Chinese iPod Touch clones increase.

Technorati Tags: , ,

A less emotional take on the font rendering issue

Tuesday, February 12th, 2008
Because I was switching between Windows and OS X, and was trying to make the text on a web page look nice, I was a little riled up when I wrote my last post about Microsoft Windows XP’s technique of rendering fonts. Now that my mental dust has settled, I still think Windows goes about font rendering in an ass-backwards way, but I can better articulate why that is, and how I think they got there.

I think the Windows font rendering method is designed specifically to make each character as clear and sharp as possible. I think the engineers who designed Windows XP’s typography engine did a great job accomplishing this task. The trouble with engineering is that it’s possible to come up with a great answer to the wrong problem. In my opinion, that is what happened here. The real problem with text on a computer is not clarity or sharpness, but readability.

The challenge of rendering fonts well on low-resolution screens is that fonts are full of curves and thin lines that just don’t line up exactly with the screen’s coarse grid of individual pixels. OS X and Windows both use sub-pixel rendering, so portions of characters that don’t land exactly on a screen pixel are rendered in shades of gray to represent how much of that pixel is covered by the font 1. In order to make each character look as clear and sharp as possible, Windows alters the shape of characters to optimize the amount of each character that lands exactly on screen pixels and minimize the number of pixels that will be rendered as anything but black.

This definitely gives many characters a sharper look in Windows. Many instances of this can be noted in the images from my previous post, one obvious example is that Windows has taken the curved-top, bottom, left, and right edges of all lowercase ‘a’s and has straightened them so that they render as single and sharp lines of pixels at right-angles to one another. In comparison, the OS X rendering of the lowercase ‘a’s looks blurry and curvy.

But the trouble is, characters do not stand alone. Typographers for hundreds of years 2 have taken great pains to design fonts so that the shape of characters, placed next to one another, produces well shaped words and sentences optimized for ease of reading. A well-designed font leads the eye through words, and the shape of the characters and the spacing between letters is crucial. The Windows font rendering engine changes fonts so thoroughly in order to maximize contrast that it warps them into shapes that barely resemble the original font (again, see those lowercase ‘a’s as a good example of this), and it also shifts portions of the fonts left and right such that the width of characters and the space between characters varies inconsistently, not just within within a line of text but even within individual words (note that in the Windows rendering of the word ‘event’ in the example image, there is a lot of space between the characters ‘e’ ‘v’ ‘e’, but ‘e’ ‘n’ ‘t’ are closer to each other).

The Microsoft engineers I know are very smart people, and I know Microsoft does a ton of usability studies, so how could they get this one so wrong? I suspect the wrong questions were asked. Perhaps test subjects were asked to look at blocks of text and rate their clarity and sharpness, or were asked to look at blocks of text rendered using different methods and were asked to judge the appearance of the text. Although I think the OS X method of font rendering is superior for the criteria that matter, I do think that when placed side by side with a block of text rendered by Windows and asked which block has the greatest clarity, many people would say the text in Windows looks clearer. And of course it does, there’s less gray, and those subjects might also be used to the look of non-antialiased fonts or bitmap fonts (especially at the time Windows XP was in development).

But the more important question to ask would be, “Which font rendering method produces more readable blocks of text”. And the way to test the question would be to take two groups of people with good reading skills who do not frequently read text on a computer, have each group read a 20-page story rendered on each computing platform, and time them. I contend that the OS X group, regardless whether they rated the text as clear or unclear, would finish reading first 3. The reason being that OS X renders the fonts much more accurately, and since body fonts are carefully designed to be readable when typeset as words in paragraphs, the Windows tendency to mangle each character out of shape and out of harmony with its surrounding characters in order to maximize the clarity of individual characters turns out to be counterproductive. And butt-ugly IMO.

Ask the wrong questions, and you often wind up with answers like “42” and font rendering engines like the one built into Windows XP.

  1. both OS’s also leverage the fact that LCD displays are high-resolution arrays of red, green, and blue pixels, and render not just levels of gray but colored pixels in order to use this additional resolution –Microsoft calls this technology cleartype and OS X doesn’t give it a name ↩︎
  2. thousands actually, we still use fonts such as “Trajan”, based on Roman typography ↩︎
  3. and would probably suffer from less eyestrain, but that wouldn’t be as easy a thing to test objectively ↩︎

Over 90% of computers render fonts terribly

Friday, February 8th, 2008
I’m building a web page right now, and am testing it on a number of web browsers on a few different computing platforms. After staring at type on computer screens for a while, I have reached the conclusion that font rendering on over 90% of computers out there is incredibly bad. Here’s an example:

The Children Of Huang Shi - Synopsis-2
Exhibit A: a scan of a magazine article

The Children Of Huang Shi - Synopsis - Microsoft Internet Explorer — Winxp English
Exhibit B: The same text typed in and rendered on a computer running Windows XP

Which do you prefer? Be honest now. OK, so maybe it’s not fair to compare the rendering of a font on a computer screen with a scan of actual printed type. And maybe it’s wrong to pick on Windows without offering up an example of how text is rendered in Mac OS X or Linux. Surely all computers have huge limitations when rendering the printed word. But actually I’m being more unfair than that. Please take another look at those examples, compare them, then click here to reveal the real captions for the above images to find out where they actually originated. (If you prefer the deceptive captions, you can reload ’em).

To my eyes, OS X’s type rendering looks much like a scan of a newspaper or book. The weighting of characters is nice and even, and the text is pleasing to the eye and easy to read. Even if you didn’t buy the pretense of the original caption, it’s at least slightly possible to pass the OS X rendering off as something that was actually typeset and printed at high resolution.

Windows XP’s font rendering is an indefensible monstrosity. 2 It pains me to think that over 90% of the personal computers in the world, in the year 2008, display text in this manner 3. The characters in the Windows sample have very uneven weighting, with all corners and pointy details stabbing my eye with a couple pixels of absolute blackness while curves are rendered an anemic gray and straight lines are often reduced down to a single pixel in width (This problem jumps out at me in almost every letter, but can be seen more clearly in the sharp “J” next to the soft “o” in Jonathan, in the oddly sharp lower left corner of the lower-case “a”, and in the weird unevenness of the italics and the numerals). The best that can be said for the kerning is that it is bizarre; Letters are either smashed too close together or separated by chasms, within a single word. Italics are so awful in so many ways that I’m thinking of redesigning my pages to avoid using them altogether –Windows users have to suffer enough with regular text. Some characters look strangely condensed.

A few details to note: compare Windows’s rendering of the word “sweeping” to its rendering of the word “events” (why so much space between the instances of “e” and “v”?), then compare Windows’s renderings of the word “events”, “Rhys”, “1930’s”, “Children” to the OS X versions. And why are the OS X and Windows renderings of these lines so different in their relative lengths?

I’m sure there are compelling-sounding engineering reasons behind Microsoft’s assault on typography-loving eyes everywhere, but the proof is in the pudding. Both of these samples are of the same font, Georgia (designed specifically for Microsoft), and it is either Alanis-ironic or just plain sad that OS X kicks Windows’s ass so soundly at rendering Microsoft’s own. Another few hours of flipping between platforms and I’ll be compelled to file a shareholder resolution to push Microsoft to fix their font render engine, undergo a few sessions of maoist self-criticism, and make a public apology.

Windows, heal thyself, particularly thy crap-ass rendering of typography

  1. If only there were a recognized acronym for “rolling on the floor hemorrhaging out my eyeballs” ↩︎
  2. And I’m being charitable. If you are even entertaining for a moment the idea of defending the crappy font engine built into Windows XP, please first revisit the sample images above and start building up your reserves of purest denial. ↩︎
  3. actually, it’s worse than that, since most Windows users don’t know to enable cleartype ↩︎