It really comes down to drivers and reference platforms. The Coby and Pantech-class of manufacturers usually take an ODM reference design, apply some stickers and a new case, and build it. These manufacturers are going to be the first wave of WebOS devices.
So WebOS needs a stable of drivers for existing and upcoming reference designs. I figure there are 4 tiers of drivers:
- usable as-is & open source/freely distributable license)
- usable as-is but needs licensin
- possibly workable & open/distributable
- does not work & closed source
My suggestion (not being a coder) would be to see what drivers could be plundered from Meego and Android. Meego is based on a linux kernel so odds are lots of Meego drivers will be usable as-is.
After that, see what are the common platforms not covered. If we are talking phones, I'd shoot for the WinPhone platform; every manufacturer has a WinPhone handset that isn't exactly flying off of shelves. They might be willing to experiment with WebOS if all it takes is reflashing the device and applying a different sticker to the case.
For tablets I'd target the BB Playbook/Kindle Fire platform, the NVidia Tegra series, and the Intel MID.
Why Intel? Meego only has limited uptake, mainly as a Nat system, and a small user base. Intel could use the somewhat
rabid WebOS fanbase to get one of those low-end OEMs to produce x86 WebOS tablets and possibly get some consumer
market traction. And Intel is willing to spend money.