WePad | iPad | |
Display | 11.6-inch (1,366 x 768 pixels) | 9.7-inch (1,024 x 768 pixels) |
Processor | 1.66 GHz Intel Atom N450 Pineview-M | 1.0 GHz Apple A4 |
Memory | 16 GB NAND Flash (optional 32 GB internal + 32 GB SDcard) | 16 / 32 / 64 GB |
Webcam | 1.3 Megapixel | None |
Ports | 2 USB ports, card reader, audio out, SIM card slot, multi pin connector | Apple connector for camera or card reader as peripherals |
Flash/Adobe Air | Yes / Yes | No / No |
AppStore | WePad AppStore + Google Android Marketplace | iTunes App Store |
Multitasking | Yes | Restricted, allowed only for Apple apps |
Battery life | 6 hours | 10 hours |
ebook Format | eBook format All open standards | Proprietary Apple format from iBooks store |
Wirless connect | Bluetooth 2.1, WiFi N, 3G optional | Bluetooth 2.1 + EDR, WiFi N, 3G optional |
Body | Magnesium-Aluminium | Aluminium |
Dimension | 288 x 190 x 13 mm | 242.8 x 189.7 x 13.4 mm |
Weight | 800 g (850 g with 3G) | 680 g |
We’ve been hearing rumors about Facebook’s location features for a long time, but the buzz has picked up in the last few months. Those rumors got legs in October, when we noticed that the site had added language explicitly talking about location features to its rewritten privacy policy.
The question now is exactly what this location sharing will look like. I’ve heard that Facebook has tested simply attaching location data to user status updates, similar to the way Twitter does it. According to the report, Facebook will also offer an API to third parties, presumably allowing services like Foursquare to send their location data into Facebook (it’s unclear if data will also flow the other way).
Perhaps the most interesting part of the Times piece is the assertion that Facebook isn’t looking to beat Foursquare, Gowalla, and similar location based services — something that I believe it could easily do if it wanted to. Rather, it’s looking to beat Google in the small-business advertising space. The Times report doesn’t say much on how exactly Facebook is going to do that, but I suspect it will involve getting as many third parties as possible to integrate its API.