Coovents.com shows you which happy hours are going on today and shows you which ones are going on now. With one glance you can see happy hours in your hood! You can also send a text message to Coovents and we’ll send you happy hours to your phone! Bar hopping will never be the same.

Now, even if you aren’t interested in happy hours, you might be interested to know that this application was writtten using the PhoneGap Framework… in other words, while it may look like a “native” iPhone App, it is actually developed in HTML, CSS and AJAX, using Mobile Safari enhancements such as Scalable Vector Graphics, WebKit Transitions and HTML 5 Database support. The client app on the iPhone interfaces with Coovents via a JSON query interface, with all the rendering, requests and other magic shenanigans in the user interface happening via JQuery.

I’ve blogged about PhoneGap many times before here, but I have to say this is the farthest I’ve taken it both functionally and visually… perhaps it is because the app (happy hours) is an enjoyable problem to solve!

Watch the video below to see the app in action…

You can also checkout the Flickr Screenshot Set of the app…

Again, if you are interested in being a beta tester, please sign up here. Otherwise, the app will be in the iTunes store very soon!

In short, say its “Phonegap-based” means that this app was built using HTML, CSS and Javascript, and then wrapped up in a native binary iPhone application. I’ve blogged about this before, when I showed how to turn a blog into a native iPhone app in 10 steps.

The full server app is still under development (server queries are VERY slow), but in short, it is a “people” search engine, for finding various profiles of someone online based on searching for their name. I, through my work with Oliver+Coady, was hired to build the iPhone App and get it into the App Store ASAP. PhoneGap was the best solution to get the job done quickly.

Development time was < 1 week... .it took longer to get the app into the store than it did to build it! The app uses JQuery for server interaction and the UI was built in Dashcode.

Another quick interesting thing about this app, is that it uses HTML 5 Database to persist search results and Safari/Webkit extensions for CSS translation and transitions.

Both working pretty well, though the translations are about 4x faster on the iPhone Simulator than on my iPod Touch.

Get Skadoo for your iPhone today!

Gee – I wish they told me that to begin with! Still I have to now re-release my application, simply to put it in the correct category. Frustrating, but not awful.

Earlier today, I was gleefully attempting to show Dave Oliver the hilarious comment thread for the blog app I recently released for Android. I pulled up the Market app on my T-Mobile G1 and searched for “Nathan”, expecting to see “Nathan’s Blog App” in the results…. but, it wasn’t there. Confusion set in for a bit, followed by disbelief that the app had been removed from the store.

This was confirmed when I received this “friendly” automated note below from the Android Market support team:

noreply-android-market@google.com
6:24 PM (5 hours ago)

This is a notification that the application Nathan’s Blog App Demo (ID: -8575230491255129376) has been removed from Android Market due to a violation of the Developer Content Policy. Please review the Content Policies and Business and Program Policies before you create or upload additional applications.

For more information, or to contact us, please visit the Android Market Help Center.

Thanks,
The Android Market Team

<- This is how I feel right now…
like a sad little lost robot.

Now if you look through the policy links above, and then read about what my app does, you’ll see that, as far as I can tell, I am in no way breaking the rules.

Your application shouldn’t contain content that displays (via text, images, video or other media) or links to:

* illegal content
* invasions of personal privacy or violations of the right of publicity
* content that interferes with the functioning of any services of other parties
* promotions of hate or incitement of violence
* violations of intellectual property rights, including patent, copyright (see DMCA policy), trademark, trade secret, or other proprietary right of any party
* any material not suitable for persons under 18
* pornography, obscenity, nudity or sexual activity

Also, make sure your products don’t:

* harm user devices or personal data.
* create unpredictable network usage that has an adverse impact on a user’s service charges or a Authorized Carrier’s network.
* knowingly violate an Authorized Carrier’s terms of service for allowed usage

Now, I’ll admit my app is a bit pointless, some may mistake it as shameless self-promotion, but in truth, it was meant as a proof of concept for gluing together the awesome Phonegap SDK (a mobile web appstack enabler) with WordPress and a mobile-friendly template. This allows my CMS-based website (be it blog or not) to have a “native” presence on a device, one click launch capability AND allow for integration with native services like GPS, media capture, accelerometer and more. Pretty cool, eh?

