I’m not sure I can see them pushing the “open web” aspect of it especially hard though. Sure, they’ll use those words, because everybody likes to use the word “open”, but I’m imagining a strong emphasis on facebook-centric APIs and services.

The platform would be an extension of the Facebook Development platform they’ve already got. Compatibility layers would be added so that most of the major Facebook apps would run reasonably well on ‘Facebook WebOS’ unmodified. New ‘native’ APIs would be added to take advantage of the hardware capabilities of mobile devices.

The message to developers on the Facebook platform would need to be something like: here are some tools to make your facebook apps (especially games) awesome on our devices. And (maybe at the f8 conference ala Google IO?) here are some free devices.

The message to consumers would probably be something like: Those Google guys have a mess of stuff for people who live in their Google account. Those Apple guys have a mess of stuff for people who live in their iTunes and Twitter accounts. Now here is a phone for people who live in their Facebook account.

As for who makes the good hardware they would need to run it on, I don’t know.

Where I would disagree is in the portrayal of Java as holding back Android. It held back WebOS because it wasn’t a good JVM. Dalvik is not the JVM. If there is a failure in Android, it’s an engineering problem, not a language problem.