Blog Post

The Chrome Show: How not to use a Chromebook

As a heavy-duty Chromebook(s goog) user, it made sense for me to get the LTE version of the Pixel. Another tech writer did the same but had issues getting a signal inside a Starbucks(s sbux): even Wi-Fi was out of commission. But the Chromebook isn’t a “brick” as the author suggests; you have to understand how to use a Chromebook and its admittedly limited offline capabilities.

We also found code suggesting that an Nvidia Tegra 4 could power a new Chromebook and offer up some new apps for editing text and code.

(Download this episode)

The Chrome Show RSS Feed

Subscribe in iTunes

Listen on Stitcher

Hosts: Alex Colon and Kevin C. Tofel


Are those floating barges the Chrome stores we were hoping for?

Code hints at an Nvidia(s nvda) Tegra 4 Chromebook in the works

Chrome beta for Android updated

Android gets the Chromium WebView

Rock on: Pandora comes to the Chromecast!

I Gave Up My Mac For A Google Chromebook Pixel And Loved It … Until It Became A Brick At Starbucks”  HUH?!?

Need some Chrome apps for coding and writing? Joe has some to check out.

Tip: Maybe you don’t want to sync all of your Chrome settings.

Extension of the week: APK Downloader

4 Responses to “The Chrome Show: How not to use a Chromebook”

  1. As much as I wanted to dislike Julie’s article, particularly since she’s a tech writer who didn’t do due diligence in learning the machine, I pretty much agree with a lot of what she says. The GDrive inaccessibility messaging when offline is not helpful; when online the messaging directs you to the network connectivity path, when the problem is not clicking make avail offline initially. Really poor focus on the user expereience I think. Her lack of 3g with Pixel vs. obtaining a signal with her phone needed explanation.

    There is no clear-cut, single source of how to do xyz for the user to follow on the web afaik, but particularly bad is the lack of resources when specific use cases go wrong, as I’ve found out. Did you know pressing ctrl with the Drive open will give you the option to delete your over-syncing local cache?

    Regardless the floating barges are one thing but if Google doesn’t polish out their average Joe troubleshooting no amount of showrooming can compensate.

    • Some, who are a lot more knowledgeable than me on this issue have said that it was due to Starbucks using HTTP rather than the normal HTTPS for their authentication page that threw the Chromebook. In other words, the issue is caused by the Chromebook following proper security measures to protect passwords on authentication pages while Starbucks didn’t.

      In any case on the web page she shows in her article, there is a link “browse as guest” which would have allowed her to access WiFi without going to the login page.

  2. Benjamin Beck

    Interesting…I read the article and it was said that they could not even take a screen shot at Starbucks….that is all local so there is obviously a major error between the chair and the keyboard.