iPhone 4 Summary

Okay, so the WWDC keynote was this morning … I briefly considered a 3am wake up to follow the liveblogs, but sanity prevailed and I settled for waking up a bit early and reviewing the blogs. The keynote didn’t really cover anything that hadn’t made it out into the world already. The new iPhone, simply “iPhone 4″, was announced. The iPhone OS has been renamed iOS (I wonder what Cisco thinks about that). Guitar Hero and Farmville now available on the iPhone (wut?). I got a little too excited about a fairly simple change to an iPad app … iBooks will have PDF support, including annotations. Okay, I know it’s sad, let’s move on to the only real announcement.

iPhone 4 – quick stats

  • Same storage options – 16/32GB
  • Front facing camera (video calls iPhone 4 to iPhone 4 only, and WiFi only until Apple works with carriers)
  • Hi-res display, 960×640-pixel resolution at 326 ppi
  • 5MP camera, LED flash and 720p video recording
  • Gyroscope for more motion control
  • Quad-band 3G (includes 900MHz band, which will help Optus!)
  • 802.11n wireless
  • Steel band around the side is the antenna
  • MicroSIM format (saw that coming)

Really, from a consumer standpoint, there’s really not a huge amount here that isn’t coming to the 3GS once iOS4 is released. The new backgrounds and apps (iBooks for iPhone) will be available for the 3GS, the app folders and multitasking will also be brought down to 3GS.

Some of the technology in this is pretty cool though. I really wanna see the screen. The idea of a pixel density so high you can’t actually distinguish pixels appeals to me.

Bonfire photoThe ability to record 720p video is a very nice addition, as is the 5MP bump on the camera, but it doesn’t really mean much if the sensors don’t improve at low light. The 3GS takes perfectly acceptable photos … in bright light. But in dim or low light, like trying to photograph bonfire day, the camera doesn’t hold up. So I don’t really care about the megapixels as much as I want the sensor to improve.

The most interesting thing is the antenna structure. The case for iPhone 4 is front and back plates, with a steel band running around the sides. The left side and part of the top band is the Bluetooth/WiFi/GPS antenna, and the rest is the GSM/UMTS antenna. Very cool.

The rest is just eye candy which, while impressive, is not having the same effect on me that it might normally given the money I just spent on another Apple product.

Lastly – release date. June 21 for iOS4 on iPhone/iPod touch. June 25 for iPhone 4 in the US/UK/France/Germany/Japan. “July” for Australia/NZ and 16 other countries.

Google Reader apps for iPhone

iPhone Google Reader

Decided to have a look at Google Reader for iPhone apps today. First just a note about the web interface: http://www.google.com/reader/i/ It is very good! Obviously has (almost) all the features of the full web version, and is continually being developed as Google learns new tricks with their “mobile touch” interfaces. It is missing the “Send to” menu, and is obviously only usable when online, but it’s certainly very usable.