I guess apparently not. I ask you out there to tell me why *you* think my app was removed. Perhaps I will hear back from Google… not sure. Their “Contact Us” capability was pretty basic and I had to dig for it… considering the notification email came from a “no-reply” address, I am not very hopeful. I am going to post this blog link to the appropriate developer lists, as well, and I look forward to gaining some insight into what I may have done wrong, though I honestly believe I am not at fault here.

Regardless, isn’t Android supposed to the more “open” platform? I thought app censorship was the domain of Apple?! Is there some sort of review process that happens after an app is released? Why not do this before the app even gets into the market… that way at least you know where you stand before you tell the world the app is up. Maybe the Apple way isn’t so bad after all…

Anyhow, for one of the biggest cheerleaders of Android out there, this is not a fun moment.

However, the reason SVG should matter to iPhone developers is that, since there is no Flash or Java support, it is difficult to achieve rich, dynamically rendered interfaces – think charts, clocks, gauges and other visualizations, through CSS alone.

The application I am developing required a working classic clock with semi-transparent wedges overlaid on top of it showing different upcoming events. The implementation is nearly done, so you will be able to see it in action soon, but for now here’s a screenshot:

And for those of you looking to do some rad geo-hacking and break out of the bonds of Google, how about moving towards OpenLayers based SVG maps? There are some links to great SVG map demos at the end of this article. Also check out James Fees GIS Blog for a whole thread on this topic.

Not sure if this works yet in WebKit on iPhone, but have you seen this cool demo of combining SVG with the new HTML video element? Perfect for the multitouch capability of the iPhone, no?

All in all, just food for thought, and an example of a great technology that might have finally found its niche!

Here are some great SVG demos, samples, tools that should all will work in the iPhone Safari browser… and hopefully the Android version of WebKit, as well!

• Smooth Analog Clock: http://www.browserland.org/scripts/svgclock/
• Bar Graphic Tutorial from IBM: http://www.ibm.com/developerworks/xml/library/x-svggrph/
• Slides from SVG Talk in 2002: http://luxor-xul.sourceforge.net/talk/jug-nov-2002/slides.html
• ChartSVG open-source package: http://www.hardcoded.net/chartsvg/
• ESRI SVG Map View: http://apps.arcwebservices.com/svgviewer/map.html
• More SVG Map Apps: http://www.carto.net/

1) Download and install the iPhone Development SDK: http://developer.apple.com/iphone/

2) Launch the Dashcode application and select the “RSS” template option.

3) Edit the RSS parameters, setting the feed URL to your blog feed (or any feed you’d like!)

4) Customize the look and feel of the blog display using the type of fancy visual editor… you can change the entire color scheme, fonts, spacing and more.

5) Press play to preview and test your blog app in the iPhone Simulator

6) Export your dashcode project to disk and/or publish it to a public web server. Since my blog lives at OpenIdeals.com, I placed my iPhone web app at http://openideals.com/iphone

7) Download the super sweet PhoneGap application framework via http://phonegap.com or just get the ZIP Archive directly
Open the archive, navigate to the “iPhone” folder and then run the “Glass.xcodeproj” xcode project (duh?) file. It should be the only “blue” file in the folder.

9) Find the “url.txt” file in the “Groups & Files” explorer. Change the url link in this file to the location of your Dashcode blog app (again, mine is at http://openideals.com/iphone)

10) Press the “Build and Go” green button in Xcode to launch your native application in the iPhone Simulator

(see the “OpenIdeals” icon with my face on it?!)

From here, you can modify the icon.png and Default.png (splash screen) until you are satisifed with the outcome of how your app looks. Also the “Info.plist” file controls the name of your application in the iPhone launcher.

(this is my splash screen that stays up for a few seconds upon app launch…)

At this point, you should have your blog running as a native application in the iPhone Simulator. To actual get this application out to the world, you’ll need to pay Apple $99 to join their Developer Program, as well as jump through many hoops to get all the security keys and permissions to distribute your application.

Otherwise, you can also just point people with iPhones or iPod Touches directly to your mobile application URL… that would work, too!

Final note on the amazing PhoneGap – they also support native application web wrapping for Android and Blackberry, as well as a bunch of other features like determining the device GPS location via Javascript calls.

That is all for this post… I hope you found it useful and to the point. I may do a similar one for Android + Eclipse, especially for all the non-Mac OS users out there.