{"id":41570,"date":"2009-11-13T13:30:27","date_gmt":"2009-11-13T18:30:27","guid":{"rendered":"http:\/\/gigaom.com\/?p=79694"},"modified":"2009-11-13T13:30:27","modified_gmt":"2009-11-13T18:30:27","slug":"smartbooks-have-to-design-their-own-market","status":"publish","type":"post","link":"https:\/\/mereja.media\/index\/41570","title":{"rendered":"Smartbooks Have to Design Their Own Market"},"content":{"rendered":"
\n

\"lenovosmartbook21\"<\/p>\n

Qualcomm-powered Lenovo smartbook<\/p>\n<\/div>\n

Qualcomm earlier this year introduced us to the smartbook concept. On paper, such a device sounds like the perfect bridge between a small smartphone and a clunky notebook — all-day battery life, a full keyboard and integrated data connectivity in an easy-to-carry package. Unfortunately, the best-laid plans often go awry, and the first expected smartbook looks like nothing more than an ARM-powered netbook running Linux.<\/p>\n

In order to carve out a market, smartbooks should offer the best features of the two devices they fit between<\/a>. Smartbooks need all-day runtime, instant-on and smartphone connectivity melded with the keyboard and usability of a netbook. But at the same time, a successful smartbook must offer an advantage over these two devices — it must be usable, but not too big. Make the device too large and it will compete poorly against netbooks, which offer x86 program compatibility and nearly all-day runtime. That’s exactly what I see in the first smartbook design — a netbook form factor that fails to take advantage of using a lower-powered ARM processor in a pocketable package.<\/p>\n

Image courtesy of Liliputing<\/a><\/em><\/p>\n

\"\"<\/div>\n

\n<\/img><\/a> <\/img><\/a> <\/img><\/a> <\/img><\/a> <\/img><\/a>\n<\/div>\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

Qualcomm-powered Lenovo smartbook Qualcomm earlier this year introduced us to the smartbook concept. On paper, such a device sounds like the perfect bridge between a small smartphone and a clunky notebook — all-day battery life, a full keyboard and integrated data connectivity in an easy-to-carry package. Unfortunately, the best-laid plans often go awry, and the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-41570","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/posts\/41570","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/comments?post=41570"}],"version-history":[{"count":0,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/posts\/41570\/revisions"}],"wp:attachment":[{"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/media?parent=41570"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/categories?post=41570"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mereja.media\/index\/wp-json\/wp\/v2\/tags?post=41570"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}