The one major complaint I’ve had with Aptana on OS X is that it’s super-slow. I’m running a 1.67GHz Powerbook w/ 2GB RAM and it still brings my system to a screeching hault. I’ve been digging around trying to allocate more memory to the Java VM and finally got it working today. This is something I’ve done in the past on Windows, but wasn’t sure how to approach this on my Mac. I read in the forums that the VM arguments are maintained in Aptana.ini and I searched for a good thirty minutes trying to find this file. After right-clicking Aptana.app a few times I finally stumbled across the Show Package Contents option:

This was the magic trick. Within this package (folder) you’ll need to browse to Contents/MacOS/Aptana.ini. Open it up and specify the appropriate memory values. On my system I’m currently running:

-Xms256m
-Xmx768m

It appears to be running smoother although not as well as I’d like. I guess at some point I’ll need to go MacBook, but I can live with this for now. Hopefully this tip will save somebody a few minutes of frustration.

Well it was pretty much inevitable. I kept delaying the purchase of my iPhone in hopes of some sort of GPS announcement. The reality is that we’ll probably have to wait until the next version for GPS support. I gave up the incredible Blackberry 8800, with built-in GPS, for the iPhone this weekend. The main reason I switched is that we’re planning some interesting developments for the iPhone at Ublip. The mobile OS road to get to the iPhone has been an interesting one and basically looks like: Symbian > Windows Mobile > RIM > OS X.

The main reason for this post is to discuss the HTTP_USER_AGENT string for the iPhone. For my device it looks like:

Mozilla/5.0 (iPhone; U; CPU like Mac OS X; en) AppleWebKit/420+ (KHTML, like Gecko) Version/3.0 Mobile/1C28 Safari/419.3

I’ve seen several companies implement a completely different URL for the iPhone version of their application. Yet some companies such as 37signals detect the iPhone and display optimized content. A perfect example is their tadalist product. If you have an iPhone check it out and you’ll see what I mean. Although the iPhone does an INCREDIBLE job of rendering content as you would see it in desktop Safari, the user experience is much better when optimizing for the device (big buttons, fonts, screen transitions, etc).

If you’d like to see the user agent for your iPhone then simply browse to the following page on the Ublip site:

http://iphone.ublip.com/user_agent.php

If you’re doing some sort of detection and determining what content to display (ie indexOf(“iPhone”)) beware that the iPod touch may have a different user agent string, yet still runs mobile Safari. I plan on doing some follow up posts on server-side device detection using Ruby on Rails.