1,277 karma · joined October 4, 2008
edit: http://mysql.org redirects to http://dev.mysql.com.
They've completely segmented the navigation between the commercial and developer sections of the site.
In particular, as a developer, I'm excited about the opportunity to have solid multitouch on a bigger screen.
The first example that comes to mind is the fact that numerous games and other apps aren't possible on the iPhone/touch because the screen isn't big enough, such as two-player games on the same screen.
Why would anyone (edit: a user who buys a below $1k machine) be inclined to purchase a netbook or even a 13" PC instead of this?
At the very least, this demonstrates both respect and sympathy for other engineers who need to use an API. Often, it also correlates to a well engineered product underneath.
For the meantime (next year or two), until batteries get better and hardware more efficient, push notifications are a pretty good way to solve this. Why does the handset need to keep these connections open when a remote server can do this more efficiently, not draining the battery, and then push a notification when an event happens?
There is a fundamental limit to the amount of information that can be conveyed on a 4" screen. Everything else "running" in the background, in a single tasking environment, can be taken care of by well written apps and services. More of a pain for the developer, yes, but a godsend for one's battery and CPU time.
The Apple model, one app at a time, makes a lot of sense, particularly in this use case: on a device with a four inch screen, there's no need to have a game, or most other applications, running in the background!
On that note, who is everyone using for registration these days?
pets.com, etoys, et al. -> zappos,
altavista, goto, yhoo, et al. -> goog,
broadcast.com, real media, "quicktime TV" -> youtube
These examples were all established a few years after the original players came in fully loaded with cash, hype, etc yet failed to solve or even identify underlying problems.
The Android system of notifying the user exactly which APIs are being used by an app, prior to install, seems like a step in the right direction.
Apple's Airtunes works really well. Plug in speakers/receiver/whatever (either analog or SPDIF) into each Airport Express. In iTunes, check each Airport you want to play through, and away you go. The audio sync is good. The Remote app for iPhone/touch works nicely with this kind of setup.
Another option, which I think is more expensive and difficult, is Sonos.
http://itunes.apple.com/WebObjects/MZStore.woa/wa/viewSoftwa...
http://www.readwriteweb.com/archives/first_iphone_augmented_...