Google is getting ready to release a version of Chrome that works in Metro mode in Windows 8 Release Preview.
On Thursday Carlos Pizano, Software Engineer and “Metro Gnome” at Google, said that Chrome for Windows 8 Release Preview will arrive soon.
According to Pizano’s blog entry, Chrome will run in both Metro and desktop environments of Windows 8 on x86. However Chrome will not be released for Windows RT — the version of Windows 8 running on ARM-based chips — because Microsoft is reportedly not allowing browsers other than Internet Explorer on the platform.
“The initial releases of Chrome in Metro mode will include integration with the basic Windows 8 system functionality, such as charms and snap view,” he said. “Over the next few months, we’ll be smoothing out the UI on Metro and improving touch support, so please feel free to file bugs. We’re committed to bringing the speed, simplicity, and security of Chrome into Windows 8, and we look forward to working with you on it.”
Consumers running Windows 8 Release Preview will be able to try the Chrome browser in Metro mode in the next Chrome Dev channel release by setting it as the default browser. Based on a screenshot provided by Pizano, the browser won’t look any different than it does on Windows 7 or other desktop operating systems, keeping with the standard Google design.
Microsoft is following Apple’s lead by denying 3rd-party browsers besides its own stock Internet Explorer on Windows RT tablets with ARM-based processors. The desktop version of Windows 8 won’t have the same restriction although users won’t be able to run more than one browser in Metro mode at any given time.
In addition to Google, Mozilla is also working on a Metro version of Firefox. The company recently published a blog stating that users of Windows RT also deserve a choice of browsers, and called on Microsoft to remain firm on its user choice principles.
“Windows on ARM -as currently designed- restricts user choice, reduces competition and chills innovation,” wrote Mozilla General Council Harvey Anderson. “By allowing only IE to perform the advanced functions of a modern Web browser, third-party browsers are effectively excluded from the platform. This matters for users of today’s tablets and tomorrow’s PCs.”
“Because Windows on ARM relies upon so many traditional Windows assets, including brand, code, footprint, and experience, the decision to exclude other browsers may also have antitrust implications,” Anderson added.
Sounds like a threat, doesn’t it?
Article source: http://www.tomshardware.com/news/Chrome-Metro-Windows-8-Windows-RT-Carlos-Pizano,15962.html
Tags: ARM, Chrome Dev, Internet Explorer, Metro Gnome, Release Preview, UI
Sony Xperia S (Photo credit: John.Karakatsanis)
While all eyes might be on the Samsung Galaxy S3, I’ve been spending time with another flagship Android handset, Sony’s Xperia S. It’s a masculine looking smartphone which has a lot going for it, but there are a few issues in Sony’s first Android powered handset that will make a lot of people think careful before any potential purchase.
Following Sony’s acquisition of the Ericsson part of Sony Ericsson, the Xperia S is the first ’100% Sony’ smartphone to be released. In parts it does feel rather rushed – the Sony Ericsson logo is prominent on the rear of the handset for some reason, while there are mentions of the joint venture still lingering in the UI and casing.
Attention to detail lifts any smartphone out of the world of ‘stock Android handsets’ and while Sony has made a number of efforts to make the handset feel ‘Sony’ and not ‘Google’ errors like the above undo the effort rather quickly. I want to see my smartphone manufacturers sweat the small software details as well as the broad strokes in the hardware and manufacturing process.
For the technically minded, the Xperia S has a 1.5Ghz dual core Scorpion CPU, the Qualcomm Adreno 220 GPU, 1GB of Ram, 32GB of internal storage, no support for memory cards or additional storage, and a 1750 mAh sealed battery.
While many people do buy their handsets on the strength of a spec list, I don’t think that’s a huge percentage. Those that do are going to make a bee-line straight to the recently announced Samsung Galaxy S3, which is marginally ahead in the numbers game when compared to the Xperia S.
Up until the S3 was launched, the Xperia’s big advantage was the screen size – at 4.3 inches and a pixel resolution of 720×1280 it was one of the most densely packed screens in the Android world. Even though it is ‘just TFT LCD’ the Xperia S screen is impressive. The Galaxy S3 might be Super AMOLED with the same resolution, but at 4.8″ the larger physical size on the S3 does lead to some issues in terms of handling that the Xperia S does not experience – such as one handed operation. With a relatively small bezel around the screen, the Xperia S is as close to a one-handed smartphone as any other 4.3 inch Android device.
Acronyms aside the display looks gorgeous.
The Xperia S excels with its camera – a 12 megapixel shooter, capable of recording in HD with a 16x digital zoom. It’s still not comparable to a digital SLR but it’s sufficiently high quality to replace any point and shoot camera in your pocket. It’s also very fast in terms of taking a second shot. With nifty fingers it is possible to take a second shot in under a second.
There’s something utilitarian about the design of the Xperia S. The angular lines are only broken apart by two elements – the slight curvature on the back panel that helps the handset sit in the palm of your hand, and the clear perspex strip at the base of the device.
If you look carefully through the strip, you’ll see a tiny criss-cross pattern of wires, part of the radio system on the device. You’ll also spot the three Android buttons of back, home and menu. For the first few days I was pressing these , hoping for the function, when the actual capacitive key is just above the bar, signified by three white dots on the casing. The perspex bar gives just enough feedback to my fingertips so I know where to press for the three default keys, but it is disconcerting for the first few days to hit the perspex bar and see nothing happen. This may catch many people out when they try the device in a store.
Article source: http://www.forbes.com/sites/ewanspence/2012/06/09/the-xperia-s-is-a-worthy-android-smartphone-but-sony-need-to-deliver-more-to-survive/
Tags: Following Sony, Qualcomm Adreno, Samsung Galaxy S3, SLR, Sony Ericsson, UI
The Chromium team is set to release its first a version of the Chrome browser for the Metro mode of Windows 8, the open-source project announced on Thursday.
The version will run in both the Metro and desktop environments that come with Windows 8, but it will only run on the traditional x86 flavour of the operating system. As has already been established to some consternation, third-party browsers are locked out of the ‘Windows RT’ version that is designed to run on ARM-based tablets.
The Chromium project is open source, but the code it produces forms the basis for Google’s Chrome browser.
“The initial releases of Chrome in Metro mode will include integration with the basic Windows 8 system functionality, such as charms and snap view,” Google software engineer Carlos Pizano said in a blog post. “Over the next few months, we’ll be smoothing out the UI on Metro and improving touch support, so please feel free to file bugs.”
Those developers wanting to access the early versions of Chrome in Metro mode will need to set it as their default browser in the Chrome Dev channel, which releases new test iterations of the browser once or twice a week.
Microsoft’s decision to ensure the only browser on Windows RT is Internet Explorer has drawn criticism from rival browser-makers such as Mozilla, and European antitrust regulators said last month that they were keeping an eye on the situation.
Microsoft has famously clashed with these regulators before over the issue of browser choice, having been forced in 2009 to stop bundling IE with Windows.
Article source: http://rss.feedsportal.com/c/32424/f/469424/s/202d1c11/l/0L0Szdnet0O0Cblogs0Ccommunication0Ebreakdown0E10A0A0A0A0A30A0Cchrome0Eset0Eto0Eappear0Eon0Ewindows0E80Emetro0Emode0Ebut0Efor0Ex860Eonly0E10A0A263530C0Ds0Icid0F938/story01.htm
Tags: ARM, Carlos Pizano, Chrome Dev, Release Preview, Release Preview Read, UI
Splashtop made waves (thankyouverymuch) in April when the mobile app company launched the Windows 8 Testbed Metro for the iPad. This iPad app allowed owners to experience the few highs and many lows of Windows 8 Metro. As Engadget put it then, it must be a bit uncomfortable for iPads, but it’s a very impressive app offering nearly all the functionality of Metro including the many multitouch swipe functions. And now it’s available for Android tablets, too.
The price is still the same: $49.99 but its current 50% off for an unspecified limited time. The app runs at a resolution of 1280 x 800 resolution and supports Android tabs ranging from seven to ten inches. Like its iPad counterpart the app supports Metro’s UI touch gestures allowing developers and consumers alike to experience most of Metro on their current devices.
Sure, it’s a bit pricy even at the $25 promotional price, but the app is fully functional even if it’s not as smooth as the real thing. If Windows 8 calls your name, it’s best to jump on the platform now. For most people Metro is not love at first sight. You have to learn to love Metro.
[Google Play] [iTunes]
= 410 ? ’410px’ : ‘auto’);
Article source: http://techcrunch.com/2012/06/09/experience-metro-with-splashtops-android-and-ipad-windows-8-metro-testbed-app/
Tags: Google Play, Testbed Metro, UI
Google on Thursday announced it would soon release a preview of its Chrome browser capable of running in the Windows 8 Metro environment.
Chrome will be the first non-Microsoft browser to appear in Metro.
The company did not set a release date for the preview, saying in a post to the Chromium blog only that it would appear in “the next Chrome Dev channel release.”
Google operates multiple “channels,” or versions of Chrome, with escalating levels of stability and reliability. The least stable and earliest public build is dubbed “Dev;” others include “Beta” and “Stable.” The last is Google’s equivalent for a final, production-grade version.
When questioned later on Thursday, a Google spokeswoman declined to offer a specific date, saying, “It’s hard to provide precise timing.”
The Dev channel of Chrome is now on version 21, which it first reached May 21. But because Google updates each version on the Dev line multiple times — nine for Chrome 20 between April 10 and May 17, for instance — the Metro-ized Chrome could easily appear within the next week.
The browser will run in both Windows 8′s traditional x86/64 “desktop” mode — which sports a user interface (UI) very similar to Windows 7′s — and in the tablet- and touch-centric “Metro” mode, where programs are called “apps” and run in a full-screen, or at best, split view.
Under Microsoft’s rules, a browser must be selected by the user as the operating system’s default browser to run in Metro.
Carlos Pizano, who listed his title as “software engineer and Metro gnome,” warned that the first Metro version of Chrome is unfinished.
“The initial releases of Chrome in Metro mode will include integration with the basic Windows 8 system functionality, such as charms and snap view,” wrote Pizano. “Over the next few months, we’ll be smoothing out the UI on Metro and improving touch support.”
He did not give an estimate on when Google would add the Metro browser to the beta or stable builds.
Google first acknowledged that it was working on a Windows 8-specific version of Chrome in mid-March, about a month after rival Mozilla said the same about its Firefox browser. But while Mozilla has provided several updates on its Metro progress, until now, Google has been silent on the subject.
Microsoft has allowed other browser makers to access the desktop’s Win32 APIs (application programming interfaces) from within Metro, in effect leveling the playing field on Windows 8.
- Microsoft tips how Windows 8 store will promote desktop apps
- Google touts pending debut of Chrome on Windows 8 Metro
- Intel, ARM trade barbs over Windows 8, RT
- Asus tablet prompts speculation on competitors’ offers
- Microsoft assimilates Flash in Metro’s IE10
- Windows 8′s built-in AV to be security of last resort
- Windows 8 Release Preview: Updated but still uneasy
- Update: Microsoft confirms $15 Windows 8 upgrade
- FAQ: Get going with Windows 8 Release Preview
- Microsoft launches Windows 8 Release Preview
Continuing coverage: Windows 8
Article source: http://www.computerworld.com/s/article/9227895/Google_touts_pending_debut_of_Chrome_on_Windows_8_Metro
Tags: ARM, Chrome Dev, Release Preview Continuing, Release Preview Microsoft, Release Preview Updated, UI
As the release of Windows 8 draws closer, all of the major browser vendors are also preparing to launching their applications for the touch-centric Metro UI that will prominently feature in next version of Microsoft’s flagship operating system. Today, Google announced that – assuming you are running the Release Preview of Windows 8 – you’ll soon be able to test Chrome in Windows 8′s Metro mode. Once the next version of Chrome arrives in the Dev channel, you will be able to take Chrome for Metro for a spin after setting it as your default browser.
Google Software Engineer and “Metro Gnome” Carlos Pizano notes that this first version will “ include integration with the basic Windows 8 system functionality, such as charms and snap view.” He also promises that the Chrome team will be “smoothing out the UI on Metro and improving touch support.”
Judging from the first screenshot Google posted today, Chrome for Metro will mostly stick to the standard design Google is also using on the desktop. Unlike Microsoft’s Internet Explorer for Metro, Google isn’t experimenting with any new designs here as far as we can see.
Similar to Apple’s policies, Microsoft doesn’t allow any browsers besides its own Internet Explorer on Windows RT tablets with ARM processors. On the desktop, however, there are no such restrictions besides the fact that users won’t be able to run more than one browser in Metro mode at any given time.
Just like Google, Mozilla is also working on a Metro version of Firefox. While we’ve seen some mockups for Mozilla’s browser for Metro, though, it looks like Google is currently a bit closer to actually releasing a working app.
Google Chrome is an based on the open source web browser Chromium which is based on Webkit. It was accidentally announced prematurely on September 1, 2008 and slated for release the following day. It premiered originally on Windows only, with Mac OS and Linux versions released in early 2010.
Tabbed browsing where each tab gets its own process, leading to faster and more stable browsing. If one tab crashes, the whole browser doesn’t go down with it
Article source: http://techcrunch.com/2012/06/07/chrome-for-metro-set-to-arrive-in-next-dev-channel-release/
Tags: ARM, Internet Explorer, Release Preview, UI, Unlike Microsoft
Chances are some members of Team Android won’t be too pleased to share the any.DO goods with the iOS squad, but for what it’s worth, you’ll always be able to say you had it first. After being a success on Google’s mobile OS, any.DO has decided to test out other waters, including making its way to those iPod touches / iPhones / iPads of the world, as well as Google Chrome in extension form. On the iOS front, the app — which sports a very minimalist, but sleek design — allows users to add, adjust and edit multiple tasks using a drag-and-drop, gesture-based UI. Meanwhile, the Chrome extension keeps the similar productivity goal, but takes it to the larger screen — what’s best, however, is any.DO allows you to sync all your To-Do’s between different devices regardless of OS. Both the iOS application and Chrome extension are free of charge, and you can grab the version best suited for you at either of the source links below.
Article source: http://www.engadget.com/2012/06/05/any-do-to-do-on-ios-google-chrome/
Tags: Google Chrome, OS, Team Android, UI
HTC Sensation Z710E Unlocked GSM Android Smartphone on Amazon
HTC has rescheduled the Android 4.0 update for the HTC Sensation handsets, which means users will now have to wait somewhat longer to upgrade to the Ice Cream Sandwich Experience.
Initially, the Taiwan-based phone manufacturer had announced that they would be releasing the Android 4.0 ICS upgrade for the HTC Sensation by the end of March. But then almost two months have gone past and now the company has announced that the update is still about a month away. The official announcement made recently says the update will not be available before some time towards the end of next month.
The new release schedule for the updates show that the company is planning the roll out of these updates between March and June this year for HTC Sensation. The schedule for HTC Sensation XL is between April and June. So there’s just one month to go before their own officially announcement time frame runs out. HTC has also endeavored to address customer frustration at the lack of upgrades and has offered explanations as to why the upgrades are taking so long. Here’s part of the company’s explanation: -
“Our goal is to make sure that an upgrade provides an equal or improved customer experience and that means a high standard of quality for hardware compatibility, adapting device or carrier specific customizations, testing by HTC and partners, addressing device hardware constraints, and many other factors,”
The newly released list also contains timelines for other Android handsets — HTC Evo 3D, HTC Rhyme and HTC Desire HD. The first two are set to be upgraded between June and July this year. HTC Desire HD will get updated between June and August. There will be no official upgrades for the HTC Salsa, Chacha, Explorer or Flyer.
HTC has also announced that the upgrades will nto bring the Sense UI 4.0 alonside Android 4.0. The company has not given out any official reasons for this except for a lack of “dedcated hardware” in some of its devices but it is clear that the older phones are not equipped to handle both Android 4.0 ICS and HTC Sense UI 4.0 at the same time. They are both resource intensive and might hamper phone performance. However, it is also possible HTC is saving the Sense UI 4.0 as an extra for those who are investing in the new handsets that are coming out with Android 4.0 pre-installed.
According to HTC, Sense UI 4.0 requires dedicated hardware that is not yet available in all of its devices. This might be just another way of saying that some of its older phones are not powerful enough to handle the new UI overlay.
This new push for upgrade the HTC Sensation, Sensation XL and other phones comes from the fact that Android 5.0 is about to debut sometime later this year (rumors). Every Android manufacturer is trying to push out Android 4.0 upgrades before moving on to Android 5.0.
Article source: http://solar-panel-reviews.org/2012/05/htc-sensation-handsets-to-finally-get-android-4-0-ics-updates-soon/
Tags: Every Android, HTC, Taiwan, UI
WOBURN, Mass., May 29, 2012 (BUSINESS WIRE) –
Monotype Imaging Holdings Inc.
, a leading provider of
typefaces, technology and expertise for creative applications and
consumer devices, has released a suite of software designed to transform
the Google Android(TM) 4.0 user experience. Monotype’s Type
Enhancements for Android enables device manufacturers to tailor
their products using high-quality typefaces, comprehensive multilingual
support and advanced font technologies.
“Type Enhancements for Android is an all-in-one solution that opens a
myriad of possibilities to evolve the Android experience,” said John
Seguin, executive vice president at Monotype Imaging. “OEMs are able to
quickly gain robust capabilities that enable their Android device to
stand out from the crowd and deliver branded, high-quality experiences
anywhere in the world.”
Type Enhancements for Android is comprised of selectable modules for
meeting a wide range of requirements, such as ensuring the display of
highly legible, brand-complementary typefaces in multiple languages,
superior Web browsing experiences and personalization through
user-selected fonts. OEMs are able to easily choose any combination of
modules, all of which have been engineered to meet Google’s CTS
(Compatibility Test Suite) certification requirements.
Type Enhancements for Android modules:
User Interface font replacement — OEMs may differentiate their
device by customizing the look of its user interface — or configuring
their device to enable users to do it for themselves — by replacing the
default UI font with a different typeface.
mobile font download solution — FlipFont empowers users to switch
their UI font, making their devices more personal and fun to use. Users
connect to an online selection of fonts to purchase, download and
install. OEMs have an opportunity to benefit with an additional revenue
stream as they promote access to a unique selection of downloadable
Expanded language support — OEMs can expand on Android’s
multilingual capabilities with extended
support for Indic languages, Thai and other complex scripts such as
Arabic and Hebrew. With Monotype’s expanded language module, OEMs are
able to support all of the world’s major
Connects and Edge(TM)
Technology — Monotype’s high-performance font rendering
engine is plug-in ready using iType Connects for Android. iType Connects
features Edge Technology, which enables East Asian text to display at
its best, even when comprised of intricately shaped characters. OEMs are
able to make precise adjustments using Monotype’s unique Edge tuning
feature, which ensures that text appears at its highest quality to meet
specific screen requirements. Text and brands are able to display
consistently and with high quality across display environments.
Web core fonts — OEMs can ensure a consistent Web browsing
experience by employing Monotype’s suite of Web core fonts, which bring
familiarity to users who expect Web pages to look and feel the same
whether they’re accessed from a phone, tablet or laptop. Monotype’s Web
core fonts enable OEMs to ensure compatibility with a PC-based Web
Smart Gamma — OEMs are no longer limited to displaying white text
on a black background, or vice versa, without compromises in quality.
The Smart Gamma option enables each combination to be optimized
independently, giving UI designers the freedom of choosing where to
apply foreground or background colors, without sacrificing quality.
About Monotype Imaging
Monotype Imaging is a leading provider of typefaces, technology and
expertise that enable the best user experience and ensure brand
integrity. Based in Woburn, Mass., Monotype Imaging provides customers
worldwide with typeface solutions for a broad range of creative
applications and consumer devices. The company’s library and e-commerce
sites are home to many of the most widely used typefaces — including the Helvetica(R),
families — as well as the next generation of type designs. Further
information is available at
Monotype, FlipFont and iType are trademarks of Monotype Imaging Inc.
registered in the U.S. Patent and Trademark Office and may be registered
in certain jurisdictions. Edge is a trademark of Monotype Imaging Inc.
and may be registered in certain jurisdictions. Helvetica and Frutiger
are trademarks of Linotype Corp. registered in the U.S. Patent and
Trademark Office and may be registered in certain jurisdictions in the
name of Linotype Corp. or its licensee Linotype GmbH. Univers is a
trademark of Linotype GmbH registered in the U.S. Patent and Trademark
Office and may be registered in certain other jurisdictions. Google
Android is a trademark of Google Inc. All other trademarks are the
property of their respective owners. (C) 2012 Monotype Imaging Inc. All
Photos/Multimedia Gallery Available:
SOURCE: Monotype Imaging Inc.
Monotype Imaging Inc.
Vikki Quick, 781-970-6115
Monotype Imaging Ltd.
Julie Strawson, 44 (0) 1737-781624
Lorenz Schirmer, 49 (0) 6172-484-470
Copyright Business Wire 2012
Add to portfolio
Article source: http://www.marketwatch.com/story/monotype-imaging-announces-type-enhancements-for-android-2012-05-29
Tags: Linotype Corp, Monotype Imaging, Monotype Imaging Inc, Trademark Office, UI, Vikki Quick
By Vlad Bobleanta on 28 May 12
Another Android phone maker is set to unveil a UI overlay sitting atop Google’s mobile operating system. This time it’s Huawei. Its Sense/TouchWiz competitor will be called Emotion UI and is going to arrive in July.
Just a few days ago, ZTE (the other big Chinese manufacturer) announced its very own 3D skin for Android, powered by Rightware’s Kanzi UI. This skin will be used from now on for ZTE’s smartphones running Android 4.0 Ice Cream Sandwich.
ICS is also presumably Huawei’s ‘target’ for its Emotion UI, although details are scarce at the moment. The grand unveiling is set for June 9, and the interface will become available sometime in July. Still a mystery is whether Huawei plans to issue updates to already shipping Android smartphones in order to add the Emotion UI. However, it seems almost certain that all Huawei Android devices that will ship in or after July will come bearing this new overlay. That obviously includes the Ascend D quad, the company’s flagship smartphone for this year, which may have been delayed until July specifically in order to get the Emotion UI baked in.
At this point we don’t really know what the Emotion UI will look like, or what functionality it will add to Android. Huawei uses words such as “emotional”, “simple”, and “smart” in describing it, and says that it has listened carefully to the needs of users. Then again, they all say this. HTC even dared say it was ‘listening to its customers’ when it decided that extra-slim phones were preferable to better battery life – and that’s quite absurd.
In the picture above which speaks about the big event in which the Emotion UI will first be showcased, we can see what looks like the stock Android ICS launcher with no modifications whatsoever. So maybe Huawei’s UI really is subtle. Or maybe the company wanted to keep it a secret until said event.
It’s not 100% clear if the Emotion UI will make it outside of China, but it probably will given Huawei’s new global ambitions. The company is undergoing a massive transition from a manufacturer most widely regarded for its low-end price-competitive offerings to one that can compete on the high-end as well (with its own in-house designed processor even).
Apparently Huawei thought that part of this transition had to be adding its own UI to Android. I would have liked it to try to differentiate itself by becoming the only Android device maker not to have its own custom UI slapped on top of the OS, and as such deliver updates quicker than its competitors. But Huawei obviously disagrees. Sure, by designing it own UI, Huawei gets to use the words “user experience” in PR materials, but maybe the world’s had enough of all this gimmickry. Or maybe Emotion UI will prove to be subtle enough to be brilliant. Let’s wait and find out, shall we?
If you liked the post, you might find these interesting too:
« ATT-bound LG E970 with possible quad-core Snapdragon and Andreno 320 graphics gets benchmarkedNokia Lumia 900 Batman Edition to be released in Europe soon »
Article source: http://www.unwiredview.com/2012/05/28/huaweis-emotion-ui-for-android-set-to-debut-in-july-will-be-detailed-on-june-9/
Tags: Apparently Huawei, Huawei Android, MWC, PR, UI, ZTE