On the iPhone I’d been using NetNewsWire, but found that because I really didn’t like it, I was rarely using it and rarely checking Google Reader while mobile, since it was not a pleasant experience. I downloaded three apps to test out: Byline, Reeder and Mobile RSS.
The table shows the major features of these apps, and I’ve just got a few bullet points on each:
MobileRSS – free (ad supported) or $3.99
+ Most features of all four apps.
+ Whole folder or individual feed views
- No option to view feeds with no new items (exception: items read via the app go to “Read” section)
- Scrolling totally unresponsive when syncing
- Preferences occasionally laggy
Special mention for being able to move feeds between tags/folders and being able to unsubscribe.
Byline – $4.99
+ Option to Cache only on wifi connection
+ Toggle between timeline or split by feed
+ Read / Unread toggle by swiping on list (but not publicised or available inside an item. Would be nice to open item, then mark unread from within the item and move on)
+ Toggle between chronological or feed sorting in folder view
+ Good granular caching options (images and/or web pages, for starred items, items with notes and “new” items)
+ Keeping read tags/folders toggled in preferences but slightly annoying to toggle since it’s in Settings.app
- Read folders clog up view, needs sort by unread option while read folders are visible.
- No individual feed view
- Caching is horrendously slow
Reeder – $2.49
+ Best looking interface, although slightly odd animations between states.
+ Simple toggle between Starred / Unread / All at top level.
+ Toggle between chronological or feed sorting in folder view
+ Starred / Unread / Read toggle in individual feed view
+ Best interface for sharing through different services
- Interface is not the most intuitive. Fine once you learn it, but bit of a learning curve. The online help page is required.
- Offline storage doesn’t cache images, or the original website sources. Only caches unread articles.
NetNewsWire – free (ad supported) or $5.99
+ Collapsible folder / feed interface is good
+ “Next unread” button
+ Toggle individual feeds on/off
- Feature poor
- “Works with” Google Reader, rather than being designed for it.
Typically, while going through all these apps today I found out that MobileRSS and Reeder both have updates pending with Apple, and Byline’s current price is a special “anticipating 3.0, a major update.” So I’ll doubtless be re-visiting all of these apps in the near future. Most importantly, MobileRSS and Reeder will both be getting my essential “keep unread” feature, which at the moment is the one big advantage Byline has over me. If I had to chose one app at the moment, I’d probably chose MobileRSS, but as soon as Reeder gets the “keep unread” option, it will probably become my app of choice, despite the extra features of Mobile RSS.

Posted via email from Computer Monkey

Annoying Apple Paternalism

If only paternalism, or nanny state, started with an ‘a’ …

iStat on my iPhone

I draw your attention to the red box … I haven’t had to restart my iPhone in almost a month. I consider uptime to be a badge of honour, especially on a device where “restart it” is often treated as the final step of every complex app install.

I now draw your attention to the green box. This is where, until recently, a “free memory” button was present, which is what I attribute to the lack of troubles I have had. Freeing up the RAM in the iPhone is the main reason, from what I can see, that developers and users alike say you should restart your iPhone after app installs.

A couple of days ago, Apple decided to spread the word to developers that this functionality was not approved – they removed a couple of apps from the store, and told the developers of my app of choice, iStat, that they needed to remove the functionality in order for their update to be approved. From what I have read, the way these apps “free” the memory is by requesting a large amount of ram, forcing the iPhone to dump the contents of “inactive” ram, and killing the background processes that Apple allows (usually Safari, iPod and Mail). In some ways, I can understand why Apple would want this removed – it’s a bit of a hack, a “creative use of programming techniques” if you will. But the obvious two questions are (a) why now, and (b) why isn’t there an Apple approved way of doing this?

Freeing up the RAM is the best troubleshooting method on the iPhone. On the 3GS, it’s a convenience that can make things run a bit smoother. On the 3G, it’s basically a necessity for smooth operation of the 3.0 OS. Maybe it’s not the best fit with the “Apple Experience”, but when it doesn’t “just work”, it’s time to either put in a solution or allow the solution that’s already out there.

Oh, and as is likely to happen when you only have 40 staff doing the reviewing (and search&destroy on verboten apps), something like Memory Status is sure to slip through … Not as elegant as iStat, but does the job.

iPhone 3G … or MMS – not for you!

Okay, this one’s a little long, so perhaps grab yourself a drink and some popcorn before settling in. And as forewarned, there’s a bit of background to this story …

I’m (currently) an unapologetic Apple fanboi. This has escalated to the point where I am now actually working (IT Support) in an environment that is very heavily mac biased. I do all my home, travel and work computing on Apple hardware, even if I do occasionally boot it up into Windows to do specific tasks. This hasn’t always been the case – I started my computing life on an 8086, progressed through 286 and 386, then used several flavours of Apple / Macintosh during primary school (Where on the Apple ][e is Carmen Sandiego?) and then around the System 7 vs Windows 95 days I shifted, fairly solidly to the Windows camp. I became one of those horrible Windows people, and ranted against macs for a good few years. At about OS X 10.2 I started looking at the mac again, now older, somewhat wiser and much more appreciative of things like UNIX (okay, BSD) core underpinnings and so on. And I was starting to see the flaws in the Windows world. Over the last few years, as XP has continued to be what it was 6 years ago, and Vista has not proved to be the magic pill someone, somewhere was probably hoping it would be, I’ve become a fairly solid believer in the OS X camp.

