Other cool applications included: AppMarks, PickleView, Fluther, The Pool, itunes Remote-o-Matic, Tilt and moPhaic (read about them here). The coolest hack from the event was called the Fluid Navigation Hack as described by Andrew:

Have you ever heard of Firebug? It’s the absolute best Firefox extension for developers. If you are building applications for the iPhone, it might be your greatest debugging tool. But Firebug for the iPhone, iBug.js, is not my favorite app. It’s Joe’s liguid navigation hack. Almost 25% of all apps presented at iPhoneDevCamp used it. Hewitt’s Javascript and CSS package mirror the iPhone’s iPod application, and use a fluid navigation scheme that will become commonplace to any iPhone user. This is my favorite app because so many iPhone hackers used it this weekend as a backbone for their application. This framework will work nicely for future iPhone development because it’s lightweight, elegant, and comfortable for anyone trying to navigate their Apple smart phone. The source code is available here. This would be my starting point if I were to develop an iPhone app.

="http://farm2.static.flickr.com/1207/747968579_427ca401b4_s.jpg" alt="DSC_0010.JPG" height="75" width="75" /> idth="75" /> "75" />

We have successfully written a tool named iPhoneInterface allowing for some basic manipulation of things on the phone, and are releasing it tonight. We are including source code so you can understand the techniques we have used so far. We will be expanding the functionality of this tool significantly tomorrow. The best news is that we have prototype code that allows the ability to:

• Run any desired application already residing on the phone.
• Control what processes run on the phone (currently implementation is very hackish)
• Move files around on the phone
• Enable viewing of verbose information during the restore process
• Activate the phone without iTunes and without a token

Note: Not all of the features listed above are necessarily included in tonight’s initial release.

We are continuing significant work on this tool and will probably have similarly worthwhile updates tomorrow.

• 95% of buyers in NYC and SFO bought the 8GB model (versus the 4GB)
• 50% of buyers were new customers for AT&T (Verizon’s CEO is kicking himself)

If you can engage the iPhone community it means you can have access to 500,000 early adopters.  How?  Start building tools specific to the needs of the ‘instant community’.  How?  Hire guys like us or come to the iPhoneDevCamp in San Francisco this week.

• Poking around the DOM, I don’t see any special objects, with the possible exception of window.offscreenBuffering (set to true).
• Bookmarklets work, although you have to go through the bookmarks menu to get to them.
• Safari crashes are handled gracefully – the main screen fades back in, and you can jump right back into Safari. It will then load page you were visiting when it crashed.
• Drag and drop, and other behaviors based on picking up mousemove events, don’t work. CSS-based element drag and drop doesn’t work either. Dragging one finger around the iPhone’s version of Safari causes the window to scroll, and that’s it. I assume that scroll events do work. I’m sure somebody is already working on a version of drag and drop based on window scrolling.
• For documents with no width set, the iPhone uses a default width of 980px.
• You do not get “mousedown” when you touch the screen. You get “mousedown” and “mouseup” at the same time when you release your finger. The “mousemove” event does not seem to fire at all. There is no way to handle double-clicking because that is the action for zooming, and calling event.preventDefault() doesn’t seem to override that.

iPhone Developers Camp is an upcoming gathering, inspired by BarCamp, SuperHappyDevHouse, and MacHack, to develop web-based applications and optimize web sites for iPhone. It is a non-commercial event, organized by volunteers, with attendance free to all. By the completion of the weekend event, a number of iPhone-ready web applications and web sites will be launched to the public. The event will be held in California, and out-of-town guests are welcome.

Attendees will include web designers, developers, testers, and iPhone owners, all working together over the weekend to improve the web experience for iPhone. Development projects will include both solo and team efforts. While some attendees will wish to work solo during the event, we encourage attendees to team up, based on expertise, to work in ad-hoc project development teams. All attendees should be prepared to work on a development project during the event. You do not need to own an iPhone to attend (although, a large number of iPhones at the event will make the development and testing process much easier).

Attendees will be able to:

• Create new web applications for iPhone.
• Optimize existing web applications for iPhone.
• Migrate Dashboard Widgets to web-based widgets for iPhone.
• Test and optimize web sites for iPhone.

Here’s the story. A trustworthy source supplied us with an actual internal Apple email that went out to thousands of Apple employees earlier today (published after the break). The fact that this was an email sent within Apple’s internal email system to its employees is not in question. Let us reiterate: this was an ACTUAL email distributed within Apple’s internal email system to Apple employees. As it turns out, the internal memo Apple employees received was actually retracted by Apple shortly after it was sent out. (Also published after the break.) We received confirmation from Apple PR that this initial email sent out to Apple employees was incorrect, and they let us know that the iPhone and Leopard are both still on track, and should meet their expected launch timeframes. Presumably Apple is now on the hunt for whomever was able to spoof its internal email system.

This is a great example of why checking your sources is important. Just receiving a forwarded email is not the best way to ‘fact check’ your story. Get on the phone and try to get the party to confirm. If you can’t just say, ‘this story is unconfirmed, but…’

Update: It matters even more when the stakes are this high and you are dealing with a publicly traded company.  Turns out stock manipulators may have been at work as Paul explains:

This is a bigger deal than a blog getting a story wrong. Why? Because this was almost certainly done for market manipulation, with someone — Russian hackers again? — inserting this into the Apple network, knowing it would get out and hook someone, while allowing them to trade against the news.

Paul Kedrosky, who I sent an iPod to last year when he told me he didn’t have one, points out that the Sony Walkman sold 60,000,000 units between 1979 and 1992.  I suspect that the platform nature of the iPod will give it a stickiness that Sony could only dream of.  The iPod has transcended its need for support from “teen pop culture.”  Yes, eventually iPod sales will stop growing – they have declined over the past two quarters, but just take a look at iTunes Music Store sales and you will get understand the concept of the “platform.”