- #Chrome workspaces full#
- #Chrome workspaces windows 10#
- #Chrome workspaces android#
- #Chrome workspaces software#
I prepared this talk for Chrome Dev Summit Extended 2020 in Singapore. Extensions that has helped my daily development.Switching environments and feature toggles.Communicating between the Content script and the web page.👥 Chrome Developer Summit Extended (Cancelled).
Chime in if you do have an older device and have seen speed degradation that might be caused by Chrome OS updates.Personalised Development Workspace With Chrome Extension I haven’t yet seen Chrome OS slowed down by feature bloat, although I don’t have older Chromebooks to test that observation.
#Chrome workspaces android#
If you just want to browse the web and don’t need or want Android or Linux apps, virtual desktops, and mobile website views, you don’t have to. Keep in mind that you don’t have to use every feature included in Chrome OS. When reporting on these types of new features I often hear from folks who just want Chrome OS to remain simple.
#Chrome workspaces windows 10#
Here’s how it looks in Windows 10 with multiple desktop spaces, for example. For now, Chrome OS only has a way to zoom the desktop out and show all running apps you can’t move them to another virtual workspace.
They offer the feel of having a second display and more room to work and organize apps.
#Chrome workspaces software#
Virtual workspaces have long been a staple on other software platforms for years, whether we’re talking about Windows, macOS or Linux. There’s just no way today to have a desktop screen filled with work apps or browser tabs and a separate second screen space for consumer or content activities, for example. For the moment we’re constrained to a single “one screen” environment where we can show a few apps on the display while minimizing or covering others. There is a point to getting virtual desktop workspaces in Chrome OS though. I’ll probably test the feature on my Pixel Slate, but honestly, I doubt I’ll use it for any length of time. I think the ability to switch to a “small screened version” of a site on small screened Chrome OS device will do a world of good for those devices. This is why the upcoming ability to request a mobile website in Chrome OS is a big deal to me. You just have a small screened tablet with a web experience best suited for a larger display. But you can’t take that monitor with you when leaving the desk behind. And yes, you can dock or connect a smaller tablet to a larger external monitor to get around this. Conversely, the desktop web experience on a larger device - the HP Chromebook X2 or the Google Pixel Slate, for example - is very efficient.
#Chrome workspaces full#
but it becomes harder to use that full web on a small screen. Yes, it’s great to have the full desktop web, true Google Docs, etc…. Using the 9.7-inch Acer Chromebook Tab 10 is when this hit me. Why? Because my observable theory is that the smaller the display size, the less value from a user experience standpoint is provided from a full desktop browser. In fact, although many people like or want small Chrome OS tablets, I’m actually not a fan, which may be surprising. Part of that has to do with the touch controls but I think an even bigger part has to do with screen size. I wholeheartedly agree with Liu’s observation that a full desktop site on a mobile device doesn’t always make sense. David Ruddock over at Android Police got a little time from Kan Liu, Google’s senior product manager for Chrome OS, and Liu shared details on two features in the works: virtual workspaces and a mobile website viewing mode for Chromebooks and Chrome tablets. While this week saw the long-awaited first reviews of the Google Pixel Slate, it also shed a little light on the future of the software platform.
0 kommentar(er)
