Last week I’ve been in Rome for the iPhone Tech Talks, Apple’s so-called worldwide event promoting iPhone development. Apparently the moto “Stay where you are. We’re coming to you.” didn’t apply to Greece, so I decided to fly to Rome and attend the one-day seminar. In the beginning of the day, we were informed that the event was considered to be confidential and we shouldn’t blog/tweet/facebook about it, but I think it’s ok to express my impressions about the event as well as my (probably useless) comments about my trip.
Roaming with the iPhone
Apart from the original frustration of not being able to connect to any cellular network (because for some stupid reason my carried switched roaming off when I upgraded my plan), the iPhone’s done well roaming into a foreign country. I don’t know if italian 3G networks are slow or if it was the roaming, but even on 3G everything was pretty slow.
Getting to the event
When I walked to the La Sapienza University, I thought I’d spot the familiar Apple logo on a banner or something, directing me to the place where the event was held, but as much as I looked around, I saw no apples at all. And almost everyone I asked was either unaware of it, didn’t speak english or would rather not talk to a stranger. I spent about 15 minutes asking and going from one place to the other, until I finally found it. They had a banner, but it was up on a balcony at some place.
A few minutes before the first session began
Event sessions
The day consisted of many sessions, some of which were more informative than the others. I’d rather like it if all sessions were tech talk, but hey, it’s their promotional event. Information on the actual technical stuff was coming fast enough so you can keep up and yet include as much as possible. Some people were taking notes but I think it wasn’t really useful to do so. I wouldn’t consider most of the talk being confidential, since in essence it’s all written down in the Apple documentation about the iPhone, but oh well.
One of the reasons I wanted to attend the event was to get to ask some questions to an Apple evangelist, but I wasn’t that lucky. The only chance to ask a question was to find the one Apple guy during the breaks, but that means fighting your way through the crowds that engulfed him instantly the minute the sessions ended. And all this talk between the developers and the Apple guy was in italian, so it was useless to me. Well, at least I had time to visit the buffet, but hey- don’t forget it was a free event.
It was funny that I was the only non-italian person attending, so the host had to speak in english throughout the sessions even though he was italian as well. Sorry guys!
Some interesting notes
Being there among all those italian developers, I quickly came to notice some stuff (most of which I Tweeted about anyway). First, I thought everyone would have an iPhone, but that was not the case. However, almost all laptops were Macs, I didn’t spot a PC in there. New MacBooks could be seen, but old aluminum Pro’s, plastic MacBooks and even my 12″ PowerBook G4 diversified the gamut.
When the audience was asked, quite an impressive amount of people raised hands about using Xcode and Objective-C. Less people were actually developing an iPhone app, and about a dozen and half already had an app deployed on the app store. I wonder how many of the rest of the developers are actually going to build an app, since it was a free event and it was obvious that some people attended maybe out of curiosity only.
Evaluation time
So was it worth it? Well, if they come to your city, it’s definitely worth it to go if you’re interested in developing for the iPhone. But flying abroad just to attend the event (at least the European schedules) wasn’t something I’d recommend, since most of the stuff is readily available in the documentation. The event was probably a good chance to hook up with other developers (an italian start-up was looking for developers there) and often great start-ups form out of such meetings. So if you’re an upcoming developer that haven’t dug deep yet into iPhone development, you should definitely go since it puts you into a mood and briefs you about the technical difficulties involved (i.e. memory management etc.)
Night shot of the Pantheon using the iPhone's camera
As for me, I tried to increase the value of my trip to Rome to make it par with the money I’ve spent, so I took a nice walk the evening after the event, re-visiting most major sites in the historic center. Piazza Di Spagna, the Pantheon, Piazza Navona, Campo Di Fiori, Fontana Di Trevi and other small piazzas here and there, a taste of italian pizza and buying souvenirs and gifts for my wife made that evening worth the trip! And since it’s all about the iPhone, here’s a (slightly enhanced) night shot of the Pantheon using the iPhone’s built-in camera.
There are lots of uses for an iPhone and it’s good to have one in your car, especially in the case of Trapster, an iPhone app that aims to alert you about speed cameras and other gear out there in the streets that can get you fined. It’s a brilliant idea, but let’s see if this app does what’s promised and whether it performs that task well enough.
How does it work?
First of all, even though the app’s description doesn’t clearly mention it, the app alerts drivers based on a user-populated database; the iPhone does not have the necessary equipment to detect speed cams! What that means is that you get alerts only for those traps that other people have reported, and that data may be inaccurate or even completely false. There is though a means of rating each trap and the app calculates a confidence level for each one, but still this is all based on people’s good will.
One case in which the user-centric database can be of no use is that of systematically submitted false alarms. Some anti-trap-alerting group, for example, could massively submit numerous traps that are not real, thus making the app useless for a driver that would constantly get alarms for cameras that are not there. But assuming that there are no such groups (yet) and the authorities would never come up with this, false alarms shouldn’t be a big issue, although some of them surely exist.
Jeez, where’s that camera?
The main problem with Trapster is not the data, but the way it reports traps to the user, who in this case is, the car’s driver. This is where Trapster fails to deliver in a practical way, for many reasons. First of all, the reports are using a synthesized voice that not only sounds rather ridiculous, but is hard to notice at times over the noise in the car. Also, don’t hope that you can scroll the map as in the Maps app -no, no! The map stays fixed and you have to hit a “center” button to re-position your car in the map.
But most importantly, the problem is that the algorithm for trap detection is based purely on proximity and doesn’t account for the car’s direction, thus alerting drivers for traps that are monitoring the cars that are going to the opposite direction! This can be rather frustrating if you’re driving in quarters that you’re not familiar with (but that’s the point of this app, if you already know by heart where the traps are, it’s of no use, right?) since you’ll be alerted for traps that aren’t meant for you, but you’ll still be slowing down and wondering where in Earth that trap is supposed to be.
Another problematic area that can be improved is when a user submits a trap, since the map problem mentioned above doesn’t make this too easy for a driving person. I think it would be a good idea to let users log in to the site when they get to their computers and fine-tune the data they entered in a hurry while driving, or even add some more details about the trap.
Bottom line
Trapster is a nice idea that is poorly implemented, at the moment. However, it can still be quite handy and save your from a speed ticket or two, so it’s good to have the app running in your iPhone while driving in a highway. Knowing it’s problems and limitations will reduce your frustration, and keep in mind that this app uses data generated by people like YOU - so don’t forget to submit the traps you see, or rate the existing ones!
Wishlist
Here’s a list of a few ideas that would make this app much better:
Detection algorithm should account for the vehicle’s course (e.g. create a vector simulating the vehicle’s track and associate that with a user-submitted trap, then check against this before alerting users).
Use a clear and loud human-recorded voice for reporting traps.
Calculate the vehicle’s speed and use audio cues to report how close the vehicle is to the trap (i.e. a driver’s that’s moving too fast should be notified earlier than one who’s barely above the speed limit).
When such audio cues cease, drivers would also be informed that they have passed by the trap and are no longer in it’s range.
Fix the interface, please (draggable map, zooming with gestures, auto-following the vehicle - you know, like the Maps app!).
Allow users to refine trap data through the website.
Recently, I’ve been arguing with a trio of ambitious entrepreneurs whether a touch interface is coming to Apple products and how this could possibly affect iPhone app development. My point was that, since Apple has already filed a patent for a touch-screen mac and had shown strong interest on multi-touch user interfaces (see iPhone), it won’t be long until we see new touch-screen Macs.
Today, circulating the news is a video demonstrating Mac OS X Leopard running on a Gigabyte M912X (video follows), a small PC laptop with a touch-screen. The video is hosted on YouTube and has already been viewed more than 12k times since it was uploaded two days ago. Reading the comments, one can see that many people would like to do the same thing with their tablet PCs, which strengthens the idea that a touch-screen Mac (or a tablet Mac) would be quite popular.
If Apple officially produces touch-screen Macs, then I can safely bet that the UI (User Interface) would be enhanced to support multi-touch gestures etc, as well as other features that were missing in the OS since it was hard to implement without a touch interface. Combining this with the recent incidents of Apple rejecting iPhone apps for duplicating built-in functionality, my point was that building an iPhone app with features resembling those of a future Mac OS release supporting touch, could possibly be rejected - if Apple has already implemented such features in the OS. And since Apple is a company that knows well how to keep secrets (see the move to Intel processors) it wouldn’t be a surprise if we suddenly see Jobs demonstrating a tablet Mac on stage, anytime soon.
