Lately I’ve noticed that some developers are avoiding building apps and, instead, are building custom web pages that are designed specifically for the iPhone. [...] Yesterday another one came along from Nextstop, which is a cool new app for sharing cool things to do near you (great for travelers to check out) and they, too, decided on HTML5 instead of doing an iPhone app.

Some reasons Nextstop likes HTML5:

1. Rapid iteration. If they code a new feature tonight, you get it tonight. No waiting three weeks for you to get their latest.
2. It prepares their systems for building a native app. Why? Because apps can include a Safari browser instance inside, so all of this work is reusable, even if they do a native app.
3. It’s easier to build and debug because you don’t need to do a lot of specialized coding to make the native app work properly.
4. It fits into the greater web easier for users. In an iPhone app it can be jarring to take users out to a web browser, but if they already are in the browser they are used to going to other pages and back again using Safari’s navigation.

That sounds like a really great idea, doesn’t it. You know who else thought so? Steve Jobs:

WWDC 2007, SAN FRANCISCO—June 11, 2007—Apple® today announced that its revolutionary iPhone™ will run applications created with Web 2.0 Internet standards when it begins shipping on June 29. Developers can create Web 2.0 applications which look and behave just like the applications built into iPhone, and which can seamlessly access iPhone’s services, including making a phone call, sending an email and displaying a location in Google Maps.

But then the developers were all like, “Nooooooooo!” and Apple was all like, “Fiiiiine!” in October 2007 and announced a way to build native apps. But submitting an app to the App Store and going through the approval process is annoying as hell for developers, so they’re getting around that by doing what Apple wanted them to do anyway in the first place.

That Steve Jobs sure is a crafty one.

PreThinking added their logo to the image, as is common practice in the interblogosphernetwebs, where anyone can take your image and claim it as theirs unless you put some form of identifier on it. For what this man did, the phrase “pre-thinking” is coincidentally appropriate.

[PreThinking via Gizmodo]

But yesterday Apple apparently did approve something called Wobble. It’s an application that allows you to add “wobble regions” to photographs. These regions will jiggle when you shake your iPhone. (Hint: You put them on boobies!!!!)

Seems Apple’s being their hypocritical selves again. After the jump, videos explaining why…

Here’s iBoobs. I don’t find it particularly entertaining myself, but the demo video shows that it’s hardly offensive or pornographic:

Contrast this with Wobble. Observe:

The use of actual boobies, to me, seems more pornographic than the use of fake ones. But there are two possible arguments in Apple’s favor here:
- Wobble, while obviously intended to make boobs jiggle, doesn’t come preloaded with any
- Apple does not condone the practice of ogling over fake tits because women shouldn’t feel the need to get implants or something

Either way, iPhone users have made a purchase, not a rental or lease or whatever, from Apple, and should therefore be allowed to put whatever they damn please onto it regardless of whether Apple likes it. But still, jiggle physics are always funny, especially when they create controversy.

[Source: Gizmodo]