
In the wake of the LiMo Foundation's huge announcement that it has
netted Verizon Wireless to sit on its board, everyone wants to know: what does this mean for Verizon's official (meaning non-"Any Apps, Any Device") lineup, and where does this leave
Android? LAPTOP has posted a good summary of some pressing questions and answers, revealing that LiMo-based devices won't launch on Big Red until next year anyway -- so there's really nothing to sweat about in the short term. As the carrier's lofty board seat might have suggested, it intends LiMo to percolate through its entire product range, starting with dumbphones and moving to smartphones (it
is Linux, after all) as time goes on. Finally, it emphasized that the move certainly doesn't spell doom for Android; for consumers, the worst case is that they'd have to bring their own Android handset to the table (assuming there are compatible, unlocked CDMA devices available), but if Verizon senses that Android demand is strong enough, there's still nothing stopping it from bringing some hardware into its official stable. Either way, the Age of Linux is upon Verizon customers, which we're thinking is probably going to end up being a good thing.
Reader Comments (Page 1 of 1)
Sascha @ May 21st 2008 3:07PM
AFAIK, LiMo is not "Linux" as most people know "Linux." LiMo doesn't carry with it the attributes of free, open-source, openness, hairy flower hippies dancing in the park, Richard Stallman, or third-party application accessibility. (Wow, that was some free association.)
For instance, MOTOMAGX is LiMo, and MOTOMAGX is about as locked down as any RTOS you ever did see.
LiMo is about manufacturers being able to bring devices to market more quickly by using a relatively standardized software platform. That software platform can be encrusted with every lock and restriction known to humans before it is released to the individual public. So say yay, yay, Nucleus and P2K are going away, but watch out before you make any generalizations about what LiMo handsets will look or feel like.
Not that you did, Chris - I'm just saying.