(The survey wasn't limited to users of Titanium, but they did advertise it via Twitter etc.)

Your basic widgets are pretty straightforward to implement on multiple systems, but what eats up time and effort is indeed things like getting layout to feel like it fits in the system, and to integrate with native widget styles, dialogs, or UI conventions that are different. (Use a system icon there, a menu here; a nav bar at top here, submit/cancel buttons at the bottom there.)

For StatusNet Mobile which we built with Titanium we've had to do a lot of special-casing to get various parts of the UI looking and feeing a little more native on each system, and we've still got a number of dialogs that need more work. The majority of our UI though is in a webview, which is nicely universal. ;)

Tying into low-level platform integration can be a bit more difficult too; being able to 'share' messages out to other apps that accept the Action.SEND intent or text/plain for instance required tossing in a low-level module to hook into the Android system code directly, which was more awkward than I'd prefer.

I took the survey; even beyond sampling bias, IMO it just wasn't that great a survey: totally self-selected, vague questions and awkward, biased options for answers. I think Android's darn spiffy, but a measurement of what applications are actually being produced would be wayyyy more useful than a count of how many respondents picked that multiple-choice option for their favorite OS. (The title on the article is misleading as well; from the text it's pretty clear that it's about what we *hope* will be be popular in the future some day, not what platforms developers are actually targeting in their actual work.)

My own (free) app is cross-platform, built on Appcelerator's Titanium Mobile; it runs much smoother and nicer on iPhone, but we've got some very handy extras for inter-app sharing on Android that just aren't available on iOS. We were able to publish to the Android market *instantly*, but had to wait over a week to get pushed to the App Store. I'd still much rather see Android "win" (if there is such a thing as "winning") but there's still a lot of work to do on user interface, interactive performance, and reducing the administrative burden on users.

Working with both systems will give you a deeper understanding of each, as well as allowing you to sell to a larger customer base, should that be something that appeals to you.

It's still ongoing, naturally: Sun/Oracle has a page with updates on the case over the last few years.

By amazing coincidence, the mobile reformatter serves as the backend for our upcoming native app (and probably other peoples' unofficial native apps once they realize they don't have to run their own reformatter proxy).

Was finally approved on the California ballot last year, we'll see if the money comes through...

Driving from SF to LA is *hell* on holidays or in bad weather, but it's short enough that high-speed rail will get you there about as fast as flying (considering the extra check-in and security burden at the airport)

Thanks! :)

Those are also not actual Wikipedia content sites, but either redirects or sites of local Wikimedia chapters. All our actual content is on our own domains -- for instance German-language Wikipedia is at http://de.wikipedia.org/ not http://wikipedia.de/ which is a portal page maintained by Wikimedia Deutschland. (In part because German courts routinely shut wikipedia.de down in preliminary injunctions... ;)

General mass management tends to be done via a distributed ssh shell wrapper. There's not much mass management that needs to be done, usually, other than "update your PHP source/config files and restart the web/proxy/whatever server" or "go install updated packages".

The fun comes when individual servers are borked in some way and you have to beat them back into shape.

We're looking into puppet, but haven't deployed it yet.