Still, I try not to be a zealot about it to other people, and I recognise the flaws in OS X and the positives in Win XP (and even Vista). But there’s no doubt about my favoured choice, and there’s little doubt that I’m willing to cut Apple a fair bit of leeway with products and try them out even if they might not be quite what the Reality Distortion Field might suggest.

With that in mind, I was front of the queue at my local Optus store for the iPhone 3G when it was released here in Australia. I knew what I was getting myself into. I was sacrificing tactile feedback, I was getting a fairly ordinary camera, and I was losing MMS. I have an iPod Touch, so I understood about the keyboard, and I knew that wasn’t an issue. Assessing my usage of the camera and MMS on my Nokia E65, I was certain I could do without those 5-6 messages per year, especially since I could freely email things to people who were usually close enough to email access anyway.

Having now had the iPhone for a few weeks, I can safely say that although my typing has been far from perfect, the keyboard is a non-issue. It has reduced my walking emails and messages, which is not really the end of the world, but if I can spare my eyes, there’s no problem with the typing. There is occasionally a bit of lag on the keyboard, and it’s annoying, but it’s not much different to my Blackberry, where I could sometimes type out a full message only to have the BB not recognise any of the (physical) keystrokes anyway.

The shitty camera quality does and doesn’t annoy me. Photo-wise, don’t care. I mean, it would be nice if I could get slightly better photos of my friends doing stupid things indoors to make contact photos, but it’s hardly a big issue. I have a real camera for taking real photos. But on the flip side, who includes a 2MP camera these days? Other phones in this price bracket are pushing 5MP cameras with “brand name” lenses. Okay, sure, they have a sensor the size of a pinhead, but compared to the iPhone camera, they’re pretty impressive. Apple has always cultivated a reputation as pushing technology and taking things that have typically been done badly and drastically improving functionality and marketability. So including a sub-par camera on their “Jesus phone” really seems out of place. Not including the (software) ability to record video seems odd as well, although battery life / processor power arguments can at least balance upright precariously, if not actually stand up to much scrutiny. The fact that jailbroken iPhones can do (crap quality) video without pain begs an answer to why it was left out.

So anyway … shopping around for something to protect my precious shiny from scratches, and I find a silicon case that doesn’t look too horrid. Normally I’m very much a fan of either “invisible” protectors, or a sleeve of some sort that protects in-pocket, but keeps the look of the device clean. But this case didn’t look too bad, and looked very easy to slip on/off as vanity dictated. I like to have my impulses at least told to someone else before I act on them, and it would’ve been so great to shoot off an MMS to my other half, who was not in a position to check her email or wander down to the Apple Store. Fitting, that my first iPhone MMS frustration was in an Apple Store, shopping for my iPhone.

When you read the spec sheet, really, who cares about MMS? It’s not that great, it’s typically overpriced on the networks, and the email argument does actually hold a lot of water, at least in my situation. But then there are those few times when MMS is exactly what you want, and you start to think “Hang on, what reasoning is there for NOT including a standard mobile phone feature?”

Think of the programming involved … there’s already the functionality for SMS, and the functionality for email. MMS would seem to be a no-brainer. Okay, we’ve struck out programming. How about appeasing the mobile networks, something Apple would’ve had to do in some instances, since a mobile phone without network support isn’t that useful. But networks, in a pure price-per-byte argument, are charging far, far more for an MMS message, since they are often capped at 100kb or thereabouts. So network-appeasement seems rather unlikely too.

It’s incredibly implausible that this was an “accidental” omission, since I don’t believe that any company developing a mobile could get to version 2.0 of their mobile OS and not have come across the feature. Which means it was deliberate. Which is frustrating. I am still an Apple fanboi, but this is totally an example of the decisions that they make that seem to serve no basis in consumer reality, but also, and this is the worst bit, don’t seem to even have any “pushing the industry” reasoning driving it.